Relax OP_RETURN standardness restrictions

The discourse within the Bitcoin development community, as highlighted in a recent thread, centers on the contentious issue of how data storage via transaction outputs is managed on the blockchain. A key point raised involves the proposal to modify current practices surrounding the use of unspendable outputs for storing data, which aims to facilitate the relay of small, time-sensitive data across the peer-to-peer network without necessitating permanent storage by all full nodes. This change, while seemingly inconsequential to those aiming to store large volumes of data due to pre-existing cheaper alternatives, introduces a nuanced approach to harm reduction by offering a method that circumvents the need for indefinite data retention by the entire network.

A significant aspect of this discussion touches upon existing mechanisms that allow for data storage on everyone's disk, a practice that has been operational and addressed by Core through data obfuscation methods. However, the conversation also brings to light how OP_RETURN outputs have historically been exploited for malicious purposes, such as updating command and control server domains for malware persistence, an issue documented in detail by Sophos (read the report). This highlights the broader implications of data storage practices on blockchain security and the innovative ways threat actors leverage blockchain technology.

Critics of the proposed changes have been accused of lacking substantive objections, instead resorting to emotional arguments that fail to address the core issues at hand. The dialogue also delves into broader criticisms of the system's robustness, with some participants questioning the reliance on communal goodwill for ensuring security. Amidst these exchanges, a call for grounding and a return to technical discussions over speculative or emotive responses can be discerned, emphasizing the importance of a rational and informed approach to development discussions.

This thread underscores not only the technical challenges faced by the Bitcoin development community but also the dynamic and sometimes contentious nature of collaborative innovation. As the community grapples with these issues, the emphasis remains on finding solutions that balance functionality with security, ensuring the blockchain's integrity while accommodating evolving use cases.