Bitcoin’s most important governance battles rarely come before public view, but the quiet opposition of two prominent figures — Blockstream co-founder Adam Back and Strategy founder Michael Saylor — to BIP 110 has suddenly raised the stakes for the network’s future. according to Original reportBoth have warned that the proposal, which seeks to monitor certain types of transactions, risks breaking the Bitcoin consensus and sets a risky precedent.
BIP 110 does not arise from a technical upgrade but from an ongoing dispute over unwanted transactions. The idea behind this proposal is to give nodes and miners a framework to invalidate transactions that are considered spam, essentially filtering out specific outputs before they enter the memory pool. But for a network built on unauthorized access and resistance to censorship, any rule that allows someone to determine what transactions are acceptable runs straight toward a philosophical fault line. The discussion is not hypothetical: for months, Bitcoin’s diary has been full of inscriptions and token traffic that some users call innovation and others call abuse. BIP 110 aims to tilt the scales toward one side of that argument.
This is not the first time Bitcoin has discussed transaction filtering. In 2014, developers considered limiting the OP_RETURN output to 40 bytes to limit data storage. The recent increase in registration, which has pushed fees to their highest levels in several years, has revived similar calls for spam filters. However, each time society eventually backed away from the strict restrictions, for fear of sliding into censorship. BIP 110 represents the latest revival of that instinct, and the same concerns are now echoed by voices like Back and Saylor.
Why spam monitoring becomes a governance crisis
The back was characteristically straight. He said BIP 110 attempts to monitor other people’s transactions and goes directly against Bitcoin’s core principles of decentralization and permissionlessness. Pak warned that forcing such a change on the network would only lead to a fork, a scenario in which the chain splits into competing versions, each with its own set of consensus rules. Saylor took a similarly outspoken stance, calling BIP 110 a move that would turn spam contention into a consensus change capable of invalidating some currently valid transactions and fee payments.
Saylor pointed out the dangers of that precedent. If the network starts making exceptions for certain types of transactions, it opens the door to a series of future demands — with each faction seeking to impose its own definition of legitimate use. He suggested that the outcome could erode the predictability that makes Bitcoin the primary asset in the unpredictable cryptocurrency market. Institutions that hold large positions on behalf of shareholders, such as strategy, rely on Bitcoin’s rule set remaining stable. Arbitrarily invalidating even a small subset of transactions would undermine the underlying value proposition of the asset as a neutral and predictable ledger.
The debate about spam filtering is not new. For years, parts of the community have argued that ordinal tokens and BRC-20 tokens — while technically valid — inflate the memory pool and increase fees for simple payouts. Supporters of BIP 110 see it as a cleanup tool. Opponents see something else: a permissible gatekeeper function that can be turned against any activity the vocal minority doesn’t like. Once you open that door, Buck and Saylor argue, you can’t close it. That’s why they both took a tough stance: not because spam is harmless, but because the cure may be worse than the disease.
Fork risk and market consequences
The most pressing concern is the chain split. The controversial fork doesn’t just create a new token; It forces exchanges, custodians and users to choose sides. This process breeds confusion, and confusion breeds selling. In past episodes, Bitcoin forks — whether it be the Bitcoin Cash fork or the SegWit2x showdown — have sparked volatility as traders hedged or exited positions. If BIP 110 advances against the wishes of a significant portion of the developer base and node operators, markets will face a similar replay, this time in an environment where… Institutional participation in on-chain assets Deeper than ever.
Moreover, the divisions are not just theoretical. The Bitcoin developer landscape is already expanding, as… Recent developer activity data It demonstrates this, prioritizing across Layer 2 scaling, security patches, and privacy improvements. Introducing a politically charged change such as divestiture can distract from more important work and drive some shareholders away. For a protocol that relies on a small circle of moderators, this is not a trivial threat. Some core developers may simply walk away from a project they see as increasingly divisive.
What remains uncertain
Despite notable opposition, it is unclear how strong BIP 110’s traction will be among the mining community and the wider contract. Miners, who collect fees, may resist anything that reduces their revenue stream. But some node operators may prefer a measure that promises to clean up what they see as wasteful on-chain activity. The debate also lies within a larger question about Bitcoin’s long-term governance model: Is bitcoin maximization — where the protocol barely changes — the safest path, or does the network need to have some ability to actively adapt to new forms of misuse?
Buck and Saylor are betting that the cost of intervention is much higher than the cost of living with some spam. Their stance reflects a growing view among long-term holders that Bitcoin’s credibility hinges not on perfection but on predictability. like Institutional capital is pouring into cryptocurrency infrastructure,The stability of the underlying layer ledger becomes non-negotiable. A governance battle drifting toward a crossroads would test this assumption much sooner than most market participants expect.
For now, the spats remain on developer mailing lists and forum threads. But the volume is rising. And when two of Bitcoin’s most famous engineers draw the line, the rest of the ecosystem must decide whether it cares enough about spam to risk splitting the chain — or whether this cure is worse than the disease.
