Bitcoin’s most important fights usually aren’t about price. They’re about who gets to decide what the network should allow, and BIP-110 has become a fresh flashpoint in that long-running battle.
- BIP-110 is a proposed Bitcoin soft fork, not an approved upgrade.
- The dispute is about neutrality, block space, and protocol governance.
- Michael Saylor calls Bitcoin's new BIP-110 proposal 'a bad” says the proposed cure is more dangerous than the condition.
BIP-110 is getting attention because it sits right on the fault line between Bitcoin as a neutral money network and Bitcoin as a system that should actively filter out what some people call spam. Supporters say it would protect node operators and keep Bitcoin focused on money. Critics say it crosses a dangerous line by turning a policy preference into consensus rules.
For readers less familiar with the jargon, a Bitcoin Improvement Proposal is a formal document suggesting changes to Bitcoin. A soft fork is a backward-compatible tightening of rules: upgraded nodes enforce stricter validity requirements, while older software can still recognize the chain. That sounds neat on paper. In practice, it’s where Bitcoin politics get sharp enough to cut glass.
The bips/bip-0110.mediawiki at master document describes BIP-110 as a proposed soft fork written by the pseudonymous developer Dathon Ohm, with original draft and technical advice credited to Luke Dashjr. The spec is described as complete, but the network upgrade has not been approved. So this is not a done deal. It’s a contested proposal, and a contentious one.
The backdrop here is Bitcoin Core 30’s relaxation of default OP_RETURN relay limits, according to the materials reviewed. OP_RETURN is a Bitcoin script operation used to embed small amounts of arbitrary data in a transaction. That policy shift has brought back the wider argument over whether Bitcoin block space should be used mainly for payments and settlement, or whether it should stay open to a broader set of data-bearing uses.
That distinction matters. Policy is what a node chooses to relay or prioritize locally. Consensus is what every valid block must obey. In Bitcoin, moving an issue from policy into consensus is not a minor tuning job. It is a constitutional amendment with miners, developers, node operators, businesses, and users all yelling at once.
According to the Bitcoin (BTC) Governance Risk Centers on BIP-110, Saylor materials reviewed, BIP-110 would temporarily limit a range of large data payloads and Taproot-related data storage methods. The reported changes include caps on certain script and witness fields, restrictions on some Taproot features, and other rules aimed at narrowing what kinds of transactions would remain valid after activation.
Supporters see that as the point. Their argument is blunt: Bitcoin block space is scarce, node operators bear real bandwidth and storage costs, and if the network is being used to stash arbitrary data, somebody has to pay for it. Their view is that Bitcoin should stay focused on money, not become a permanent public dump for digital clutter.
There is a fair economic case there. Every block has limited space. If non-payment data crowds out ordinary transactions, fees can rise and honest users can get squeezed. That’s not an abstract purity debate. It’s a cost problem.
But the critics’ objection is just as serious. If Bitcoin starts invalidating classes of transactions that were previously valid, the network is no longer just enforcing neutral rules. It is making judgment calls about acceptable use. That is where the alarm bells start ringing.
Guardians of Neutrality: Rejecting BIP 110 to Preserve says BIP-110 removes currently valid transaction functionality, could disrupt rare pre-signed workflows that span activation, and reduces technical optionality. It also argues that using consensus rules to suppress a category of valid use creates a precedent Bitcoin should avoid.
Saylor Says Bitcoin’s Biggest Threat Is Internal Governance put his warning plainly:
“Many Bitcoiners I respect support BIP 110. I understand and share their desire to protect Bitcoin, but believe the proposed cure is more dangerous than the condition. Here are 110 reasons why Bitcoin needs guardians of neutrality.”
That is not a rejection of the concern behind the proposal. It is a rejection of the remedy. Saylor’s point is that Bitcoin’s base layer should not become a moral referee for transaction types, even if some users find those transactions obnoxious, wasteful, or culturally cringe. Neutrality is the whole game, in his view, and once Bitcoin starts picking winners and losers at the consensus layer, the floor gets slippery fast.
Strategy also objects to the deployment design. Its materials say the proposal uses a modified BIP 9 process, lowers the miner-signaling threshold to 55 percent compared with BIP 9’s 95 percent, removes the conventional timeout and FAILED state, adds a mandatory-signaling period, and guarantees lock-in on the enforcing chain by a specified height. It also introduces an EXPIRED state after 52, 416 active blocks.
That’s not a small detail. Deployment mechanics decide whether a proposal looks like an orderly upgrade or a shove through the door. Critics see a recipe for conflict if broad economic support is missing. Supporters see a practical way to stop Bitcoin from being repurposed into a general-purpose data dump while everyone pretends fee pressure will magically solve the problem.
The proposal is also temporary, which is unusual enough to matter. According to the materials, it would apply for roughly one year after activation and then expire unless extended by a separate proposal. That makes it sound like a targeted intervention, but temporary fixes in Bitcoin have a habit of turning into permanent ideological scars.
There’s a real philosophical split underneath all this. One camp sees Bitcoin primarily as sound money and settlement. The other sees it as a neutral, permissionless fee market where valid transactions should remain valid, even if some people hate them. That old fight over “money only” versus “anything valid and fee-paying” is still alive. BIP-110 just drags it into the light and refuses to let it sit quietly in the corner.
For non-technical readers, a few more terms help. Taproot is a Bitcoin upgrade that improved privacy and scripting flexibility. Witness data is the part of a transaction tied to SegWit and Taproot, and it can be used more cheaply than older transaction data. Consensus rules define what is valid across the network; mempool policy is just a node’s local preference for what it relays. Bitcoin’s rulebook is not one book. It is a stack of books, and people keep arguing over which chapter should count as law.
Bitcoin BIP-110 Debate: Saylor Warns of Protocol Risks Amid the governance risk here is not that Bitcoin suddenly has a CEO in a bad mood. It’s that decentralized systems still need social agreement to change. When a proposal tries to turn “we don’t like this” into “this is invalid, ” it tests whether Bitcoin can stay neutral without becoming a landfill and whether it can stay decentralized without becoming indecisive.
Bitcoin BIP-110 Sparks Blockspace Fight Over Spam and that tension is the story. Not whether everyone likes inscriptions, data storage, or whatever the next creative use case turns out to be. The deeper question is whether Bitcoin’s base layer should be allowed to police use cases at all. If the answer is yes, then the network is no longer fully neutral. If the answer is no, then users who want to fill blocks with nonsense get to keep pushing the line, and node operators get to keep paying the bill. Bitcoin, as usual, offers no free lunch. Just a very expensive argument.
Key takeaways
-
Is BIP-110 already active on Bitcoin?
No. It is described as a proposed soft fork, and the network upgrade has not been approved. -
Why do supporters want BIP-110?
They say it would limit data-heavy uses, protect node resources, and keep Bitcoin focused on money and settlement. -
Why is Michael Saylor warning against it?
He argues the proposed cure is more dangerous than the condition because it weakens Bitcoin’s neutrality and pushes policy preferences into consensus rules. -
What makes this a governance risk?
It tests whether Bitcoin’s social consensus can support a rule change that many users see as a move from neutral policy into censorship by code.
The bigger lesson is simple: Bitcoin’s hardest debates are not technical trivia. They are battles over power, neutrality, and the right to use the network without asking permission. That mess is uncomfortable. It’s also the price of keeping a decentralized system from turning into a gated club with a blockchain sticker on the door.
