The Ghost in the Machine: Why Michael Saylor’s 110 Reasons Against BIP-110 Are a Warning, Not a Negotiation
Hook: The 110 Reasons That Shook the Consensus
On a Tuesday afternoon that felt like any other in the sideways market of mid-2026, Michael Saylor, the executive chairman of MicroStrategy and Bitcoin’s most vocal institutional champion, did something that, on the surface, looked like standard Twitter clutter. He posted a thread. But this wasn’t a thread about the latest orange coin price pump or a quarterly earnings call. It was a list of 110 distinct reasons why he opposed a single Bitcoin Improvement Proposal: BIP-110. The list was exhaustive, obsessive, and borderline paranoid. It didn't just critique the proposal’s technical details; it sought to dismantle the very mechanism by which it would be activated. As I read the thread, scrolling past points about "55% miner thresholds" and "lack of a FAILED state," I felt a familiar chill. This wasn't just a disagreement about data blocks. This was a war over the soul of the machine itself.
Beneath the surface, a more profound schism was fracturing the very foundations of the digital gold narrative. It wasn't immediately obvious to the casual observer. But for those of us who’d spent years auditing the philosophical code beneath the technical code, Saylor’s thread was a declaration. He wasn't just saying "no" to a rule change. He was saying that the very process for changing the rules was a backdoor for capture. The market, predictably, yawned. BTC price barely moved. But the signal was clear: the governance of Bitcoin was entering a new, dangerous phase, and the guardian of the treasury was ringing the alarm.
Context: The Proposal and Its Provocation
To understand the fury, you must understand the threat. BIP-110, officially titled a proposal to "limiting data storage," is a response to a persistent anxiety within the Bitcoin community: the explosion of non-financial data on the base layer. For years, the debate has simmered. The rise of Ordinals, inscriptions, and BRC-20 tokens turned Bitcoin blocks into a digital junkyard of JPEGs and text strings. For purists, this was a desecration of the sacred ledger, a waste of scarce block space that should be reserved for high-value financial settlements. For innovators, it was a sign of a living, breathing, expanding ecosystem. BIP-110 was the hammer designed to smash this debate.
The proposal, as described in the thread and inferred from sparse public documentation, seeks to impose seven distinct consensus-level restrictions on what can be included in a Bitcoin transaction. These include limiting the length of script public keys, restricting the use of certain witness data fields, and specifically disabling several alternative paths within the Taproot upgrade that were designed to enable complex smart contracts. In essence, it’s a surgical strike against the tools that made inscriptions possible. The core insight of BIP-110 is simple: if you can’t write it in a way the protocol understands, you can’t store it. The proposal aims to enforce this via a novel activation mechanism: a 55% miner signal threshold, without a predetermined "FAILED" state for the proposal itself.
This is where Saylor’s campaign found its ammunition. The technical solution, he argued, was a red herring. The real problem was the weapon itself: a governance process that could, for the first time, change Bitcoin’s consensus rules with a simple majority of mining power. It was a break from the tradition of BIP-9, which required 95% miner signaling over a retarget period. It was, in effect, a new paradigm for how Bitcoin could be changed.
Core: The Architecture of the Alarm
Saylor’s 110 reasons can be distilled into three core technical and philosophical arguments. My own experience auditing the first 50 Ethereum ICO tokens in 2017 taught me that most catastrophic failures aren't bugs; they are logic flaws. BIP-110’s logic is dangerously flawed.
1. The 55% Threshold is an Invitation to Capture.
The proposal’s activation mechanism is the single most dangerous element. Setting a signal threshold at 55% is a deliberate choice. It’s high enough to be a "majority" but low enough to be achievable by a coordinated cartel of large mining pools. It creates a situation where a minority of hash power (45%) can be forced to follow a rule they fundamentally oppose. In a system designed for censorship resistance, this is a built-in vulnerability. The map is not the territory, but the map became the territory. The 55% threshold doesn't just allow change; it actively encourages a hostile takeover if a coalition of pools sees a financial benefit in the new rules. Saylor’s underlying fear is that this creates a "liquidation event" for the immutability narrative.
2. The Absence of a "FAILED" State is a Constitutional Error.
This is the most subtle but devastating point. In previous BIPs (like BIP-9), if a proposal didn't reach the threshold by a certain deadline, it transitioned to a "FAILED" state. This signaled to the network that the upgrade was dead, allowing the community to move on. BIP-110, as described, has no such automatic timeout. This creates a perpetual activation risk. A coalition of pools could, in theory, signal for it in a future epoch, years after it was supposedly abandoned. This isn't a technical bug; it's a governance vaporware. It allows a minority to perpetually hold a sword over the network, ready to activate the change at a moment of weakness or low hash. I have seen this pattern in protocol design for NFTs. It creates permanent uncertainty, which is the enemy of long-term capital formation.
3. The Technical Restrictions are a Slippery Slope.
While Saylor focuses on governance, the technical restrictions themselves are poorly designed. The proposal is a blunt instrument. By banning certain Taproot paths, it doesn't just kill inscriptions; it threatens legitimate use cases like RGB (a smart contract system) and Taproot Assets (an asset issuance protocol). It’s the equivalent of banning all vehicles to stop a single speeding car. The network effect of Bitcoin relies on its ability to be a foundation for other things. This proposal is a wall built on that foundation. It’s a solution that destroys the very thing it is trying to protect: the utility of the block space. It’s a technical step backward that would require downstream users to rebuild their infrastructure for a minimal gain.
My own work in the DeFi Summer and the subsequent bear market taught me that protocols survive not by being rigid, but by having the right kind of flexibility. BIP-110 is not flexibility; it’s a forced constraint that ignores the market’s ability to solve the problem naturally. It assumes the protocol must police itself, when in fact, the market does a far better job of pricing the value of block space. Saylor’s argument is a brutal critique of the arrogance of engineering-based solutions over market-based ones.
Contrarian: The Machine’s Hidden Fear
The contrarian view—and the one that keeps me up at night—is that Saylor is fundamentally right, but for the wrong reasons. The popular narrative is that he is protecting the "digital gold" thesis, defending Bitcoin from becoming a cluttered meme chain. But I believe the deeper, unspoken anxiety is that BIP-110 exposes the fragility of Bitcoin governance itself.
The very fact that a proposal like this can be written and seriously debated is terrifying to the institutional holders. It proves that Bitcoin is not a frozen, immutable monolith but a living, political system. The ENFP in me wants to see this as a creative tension, but the 44-year-old protocol PM knows that political instability is the one risk that capital hates most. The contrarian insight is that Bitcoin’s greatest strength—its immutability—is actually a product of its greatest weakness: an ambiguous governance process. BIP-110 doesn't create a new risk; it reveals the old one that everyone pretended didn't exist.
Saylor’s 110 reasons are a gift, but also a warning. If the community dismisses his concerns as FUD, they will miss the point. The most dangerous outcome isn't that BIP-110 passes; it’s that it fails in a way that leaves the governance issue unresolved. A failed proposal that doesn't lead to a better process is a wound that doesn't heal. It leaves the network vulnerable to the next, more cleverly designed attack. The ghost in the machine is not the inscription data; it’s the inability to agree on how to run the machine.
Takeaway: The Future is a Question
So, what does this mean for the next six months? The immediate signal is clear: the noise around BIP-110 will not die. It will become a litmus test for institutional confidence. If you are a holder of Bitcoin, you are now a shareholder in a corporation with a disputed constitutional convention. The debate isn't over whether to ban JPEGs; it's over who gets to decide. Saylor has drawn a line in the sand, and the sand is shifting.
The question is not whether BIP-110 is good or bad for the protocol. The question is whether the protocol is ready for the 55% world it is proposing. And based on the 110 reasons I’ve just read, the answer is a resounding and technical no. The battle for the soul of the machine has only just begun.