The fight over Bitcoin proposal BIP-110 is back in public view. A post from Mr.Hodl on X placed Roger Ver’s 2019 criticism of BTC censorship next to fresh complaints from GrassFedBitcoin about how BIP-110 is being treated in discussion channels, pushing the issue beyond one proposal and back into a wider argument over how Bitcoin handles dissent.
The first screenshot in the post showed Ver’s earlier claim that BTC had failed its censorship-resistance standard by censoring parts of its own community. The second showed GrassFedBitcoin arguing that critics of BIP-110 should engage directly if they believe the proposal is flawed. That account said several Bitcoin discussion spaces had become difficult places for supporters to defend the idea.
Moderation complaints revive a broader governance dispute
GrassFedBitcoin also claimed that bitcointalk had gone quiet, GitHub posts were being marked as spam, and Reddit accounts were being banned for discussing Bitcoin Knots or BIP-110. The same account said the BIP repository still allowed the proposal to be discussed and merged. Those allegations were not confirmed by the named platforms in the material reviewed. Even so, they were enough to pull BIP-110 back into a larger conversation about governance, social pressure, and who gets heard in Bitcoin’s public forums.
The argument quickly moved beyond moderation mechanics. By pairing the current dispute with Ver’s older remarks, Mr.Hodl gave the debate a cultural edge, linking BIP-110 to a long-running suspicion inside Bitcoin circles that some venues filter out unpopular views rather than defeating them in open argument.
Adam Back says silence is not censorship
Blockstream CEO Adam Back rejected the idea that BIP-110 is being suppressed by a coordinated campaign. His view was blunt: the proposal is not being blocked in secret, it is being ignored because many people have already reviewed it and decided against it.
Back wrote that it was “being ignored because it’s a stupid idea.” He added that people were tired of revisiting the same points after debating them last year. In his telling, no conspiracy is needed to explain the lack of momentum. If supporters still want those rules, they can fork away from Bitcoin.
That response fits a position held for some time by parts of the Bitcoin developer and infrastructure community. Critics of BIP-110 argue that using consensus rules to restrict transaction content would weaken Bitcoin’s neutrality. The dispute is not only about code. It is also about who gets to define the acceptable boundaries of the protocol.
BIP-110 is aimed at non-monetary transaction data
BIP-110 seeks to limit arbitrary data stored in Bitcoin transactions. As described in the report, it targets activity associated with inscriptions, Ordinals, and Runes by restricting certain large data fields. Supporters say this would protect Bitcoin’s monetary function and reduce the burden on node operators.
People backing the proposal argue that block space should not drift into a general-purpose data storage layer. They want Bitcoin’s on-chain capacity used primarily for monetary transfers rather than carrying large amounts of unrelated data. That line of argument has remained active since inscription-driven traffic sharpened debates around fees, node costs, and block space use.
Opponents focus on the downside. They warn that BIP-110 could create bigger problems than the activity it is trying to curb, including breaking existing use cases, freezing some transaction outputs, or splitting the network if only a limited group tries to enforce the rule. Fork risk remains the central fault line.
Low support keeps activation uncertain
The latest account says BIP-110 has low node support and no clear backing from major mining pools. That leaves the proposal facing a practical obstacle: unless support changes before the proposed enforcement date, activation looks difficult. Social media attention can revive the argument, but it cannot substitute for node, miner, and market support.
The divide is now clear. Supporters present BIP-110 as a way to defend Bitcoin’s monetary purpose, while opponents describe it as a risky effort to police transaction content. Back’s comments pulled the issue back toward support levels and technical legitimacy. Mr.Hodl’s post pulled it toward the old question that never fully disappears in Bitcoin: is the community rejecting a weak proposal, or narrowing the space in which opposing views can compete?