The BIP-110 Trap: Why Michael Saylor's Objection Exposes a Deeper Flaw in Bitcoin's Governance
The data suggests that the proposed activation mechanism for BIP-110 is more dangerous than the seven consensus changes it enforces.
Michael Saylor, the most vocal institutional bull on Bitcoin, has publicly declared his opposition to BIP-110. His 110-point manifesto, published on July 10, 2024, is not a technical rebuttal; it is a systemic warning. From my experience auditing ICO whitepapers in 2017, I learned that the most dangerous propositions are not the ones with bad math, but the ones that change the rules of the game for the sake of a perceived utility. BIP-110 is precisely that: a proposal to tighten Bitcoin’s consensus rules to curb data storage, specifically the inscription of large data (like Ordinals) onto the blockchain.
But the proposal’s content—limiting script public key lengths, restricting specific Taproot paths, and capping witness data items—is not the real story. The real story is the governance mechanism proposed to activate these changes: a mere 55% miner threshold, with no defined ‘FAILED’ state. This is a break from Bitcoin’s conservative upgrade tradition, which historically required 95% miner support via BIP-9. Who you are in this debate matters less than what the precedent could become.
Following the code where the humans fear to tread, we must examine the architecture of value in a trustless system. Bitcoin’s value proposition is built on immutability and predictable rules. The ‘don’t mess with the base layer’ philosophy is not Luddism; it is a structural requirement for a global, sovereign-grade asset. Saylor, leveraging his experience as the CEO of a company holding over 200,000 BTC, is not arguing about byte limits. He is arguing about control. He is asking: if a minority of 55% can force a consensus change, who is to say the next proposal won’t be a tax on coinbase rewards or a reallocation of the subsidy?
The Governance Defect: A 55% Threshold Without a Safety Valve
Deconstructing the myth of utility in the BIP-110 narrative reveals a governance framework that is structurally vulnerable. Bitcoin’s strength has always been its requirement for overwhelming consensus. The BIP-9 standard required 95% of miners within a retarget period to signal support before activation, with a built-in FAILED state that prevents the proposal from being stuck in a limbo of non-consensus. BIP-110 removes both safeguards. It proposes a simple majority of 55% and no expiration mechanism.
From my work modeling the LUNA crash in 2022, I learned that feedback loops in incentive structures are fragile. A 55% threshold is a capture threshold. It means a coordinated group of mining pools representing just over half the hash rate could force a change against the will of nearly half the network. In a liquid market, this is not merely theoretical. A large, state-backed mining pool, a consortium of institutional miners with a specific agenda, or a temporary coalition of pools chasing a particular transaction fee market could exploit this.
The architecture of value in a trustless system relies on the difficulty of change. By lowering the bar for consensus changes from 95% to 55%, BIP-110 creates a new attack surface: governance attacks. This is not a hypothetical risk. If the proposal activated, and the remaining 45% of miners refused to enforce the new rules, the network would split into two chains: one following the new BIP-110 rules (with smaller blocks, limited scripts) and one maintaining the current rules. This is a chain fork, a scenario that breaks the very concept of a single, unified Bitcoin. Saylor’s 110-point argument is, in essence, a 110-point list of ways this governance failure could cascade into a systemic crisis.
Charting the entropy of digital scarcity, we see that the technical merits of BIP-110 are secondary to its governance implications. The proposal’s seven restrictions are a reaction to the ‘inscription problem,’ where users embed large files (images, text, code) into the witness data of SegWit and Taproot transactions. This has increased block sizes and, for some, represents a ‘noise pollution’ on the sacred digital ledger. Saylor’s preferred solution is not consensus enforcement but market-based disincentives. He advocates for a ‘non-consensus approach’ where node operators and wallet developers can choose to reject transactions with large witness data. This is a subtle but critical distinction. It puts the onus on the users, not the protocol.
From my 2020 study of Uniswap V2 liquidity flows, I learned that market mechanisms are often more efficient than protocol-level restrictions. A disincentive mechanism—like a higher fee market for large transactions—is a price signal. It allows organic adjustment. A consensus-mandated limit is a stick, not a price signal. It kills the behavior outright, but it also kills the innovation that might have grown around that behavior. The Ordinals protocol, Taproot Assets, and RGB are all building on these script paths. Limiting them via BIP-110 is a pre-emptive strike on a nascent ecosystem.
The Contrarian Angle: The ‘Do Nothing’ Risk is Higher Than the ‘Do Something’ Risk
My LUNA analysis taught me that the most dangerous assumption is that ‘safe’ means ‘unchanging.’ The contrarian view to Saylor’s objection is that doing nothing is itself a risk. The current design allows for unbounded block growth, at least in theory. If a coordinated effort to inscribe the entire internet onto Bitcoin occurred, it could cause a catastrophic increase in block size, making it impossible for consumer-grade nodes to validate the chain. This is a real risk to decentralization.
However, I contend that the ‘do nothing’ risk is far less dangerous than the ‘do something’ risk of BIP-110’s governance. The market is a better filter than a committee. If block sizes become a problem, users and node operators will adapt. They will prioritize blocks with higher fees, reject large transactions, and adopt Layer 2 solutions like Lightning Network and RGB even faster. The market has a natural defense: capacity. A 4MB block is already more than enough for financial transactions. The inscription ‘problem’ is a human values problem, not a technical one. It is about what the blockchain is for. And forcing a change on 55% of miners to solve a values problem is the kind of hubris that breaks systems.
Saylor’s objection is also a signal to the development community. Following the code where the humans fear to tread, I see a clear warning: do not let the immediate solution (a 55% threshold) become a permanent precedent. The proposal lacks the necessary checks and balances that protect Bitcoin’s most important feature: predictability. The lack of a FAILED state means that if 55% signal, and then later 45% signal against, the proposal could remain in a state of limbo, creating a chronic governance crisis. This is a classic ‘liquidity trap’ for protocol development.
Who Benefits from Lowering the Bar?
The architecture of value in a trustless system is about making certain actions prohibitively expensive. Governance attacks should be expensive. A 95% threshold is expensive to achieve. It requires near-universal consensus. A 55% threshold is cheap. It can be bought.
Who would benefit from a cheaper governance threshold? Entities with a high degree of coordination and a specific agenda. A consortium of large mining pools from a single jurisdiction could easily coordinate to pass future BIPs. A group of institutional holders that want to add a ‘recovery key’ to the protocol could do so. The threat is not the current BIP-110 content, but the future BIPs that will be proposed with the same, now-normalized, 55% activation mechanism. This is the ‘open the door a crack’ risk.
My experience reverse-engineering the Terra/LUNA failure points in 2022 showed me that the most catastrophic failures are not from a single bad actor, but from a cascading series of incremental decisions that lowered the bar for acceptable risk. Each decision seemed logical in isolation. BIP-110’s governance changes are the same: they seem like a reasonable efficiency improvement, but they are lowering a fundamental security barrier.
The Takeaway: What Happens When the BIP Fails?
The most likely outcome, given Saylor’s public opposition and the likely resistance from core developers (who have historically favored the 95% rule), is that BIP-110 will fail to reach activation. But this outcome is not a victory for conservatism; it is a signal of a divide. The debate will not end. It will fester.
The rejection of BIP-110 will likely push advocates for ‘clean blocks’ to build their own tools—custom nodes that reject large inscriptions, for example. This is a healthy, organic outcome. But it also means the core network will continue to allow these uses. The ‘pragmatists’ who want a more programmable, data-rich L1 will feel disenfranchised. The ‘purists’ who want a gold-like store of value will feel vindicated but wary of future attempts. The risk to the network is not the change; it is the widening of the ideological split.
For the market, this is a non-event in the short term. The price of Bitcoin will not drop because of a governance debate. But for the long-term institutional investor who reads my work, this is a signal. Deconstructing the myth of utility in the NFT boom, we saw that chasing the hype of ‘use cases’ on the base layer created a fragile ecosystem. BIP-110 is the same, but for governance. The system is not broken yet. But the proposal reveals a vulnerability that must be watched.
The next narrative is not about BIP-110 itself. The next narrative is about Layer 2. As market mechanisms deal with the data problem, demand for efficient Layer 2 solutions—Lightning, RGB, Ark—will increase. This is where the risk and opportunity lie. The bitcoin network is a settlement layer. It is not an application platform. Any attempt to treat it like one, whether through contentious proposals or market-driven inscription hype, will eventually create stress. The question is how that stress is resolved.
Charting the entropy of digital scarcity, the only certainty is that the code does not lie, but the narratives do. The narrative that BIP-110 is a simple technical fix is the lie. The truth is it is a test of how far Bitcoin is willing to drift from its founding principles. My 50-page paper on the LUNA collapse concluded with the same warning: the most dangerous thing is not the failure of a system, but the failure to understand the system’s own fragility. BIP-110’s governance mechanism is a fragile point in an otherwise robust architecture. Saylor’s objection is not about block size; it is about the soul of the network. And in a trustless system, the soul is everything.
Follow the Code
I will be monitoring three signals over the next 180 days: 1) The GitHub activity on the bitcoin/bips repository for BIP-110. A single negative comment from a core contributor like Pieter Wuille or Greg Maxwell can kill it. 2) The actual miner signals on the network. If we see 30% of blocks signaling for BIP-110, the market should start pricing in a governance risk premium. 3) The lock-in of Layer 2 solutions. If Lightning capacity grows by more than 50% in Q3, it is a market-based signal that the network is adapting to the data problem without a consensus change.
The quiet before the storm is the most dangerous time to adjust your sails. For now, the architecture holds. But the repair bill has been presented, and the item on it is not a technical fix; it is a governance one.
