- Bitcoin Core maintainers have muted several developers amid a heated debate over OP_RETURN data limits.
- The censorship has sparked outrage within the Bitcoin community, with many criticizing it as contradictory to Bitcoin’s censorship-resistant values.
- The community remains divided with no clear consensus on whether to relax or maintain current OP_RETURN data storage restrictions.
Bitcoin Core maintainers have silenced multiple developers in a contentious dispute over blockchain data storage capabilities. The conflict erupted this week when developers were split on a proposal to modify the OP_RETURN operation code’s data storage limitations, leading moderators to mute prominent conservative voices including Luke Dashjr and Bitcoin Mechanic.
The dispute centers on Bitcoin’s OP_RETURN’s 83-byte datacarrier limit, with conservatives advocating for maintaining or further restricting the limit, while progressives push for relaxation. The conservative faction has raised concerns about corporate interests, spam vulnerabilities, and UTXO validation issues that could arise from expanded data storage capabilities.
The decision to mute these voices has ignited fierce backlash across the Bitcoin community. Giacomo Zucco called the moderators “absolutely out-of-control” and a “cabal of self-appointed politicians,” while Michelle Weekley called the censorship “antithetical to the ethos of bitcoin.”
Community Division Over Moderation Actions
Jameson Lopp, representing the progressive side of the debate, defended the moderators’ actions, characterizing them as necessary moderation rather than censorship. He claimed the muted developers had engaged in personal attacks and suggested that only non-contributors to Bitcoin Core were affected.
However, contrary to Lopp’s assertions, evidence shows that Bitcoin Mechanic, a long-time contributor to Core development, was among those muted, along with several other established contributors.
The Future of Bitcoin’s Data Storage Policy
The controversy has pushed the #FixTheFilters hashtag to trend on X (formerly Twitter), highlighting the community’s active engagement with this technical debate. Samson Mow summarized the situation, stating: “It’s supposed to be based on rough consensus. Anyone can see that there is no consensus on relaxing OP_RETURN limits.”
This incident has raised fundamental questions about governance in Bitcoin’s development process, particularly highlighting the tension between centralized control of code repositories and the cryptocurrency’s decentralized ethos. As one observer described it, the situation represents “concerted community sabotage” at a time when technical consensus-building is most needed.
✅ Follow BITNEWSBOT on Telegram, Facebook, LinkedIn, X.com, and Google News for instant updates.
Previous Articles:
- Bitcoin to Surpass Gold, Hit $1M by 2029, Says Bitwise Researcher
- Trump Media & Technology Group relocates incorporation from Delaware to Florida
- Crypto Exposure Boosts Risky Investment Behavior, UCD Study Finds
- Public Companies Trading at High mNAV Ratios as Crypto Speculation Returns
- MultiBank signs record $3B real estate tokenization deal with UAE’s MAG
