- Developers halted an attempt to quietly alter Bitcoin Core’s mempool policy, sparking debate over OP_RETURN data limits.
- The proposed change aimed to lift OP_RETURN’s 83-byte data cap, arguing it would standardize data storage and minimize network strain.
- Community disagreements over censorship, bitcoin’s intended use, and potential corporate influence led to the proposal’s rejection—for now.
Last week, a small group of developers attempted to adjust the default mempool policy of Bitcoin Core, which is the leading software for verifying and broadcasting bitcoin transactions globally. The change was stopped before approval after critics identified it as a renewed effort to raise the data storage limit for OP_RETURN outputs, originally proposed and rejected in 2023.
The disputed proposal, known as PR 32359 and written by developer Peter Todd, would have increased the data allowed in OP_RETURN, a function that lets people add extra information to bitcoin transactions. Critics on social media and developer forums described the move as chaotic and lacking consensus, with some calling it "malicious" or "vandalizing." Supporters, however, argued that the change would bring mempool policy up to date and align it with how users already store various kinds of data in bitcoin blocks. They noted that storing data via OP_RETURN is preferable to alternative methods, which can increase workload for Bitcoin nodes.
According to statements on Stacker News, supporters compared the proposal to “harm reduction,” saying it would help standardize data storage and reduce negative effects like network congestion. Developer Mark "Murch" Erhardt explained that allowing larger OP_RETURN payloads could reduce the number of unprunable transaction outputs (UTXOs) created by projects such as Citrea, a bitcoin project requiring 100-byte payloads for certain functions. Writing this data elsewhere can force full node operators to process and validate a growing amount of non-financial transaction data.
Peter Todd confirmed on Stacker News that he submitted the proposal at the request of Chaincode Labs developer Antoine Poinsot, specifically because companies like Citrea are using less efficient methods due to the existing OP_RETURN limit. Citrea’s requirements would normally exceed OP_RETURN’s cap, encouraging them to use less desirable outputs and increasing the burden on bitcoin’s network.
Jameson Lopp, an investor in Citrea, denied on X that he had a conflict of interest in supporting the proposal. He stated: “The Citrea protocol does not benefit from this change at all! We’re just asking them nicely to please use OP_RETURN and not bloat the UTXO set.”
The debate over this proposed adjustment has led to what some are now calling the “OP_RETURN war,” with discussions ongoing across development forums, social channels, and GitHub. Issues of censorship, the role of non-financial data on the blockchain, and corporate interests have kept the change from being accepted. The topic continues to generate discussion in the wider bitcoin community.
✅ Follow BITNEWSBOT on Telegram, Facebook, LinkedIn, X.com, and Google News for instant updates.
Previous Articles:
- Solana Quietly Patches Bug Allowing Unlimited Token Minting
- Mastering Solana Volume Bots: A Step-by-Step Guide for Web3 Projects
- Brandeis Liu Lab Taps Theta EdgeCloud to Power AI Research
- El Salvador Plans Arrests of El Faro Journalists After Gang Exposé
- Ripple Donates $25M in Crypto to Support US Teachers, Education
