We didn't expect the most direct threat assessment to come from a balance sheet. Yet in July 2025, Michael Saylor, the executive chairman of MicroStrategy, published a commentary that sounded less like an investment thesis and more like a security audit. He named a specific attacker: BIP-110. Not a hostile state. Not Ethereum. Not an exchange collapse. A Bitcoin Improvement Proposal.
Governance isn't a button you press after deployment. It is a proof system that must run every block. Saylor's warning deserves that reading. He is not offering a technical specification. He is running a governance audit on the social layer, and his conclusion is blunt: every consensus change is a precedent, and every precedent is a tax on future immutability.
The Context: Bitcoin Is Not a Company. It Is a Constitution.
Bitcoin's Layer 1 is intentionally small. A UTXO ledger. A fixed 21 million supply. Proof-of-Work mining. A block creation schedule that halves every four years. It does not execute smart contracts. It does not enforce royalty payments. It does not serve ads. That minimalism is not a technical limitation; it is a legal structure. Every full node enforces the same property rights. Every miner competes for the same scarce block space. Every wallet user relies on the same settlement rules.
But this constitution has no formal courts and no single parliament. Changes are proposed through the Bitcoin Improvement Proposal process. If node operators and miners signal enough support, the proposal can activate as a soft fork or a hard fork. Most proposals die quietly. Some survive because they are, genuinely, low risk. BIP-110 is not dying quietly.
BIP-110 is often framed as an obscure technical proposal, but in reality, it tests the boundary between a soft fork and a policy intervention. The proposal, in Saylor's view, would restrict certain transaction output types and, more importantly, break the consensus neutrality that has kept Bitcoin stable for over a decade. Its details can be debated; its mechanism cannot be neutral. The moment a consensus rule favors one class of transactions over another, the base layer stops being a neutral ledger and becomes an active regulator. That is Saylor's actual point.
Saylor's criticism is aimed at the idea that a fee-market fix can be neutral. He claims that once you allow one special interest to change the base layer's output semantics, other special interests will line up for their own precedent. He predicts a chain reaction: governance conflict, capital flight, network security deterioration. Behind the dramatic language is a real mechanism. Every line of code writes a history of power.
The historical shadow is the 2017 block size war. That was not a conflict about bytes. It was a conflict about who could change Bitcoin's rules and for what purpose. The result was Bitcoin Cash, a network that chose larger blocks and then watched its value and security relative to Bitcoin erode. Saylor may not mention it directly, but the echo is there. If language around block size increase is a red flag for him, it is because that chapter burned a warning into the community's memory.
In my years auditing smart contracts, I learned to fear small changes more than big ones. A reentrancy bug is visible to trained eyes. A governance precedent is invisible until it has already established the right to change. In my later work designing governance frameworks for DeFi protocols, I learned that the hardest committee to corrupt is the one that meets rarely and changes only under existential pressure. Bitcoin has that structure. Proposals like BIP-110 test whether Bitcoin can keep it.
The Core: The Fee Market Is Not a Detail. It Is the Security Budget.
Saylor's technical argument has three pillars. The first is scarcity. Base-layer changes that make block space less scarce, for example by increasing capacity, reduce the economic cost of spamming the chain. When block space is abundant, miners compete for fewer meaningful transactions, and the transaction fee market weakens.
The second pillar is the fee market itself. Bitcoin miners currently earn roughly 3.125 BTC per block as subsidy. At a bitcoin price around sixty-four thousand US dollars, that subsidy is approximately two hundred thousand dollars per block. Transaction fees add only a small fraction, often less than five percent of total reward. As block subsidies continue to halve, that fee fraction must grow. If a consensus-level proposal suppresses fee competition, the network's future security budget will not grow enough to pay for the electricity, hardware, and bandwidth required to defend the chain.
The third pillar is complexity. Any change to Bitcoin Script, such as the introduction of covenants or new output restrictions, expands the attack surface. Developers and auditors must now reason about new edge cases, new reentrancy-style scenarios, and new interaction patterns with wallets and other protocols. Bitcoin's security has historically rested on "less code, less attack surface." BIP-110 may appear small, but it opens the door to more complex script features later. Based on my audit experience, a small change in one function often produces a critical bug in an unrelated part of the system. In Bitcoin's case, the system is the global monetary network.
The 2017 SegWit activation experience shows Bitcoin can handle upgrades without catastrophe. But SegWit succeeded because it was backward-compatible, reduced malleability, and had measured support. The current wave of covenant-related proposals is different: it invites the base layer to enforce application policies. That is a governance shift disguised as a technical patch.
Saylor's solution is to lock Layer 1 down and delegate innovation to Layer 2. Lightning Network, RGB, and future protocols can handle fast payments, smart contract functionality, and programmable assets. This is a standard and respectable architectural position: the base layer should remain a settlement layer, not an application platform.
But here is the gap I cannot ignore. Layer 2 is not currently ready to absorb Bitcoin's entire functional future. Lightning Network capacity is growing, but it still represents a small percentage of Bitcoin's economic activity. The channel liquidity model solves some problems and creates new ones around routing and custody. RGB is promising, but its adoption remains early. Saylor is asking for a decade of patient waiting while the rest of the crypto ecosystem keeps moving. That is a valid trade-off only if the base layer's immutability is truly the highest-value asset. It may be. But it is not guaranteed.
The Contrarian Angle: Immutability Without Maintenance Is Decay
Now I have to push back. Saylor's warning is strong, but it is also self-interested. He is the largest public corporate holder of Bitcoin in the world. His net worth, his treasury strategy, and his entire business narrative depend on Bitcoin remaining the scarce digital asset he says it is. That does not invalidate his technical logic. It does mean that his definition of "safe" is the definition that protects his position.
The counterintuitive risk is that Saylor's absolutism becomes another form of governance failure. If every proposal is treated as an attack, Bitcoin will not be able to fix real bugs. I have seen protocol teams so afraid of change that they shipped known vulnerabilities to production. The blockchain industry does not need more examples of refusal to upgrade. It needs a process for distinguishing between a necessary correction and a harmful precedent.
There is also a market risk. When influential voices frame a routine BIP discussion as a civil war, retail investors treat it as a signal to sell. Short-term volatility is gamed by traders who understand exactly how narrative amplification works. The true governance risk is not the proposal itself. It is the inability to have a rational, transparent debate without maxi rage destroying the price.
Finally, the ideology of total immutability has an uncomfortable political consequence. The Bitcoin network is already concentrated enough. Large miners, large exchanges, and large institutions define the upper limits of the system. A governance environment that blocks every base-layer evolution preserves not only neutrality but also the power of those who hold the most bitcoins. Saylor is not standing outside the system; he is standing at its center. Truth emerges from transparency, not from silence. His commentary is transparent about the danger of change, but silent about his own incentive to freeze the status quo.
I have seen better governance in DAOs: quadratic voting, timelocks, veto thresholds, and public audit trails. None of those tools need to be written into Bitcoin's base layer, but they are useful mental models for how a decentralized network can update itself without being captured. The goal is not to change Bitcoin constantly. The goal is to build a healthy relationship with change itself. That is what Saylor's commentary lacks: a constructive path. We didn't get a governance framework. We got a warning.
The Takeaway: Watch the Version Bits, Not The Tweets
Bitcoin will not die from BIP-110. It will die, if it dies, from the governance culture around it. There are concrete signals that matter more than Saylor's latest interview. Miner version bit signalling during a BIP activation window. The number of Bitcoin Core maintainers willing to review contentious patches. The growth in Layer 2 capacity relative to mainnet transactions. The willingness of large holders to fund independent technical research instead of only buying more coins.
Governance isn't a destination. It is the longest-running audit in the industry.
In my next governance audit, I will be looking for a specific vulnerability: the precedent. A proposal can be safe in isolation and fatal as a pattern. Parsing Bitcoin's future requires reading not just the code, but the history of every patch around it.
Bitcoin's hardest fork is not a chain split. It is the philosophical fork inside every node operator's mind. The future is not about whether Bitcoin changes. It is about whether the community can change the conversation before the chain is forced to choose.