Published on: 2023-02-18T18:38:00+00:00
The discussions on the bitcoin-dev mailing list revolve around finding efficient and cost-effective ways to store data in the Bitcoin network. One proposal suggests increasing the size of the OP_RETURN to support a hash, signature, and metadata, while another proposal argues for allowing any number of OP_RETURN outputs without a size limit. The community also discusses the best practices for storing data in Bitcoin, including the use of witness envelopes and OP_RETURN.To request a change to the OP_RETURN size, individuals must issue a pull request on bitcoin-core and address any concerns or objections that arise. The process involves discussions within the community, obtaining acknowledgments (ACKs), and addressing negative acknowledgments (NACKs). The maintainers decide when to merge the change based on community interest and consensus. Once released, the change can only take effect after a significant number of miners and nodes have updated to the new release.The conversation explores different approaches and considerations, such as the efficiency gains of using FALSE IF ... ENDIF over repeated drops. There are also discussions on storing data in Bitcoin's UTXO set and the potential impact on deviant behavior. The use of Taproot is considered for making a script visible, with considerations for data privacy and user control.The discussions highlight the importance of community engagement, consensus-building, and addressing concerns when proposing changes to the Bitcoin protocol. Christopher Allen actively seeks to understand the tradeoffs in post-taproot Bitcoin, exploring options for publishing data while minimizing harm. The focus shifts to whether a traditional OP_RETURN or a spent taproot transaction is more suitable for placing a 64-byte message in the Bitcoin blockchain. However, alternative options and perspectives are welcomed in this ongoing discussion.
Updated on: 2023-08-02T08:54:11.232682+00:00