Michael Saylor isn't worried about Bitcoin's block space being filled with inscriptions. He's worried about what happens when 55% of miners can rewrite the rules. That's the real story behind his 110-point takedown of BIP-110.
Bitcoin's consensus layer has always been its moat. The promise of immutability. The guarantee that no single group can change the rules without near-universal agreement. BIP-110, a proposal to restrict certain script and witness data to curb inscription bloat, seems like a narrow technical tweak. But its activation design—a 55% miner threshold with no timeout or failed state—threatens that fundamental guarantee.
Skepticism isn't about opposing change. It's about weighing precedent. And BIP-110 sets a dangerous precedent: that a simple majority of miners can force a consensus change onto the rest of the network.
Context: The Proposal and the Mechanism
BIP-110 targets seven specific areas of Bitcoin's script and witness structure. It caps script public key lengths, disables certain Taproot paths, and restricts the number of witness items. The stated goal: reduce the data footprint of non-financial transactions like Ordinals inscriptions. On the surface, it's a response to a real problem: blocks are filling with data that some argue degrades Bitcoin's utility as a store of value.
But the surface is misleading. The activation mechanism is the real story. BIP-110 proposes a threshold of 55% of miners signaling in a difficulty adjustment period. No fail state. No automatic timeout. If 55% of miners signal support, the new rules activate after a grace period. If they don't, the proposal lingers indefinitely. It's a design that deliberately lowers the bar for consensus change.
Based on my experience auditing governance mechanisms in 50+ ICO whitepapers, I've seen this pattern before. Low thresholds are sold as efficiency gains. In practice, they become attack vectors. The absence of a 'failed' state means a minority of 45% can block activation indefinitely through inaction, creating deadlock. Or worse, the 55% can activate and force the rest to either comply or fork.
Core: Why This Matters – Governance as the Underlying Asset
Bitcoin's value as a digital commodity is not just in its fixed supply. It's in the predictability of its rules. The market prices in the assumption that changes require overwhelming consensus. Liquidity doesn't flow into systems where rule changes can be forced by a simple majority. It flows into systems where the rules are stable.
I've tracked liquidity flows across crypto cycles since 2017. The pattern is clear: capital gravitates toward assets with credible governance. Bitcoin's 95% threshold for BIP-9 upgrades was a feature, not a bug. It ensured that any change had broad community buy-in. BIP-110's 55% threshold is a regression to the mean—toward the kind of governance that plagues proof-of-stake networks where a few validators can collude.
Consider the downstream effects. If BIP-110 passes under this mechanism, what stops the next proposal? A 55% threshold to cap block rewards? To change the halving schedule? To freeze certain addresses? The door would be open. The narrative of Bitcoin as 'digital gold'—unchangeable, predictable, beyond the reach of politics—would evaporate.
The Contrarian Angle: The Proposal May Be Rational, But the Mechanism Isn't
Some argue that BIP-110 is a necessary defense against data bloat. They claim that inscriptions are a parasitic use of block space, driving up fees for legitimate transactions. They point to rising mempool congestion and argue that something must be done.
I disagree with the method, not the diagnosis. The real solution is market-driven: higher fees naturally discourage low-value transactions, and Layer 2 solutions like Lightning Network or RGB can absorb the legitimate use cases. Saylor himself advocates for non-consensus solutions: node operators can choose to filter certain transactions, and application developers can migrate to layers that better serve their needs.
But here's the blind spot: the supporters of BIP-110 underestimate the long-term cost of weakening Bitcoin's immutability narrative. Even if the proposal is technically sound, the mechanism taints it. The market will see a precedent. Every future governance debate will be framed around this lowered threshold. The question won't be 'is this change good for Bitcoin?' but 'can we get 55% of miners to agree?' That is a fundamentally different conversation.
In my analysis of institutional adoption metrics, ETFs and large holders value stability above all. The approval of spot Bitcoin ETFs in 2024 was a signal that traditional finance sees Bitcoin as a stable, predictable asset. BIP-110, if passed under a flawed mechanism, would undercut that perception. Liquidity doesn't wait for governance debates to resolve; it moves to where rules are stable.
Takeaway: The Real Risk Is the Precedent, Not the Proposal
The probability of BIP-110 passing is low. Saylor's opposition, combined with likely pushback from core developers and the broader community, will likely kill it or force a redesign. But the debate itself is a stress test for Bitcoin's governance.
Watch three signals: first, miner signaling—if any major pools publicly support the 55% threshold, that's a red flag. Second, core developer statements—if Bitcoin Core maintainers reject the mechanism, the proposal is dead. Third, the hash rate distribution—if miners that support it control a significant share, the market will start pricing in governance risk.
Forward-looking: If BIP-110 fails, it reinforces the status quo. Bitcoin remains a conservative, high-threshold system. If it gains traction, prepare for volatility. Not because of the content of the proposal, but because of what it signals about the willingness to change the rules by a simple majority.
Bitcoin's value proposition is its predictability. Any move to make governance easier erodes that. Saylor's opposition isn't about inscriptions—it's about preserving the very foundation that makes Bitcoin a store of value. Skepticism isn't just healthy; it's essential.