Michael Saylor didn't just criticize BIP 110. He deconstructed it. Calling the proposal a 'rough proxy for an unmeasured cost' before a live audience, the MicroStrategy chairman didn't just signal disagreement—he framed the entire debate as a test of Bitcoin's fundamental neutrality. This isn't a technical argument over transaction limits. It's a governance stress test.
Tracing the alpha through the noise of consensus.
The proposal itself is deceptively simple. BIP 110 aims to impose strict data per block limits—capping script sizes, Taproot control blocks, and undefined witness versions—to reduce DoS attack surfaces and keep node operation costs low. Superficially, it reads like responsible protocol hygiene. But the surface code never tells the full story.
Context demands a look at Bitcoin's historical soft fork pattern. From SegWit to Taproot, each upgrade expanded utility or improved efficiency. They passed with overwhelming consensus—typically over 90% miner signaling. BIP 110 flips this trajectory. It doesn't enable anything new. It restricts. And its activation threshold is a contentious 55%, far below the traditional 95%. This is not the Bitcoin I verified against formal logic back in 2017, when I spent months manually auditing the Ethereum whitepaper's state transition function. That Bitcoin was built on conservative consensus, not bare-minimum signaling.
The core of this debate is a fundamental mismatch between the problem and the solution. The problem: node operators face rising costs from data bloat and potential spam. The solution: hard-code arbitrary limits. But as Saylor pointed out, the cost being targeted has never been rigorously measured. And the proposal bundles multiple, unrelated restrictions into one package—a classic governance tactic to slip controversial changes under the radar. During the Terra collapse in 2022, I saw the same pattern: complex rule changes sold as minor fixes, masking deep structural flaws. BIP 110 reeks of the same proxy logic.
The code doesn't lie, but the intentions behind the proposal do.
Digging into the technical mechanics reveals deeper risks. The most damning consequence of BIP 110 is its impact on future innovation—specifically BitVM, a method to enable Turing-complete computation on Bitcoin without altering the consensus layer. BitVM opens doors to trust-minimized bridges, complex DeFi, and even verifiable AI inference. BIP 110, by restricting undefined witness versions and script sizes, effectively closes those doors before they're fully open. This isn't just a conservative upgrade; it's a preemptive strike against an entire direction of research. From my EigenLayer analysis days, I learned one hard truth: restrictive base layers kill the ecosystems built on top of them.
Furthermore, the activation mechanism itself is a governance landmine. The 55% threshold is dangerously low. In a network where a handful of large mining pools can coordinate quickly, this opens the door for a vocal minority to lock in rules that the majority of node operators and users oppose. The social layer may reject it, but the precedent of a low-threshold activation weakens Bitcoin's greatest asset: its predictability. Arbitrage isn't just for markets; it's for governance. If the cost of pushing controversial rules drops, expect more proposals to test the floor.
Now the contrarian angle. Perhaps BIP 110 has a point. Node operating costs are real, and spam attacks like the 2023 ordinals inscription wave did congest blocks. A small, data-capped block space might keep Bitcoin lean and resistant to censorship. But is the trade-off worth it? The answer lies in the numbers. The data bloat from the ordinals frenzy was manageable—most nodes barely felt the strain. And the 'solution' of capping script sizes kills the very innovation that gave rise to Bitcoin's first non-financial use cases. If Bitcoin wants to remain digital gold, it must also remain a playground for experimenters. Locking down the protocol now is betting against future problems we can't yet envision. That's not conservatism—it's myopia.
Every rug pull has a pre-written script.
The real narrative here isn't about block limits. It's about who controls the direction of Bitcoin's evolution. Saylor's position—favoring a market-based fee and voluntary relay strategy—isn't just technically sound; it's philosophically aligned with Bitcoin's ethos of permissionless innovation. By opposing BIP 110 so publicly, he's signaling that protocol neutrality demands active defense, not passive acceptance. Adam Back's prediction that the proposal will 'stall in weeks' suggests even the technical elite see its foundations as weak.
Decentralization is a spectrum, not a switch. BIP 110 tests how much centralization of control we're willing to accept in the name of efficiency.
Takeaway: The signal to watch is not the 55% activation threshold—it's the social layer's response. If miners signal support despite developer and community opposition, we'll witness a governance crisis that shakes confidence more than any market correction. If the proposal dies quietly, Bitcoin's governance emerges stronger for having had the debate. But the ghost of this proposal will linger. Future upgrades must now prove they respect the boundary between stewardship and overreach. The code is the law, but the narrative is the constitution. And this narrative is still being written.
For now, BIP 110 is a textbook case of what happens when a 'fix' ignores the opportunity cost of innovation. The market may not price this immediately, but the alpha is clear: Bitcoin's long-term value depends on its ability to remain a neutral, extensible platform. Proposals that trade that neutrality for temporary relief are not improvements—they are liabilities.
