Michael Saylor published 110 reasons to oppose BIP-110. But the real fracture isn't in the script limits—it's in the ledger of Bitcoin's governance itself. As a macro strategy analyst who has spent a decade dissecting the intersection of protocol design and financial stability, I see this not as a technical debate about ordinals or data bloat, but as a stress test of Bitcoin's most sacred asset: its immutability. Fractures in the ledger reveal what hype obscures—and the hype around "fixing" block space usage masks a far deeper systemic risk.
Context: What Is BIP-110 and Why Now?
BIP-110, proposed in mid-2024, is a set of seven consensus-level restrictions on Bitcoin script and witness data. It aims to limit the use of transactions that embed arbitrary data—commonly associated with inscriptions, ordinals, and other non-financial uses of block space. The proposal is a reaction to the steady increase in block size driven by such activities, which some argue degrades the user experience for value transfer. The seven restrictions include caps on script public key lengths, witness item counts, taproot leaf versions, and more. On the surface, it appears as a technical cleanup.
But the mechanism for activation is where the true story lies. BIP-110 proposes a 55% miner signaling threshold—not the historical 95% required by BIP-9 for soft forks. And critically, it lacks a FAILED state. Once miners signal support, there is no timeout, no off-ramp for continued disagreement. This design is a radical departure from Bitcoin's conservative upgrade tradition. Saylor's opposition speech, delivered via a 110-point thread, focused not on the technical restrictions but on this governance design: "The proposed governance solution is more dangerous than the problem."
Core: The Hidden Danger Is Governance, Not Script Limits
Let me be clear: the technical restrictions of BIP-110 are secondary. They can be mitigated through non-consensus means—node policies, wallet defaults, Layer2 solutions. The real danger is the precedent that a 55% miner majority can force a consensus change on the network. This is a fracture in the ledger that no software patch can fix.
From my experience auditing 40+ ICO whitepapers in 2017, I learned that tokenomic sustainability is not about the features but the incentives. In 2017, projects with soft caps and low thresholds for change often failed when market conditions shifted. Similarly, Bitcoin's value proposition depends on the near-absolute certainty that the base layer will not change unless there is overwhelming support. The 95% threshold in BIP-9 was not arbitrary; it was a guardrail against capture by a simple majority.
Consider the numbers. In 2017, SegWit activation required 95% miner signaling over a 2016-block retarget period. The process took over a year and intense community coordination. BIP-110's 55% threshold effectively means that if 55% of the hashrate signals support, the change activates—regardless of whether the remaining 45% agree. That 45% could include major mining pools, core developers, and the majority of economic nodes. The result is not consensus but coercion.
The chart is the symptom, not the disease. The symptom is the data bloat on Bitcoin. The disease is the proposal's mechanism design. Saylor's 110 reasons are a post-mortem of a crisis that hasn't happened yet—but he has seen this pattern before. I saw it too during the Terra collapse. When algorithmic stablecoins failed, it wasn't because of a technical bug in the code; it was because the governance structure allowed leveraged positions to spiral without circuit breakers. BIP-110's governance lacks a circuit breaker. There is no FAILED state, no automatic reset if consensus is not robust. Once the threshold is crossed, the network either accepts the change or splits.
Deep Dive into the Seven Restrictions
Let me be precise about the technical scope. BIP-110 restricts: - Script public key length (max 34 bytes) - Witness items count (max 100) - Witness script length (max 520 bytes) - Taproot leaf version (only version 0xc0 allowed) - Taproot output size (only 32-byte key path) - OP_RETURN payload size (max 80 bytes) - Standardness checks for specific opcodes
Each of these restrictions targets a specific vector used by ordinal inscribers and other data-heavy applications. For example, limiting taproot leaf versions to 0xc0 restricts the use of tapscript for complex smart contracts, effectively banning most non-financial taproot usage. This would break protocols like RGB and Taproot Assets that rely on taproot leaf scripts for asset issuance.
But here is the nuanced point: these restrictions can be implemented via node policy or wallet defaults without a consensus change. The Bitcoin Core team could simply update the default relay policy to reject transactions that exceed these limits. This would achieve the same effect without altering the consensus rules. Saylor explicitly advocates for this non-consensus approach. So why propose a hard consensus change? The answer lies in enforcement: consensus rules are binding for all miners, while policy is optional. BIP-110's authors want to force compliance on the entire network, including miners that may profit from inscription transactions.
This brings us to the economic incentives. In the current bull market, with high transaction fees from inscriptions, some miners earn a significant portion of their revenue from such transactions. Data from Q2 2024 shows that inscription-related fees accounted for 15-20% of daily miner revenue at peak. A consensus ban would remove that income stream for all miners. The 55% threshold could be seen as a way for the majority of miners to impose a revenue reduction on the minority—a form of market capture. Saylor, as the largest public BTC holder, has a clear interest in preserving the network's stability, but his opposition also aligns with maintaining the fee market for all miners.
Contrarian: Is Saylor's Opposition Self-Serving?
A cynical reading of Saylor's 110 reasons is that he is protecting his $10 billion+ BTC position from any change that could introduce volatility or chain split risk. As a corporate holder, MicroStrategy benefits from Bitcoin's status quo—an immutable asset with no governance debates. Any proposal that tests consensus introduces uncertainty, which could depress the premium that institutions pay for Bitcoin compared to other assets.
But the truth is more nuanced. Saylor's argument is structurally sound: a low-threshold governance change is a systemic risk that outweighs any benefit from restricting inscriptions. I saw the same dynamic during the 2022 Luna collapse. The proposal to change the burn mechanism in Terra (a governance vote) was passed with a simple majority, which accelerated the death spiral. The chart is the symptom, not the disease—the disease was a governance structure that allowed a few large holders to alter the protocol in a crisis.
Consensus is a lagging indicator of truth. The market's reaction to BIP-110 has been muted so far—Bitcoin price has not materially moved. But the truth of the governance risk will only become apparent when a future proposal uses this precedent to push through a more contentious change. The 55% threshold is a cannon aimed at the future.
Takeaway: Positioning for the Cycle
Where does this leave investors? The most likely outcome is that BIP-110 fails. Saylor's opposition, combined with likely pushback from core developers, will stall the proposal. The 55% threshold will not be reached. But the discussion itself has already changed the narrative. The market is now aware that Bitcoin's governance is being tested. This is a positive for the long-term value proposition of Layer2 solutions that can absorb the inscription demand without congesting the base layer. Expect increased developer activity on Lightning, RGB, and Ark.
Watch the miner signaling charts. If any major pool signals support for BIP-110, that will trigger a liquidity event as exchanges prepare for potential chain splits. But I believe the community will reject this proposal, reinforcing Bitcoin's conservative upgrade path. The cycle position: long on infrastructure that supports scalable non-consensus solutions, short on protocols that depend on unrestricted Bitcoin script space. The ledger fractures, but the truth remains: consensus is the only anchor in a sea of hype.
_Fractures in the ledger reveal what hype obscures._