Discussion on OP_Return Data Storage Proposal
A significant discussion is unfolding among Bitcoin’s core developers regarding a controversial proposal aimed at eliminating the existing limit on OP_Return data storage. Put forward by Peter Todd, the proposal identified as PR 32359 seeks to remove the current restriction of 83 bytes on data outputs.
Advocates like Chaincode Labs developer Antoine Poinsot argue that the present cap has become obsolete as users have found alternative ways to store non-financial data, including methods like Taproot unspendable outputs and private miner memory pools known as MARA Slipstream.
Support and Resistance
Supporters of the change contend that lifting the restriction would facilitate legitimate applications that are currently being stifled by the outdated limit. However, there is substantial resistance to the proposal, notably from Luke Dashjr, who labels it as “completely insane.” Dashjr emphasizes that the focus should be on addressing security vulnerabilities rather than allowing what he describes as “junk data attacks.”
Ongoing Dialogue Among Developers
As the conversation continues, developers are actively sharing their views through comment threads on email lists and GitHub, with new messages emerging frequently. While some developers are expressing their endorsement with brief acknowledgments, termed “concept ACK,” others are voicing their dissent with “concept NACK” remarks. Notably, the proposal is still in the early stages, and robust technical evaluations have yet to be conducted.
This ongoing dialogue highlights the complex interplay of innovation and security within the Bitcoin community.
