- The change aims to streamline network efficiency but has sparked controversy within the community over process and potential impact.
- Critics worry about reduced focus on Bitcoin’s financial utility and alleged lack of consensus in the decision-making process.
Bitcoin Core developers have decided to eliminate an 80-byte restriction on OP_RETURN transaction outputs in the network’s upcoming upgrade, according to an announcement by Greg Sanders on GitHub dated May 5. This adjustment aims to allow more data to be added to Bitcoin transactions in a more efficient manner.
The OP_RETURN function in Bitcoin allows users to embed small amounts of information directly onto the blockchain. Unlike standard outputs, OP_RETURN outputs are not spendable, which helps prevent unnecessary growth of the unspent transaction output (UTXO) database. This change follows a proposal by Peter Todd at the request of Chaincode Labs, documented in PR 32359.
According to Sanders, the previous OP_RETURN limit acted as a “gentle signal that block space should be used sparingly for non-payment proof of publication data,” but is now outdated. Users have found workarounds—such as using fake output addresses—that are less efficient for the network, and some mining services have already bypassed the restriction. Sanders wrote, “Large-data inscriptions are happening regardless and can be done in more or less abusive ways; the cap merely channels them into more opaque forms that cause damage to the network.”
Potential benefits outlined include a cleaner UTXO set, improved consistency across the network, and better alignment with current use patterns. The development team considered maintaining, increasing, or entirely removing the cap, eventually settling on removal after what Sanders described as “broad, though not perhaps unanimous, support.”
Despite the technical rationale, some within the Bitcoin community have voiced reservations. Samson Mow shared objections on X, stating, “Many users find this to be an undesirable change for a number of reasons.” He noted users can refuse to update their software or use alternative network implementations.
Other critics, like Marty Bent, expressed concerns about the project’s governance, stating on X, “I think one thing is pretty clear, there is no consensus at the moment on this OP_RETURN issue.” Some community members have raised further questions about prioritizing financial transactions over data storage and about unspecified conflicts of interest regarding the change.
For additional background, research has indicated that Bitcoin block sizes could grow to 4 megabytes with increased use of inscriptions, as noted in related discussions.
The decision to remove the OP_RETURN limit marks a significant shift for Bitcoin’s technical structure, with supporters emphasizing network efficiency and critics voicing concerns about consensus and Bitcoin’s future direction.
✅ Follow BITNEWSBOT on Telegram, Facebook, LinkedIn, X.com, and Google News for instant updates.
Previous Articles:
- Mountain City Debates Proposed Bitcoin Mining Facility, Jobs, Impact
- OpenAI to Drop Investor Cap, Restructure as Public Benefit Firm
- Wood County Pushes for State Regulation of Cryptocurrency ATMs
- New US Attorney Appointed as SafeMoon CEO Karony Faces Trial
- JP Morgan, MIT Propose Standards for Interoperable Bank Tokens
