Posted by Martin Habovštiak
May 3, 2025/02:02 UTC
In a recent conversation with a legal professional, it was confirmed that possessing illegal content within a chain is not deemed illegal unless it can be easily accessed with general-purpose software. Moreover, the legality of images marked by red dots remains unchanged; they are still considered illegal if they inherently contain illegal content. An interesting point raised was the potential for confusing scanning tools, which has been addressed through the technique of xoring. The capability to xor without needing to redownload content exists, albeit through an external tool. It's suggested that those interested in having this feature integrated directly should either contribute to its development or fund it.
The discussion also touched upon a personal project involving the embedding of data into Bitcoin addresses through a process known as grinding. This project is publicly accessible via GitHub, although it was clarified that the technique has never been used to send information into the chain, and sending tips to the address mentioned is discouraged.
A common misconception regarding the complexity of implementing the 'red dot' method for non-technical individuals was dispelled by the use of ChatGPT to generate functional code effortlessly, highlighting the accessibility and efficiency of modern AI tools in programming tasks.
The email further delves into the implications of requiring signatures to prove discrete logarithm (dlog) knowledge for non-p2tr outputs, illustrating that such a requirement would significantly increase the data size for transactions beyond the current maximum standard for OP_RETURN outputs, while also emphasizing the substantial computational resources needed for signature verification compared to processing OP_RETURN. It was argued that enforcing signature and preimage requirements on Taproot could undermine protocols dependent on nothing-up-my-sleeve numbers (NUMS) and eliminate the advantages offered by Taproot. The discourse concludes by questioning the practicality and potential adverse effects of measures intended to combat spam within blockchain protocols, suggesting that such efforts might inadvertently exacerbate the situation.
TLDR
We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project?
Give Feedback