When MicroStrategy executive chairman Michael Saylor speaks about Bitcoin's protocol architecture, the market pays attention — not merely because of his company's outsized treasury position, but because his interventions in technical debates have a way of crystallizing what is at stake for institutional holders. His latest salvo targets Bitcoin Improvement Proposal 110, known as BIP 110, and his framing is characteristically blunt: the proposal itself is more dangerous to Bitcoin's long-term integrity than the data problem it purports to address.
That is a striking claim worth unpacking carefully. Bitcoin periodically confronts debates over how data — whether inscriptions, token metadata, or other non-payment payloads — propagates across its network. Critics of permissive data usage argue it bloats the blockchain, crowds out financial transactions, and degrades node economics for ordinary participants. Proponents counter that permissionless data embedding is a feature of a neutral settlement layer, not a bug. BIP 110 appears to intervene in this dispute by proposing protocol-level changes that would alter how such data is handled. Saylor's concern is not primarily about what BIP 110 does today, but about what it forecloses tomorrow.
The Protocol Neutrality Argument
Saylor's central objection rests on the concept of protocol neutrality — the principle that Bitcoin's base layer should not discriminate between use cases, transaction types, or categories of data at the protocol level. To build discrimination into the protocol is, from this perspective, to make a permanent philosophical concession: that Bitcoin's ruleset can and should be shaped by the preferences of a current majority, rather than constrained by a minimal, universal design that future participants inherit intact.
This is not a novel argument in Bitcoin governance circles. The block size wars of 2015 to 2017 were, at their core, a collision between competing visions of what the protocol should be neutral toward: large-block proponents wanted neutrality for commerce and payment volume, while small-block proponents wanted neutrality for node operators and decentralization. What emerged from that conflict — the Segregated Witness soft fork and ultimately the rejection of Bitcoin Cash's scaling approach — was a strong community prior against changes that imposed new value judgments at the base layer. Saylor appears to be invoking precisely that prior against BIP 110.
The Upgrade Path Problem
Perhaps the more technically consequential element of Saylor's critique concerns upgrade path closure. In protocol design, closing a future upgrade path means implementing a change today that makes a different, potentially superior change harder or impossible to implement tomorrow. Bitcoin's scripting language, its opcode set, its witness discount structures — all of these represent decisions whose downstream effects were not fully anticipated at the time. The lesson Bitcoin developers have internalized over years is that conservative, reversible changes preserve optionality, while aggressive interventions that solve one problem can inadvertently lock in constraints that bind the protocol for decades.
If BIP 110 introduces logic at the protocol level that embeds a specific judgment about what data is acceptable or how it should be weighted, that logic could interact in unforeseen ways with future proposals — covenants, validity rollups, BitVM constructions, or whatever the next generation of Bitcoin scalability and programmability research produces. Saylor's warning, read carefully, is less about BIP 110 on its own terms and more about the governance precedent it sets: that when Bitcoin faces a contentious usage pattern, the correct response is to encode a resolution into the protocol rather than allow the market and fee dynamics to resolve it organically.
Why Institutional Holders Have Skin in This Game
Saylor's opposition carries a particular resonance because MicroStrategy's entire investment thesis for Bitcoin rests on the network's immutability and predictability as a monetary protocol. Any change that introduces discretionary, socially-negotiated rules into Bitcoin's base layer creates a category of risk that institutional treasury holders cannot easily model or hedge. If the protocol can be changed to address a data usage controversy today, the implicit question becomes: what controversy justifies a change tomorrow? For institutions holding Bitcoin as a long-duration, rules-based monetary asset, that question does not have a comfortable answer.
This is also why the framing of BIP 110 as "more dangerous than Bitcoin's data problem" is strategically pointed. Saylor is not dismissing the data debate — congestion, fee spikes, and mempool dynamics are real operational concerns. He is instead arguing that the cure proposed by BIP 110 is structurally worse than the disease it addresses, because the disease is bounded and observable while the damage to protocol neutrality and upgrade optionality is diffuse and cumulative.
What This Means for Bitcoin Governance
The BIP 110 debate is a microcosm of a broader tension that will intensify as Bitcoin's utility expands beyond simple value transfer. Each new use case — from ordinals and inscriptions to layer-2 settlement and programmable contracts — will generate constituencies with strong preferences about how the base layer should behave. The question Bitcoin's governance process must answer, repeatedly and without a formal mechanism for doing so, is whether protocol changes serve the network's foundational properties or merely the preferences of whoever is loudest in a given cycle. Saylor's intervention, whatever one makes of his specific conclusions, forces that question into sharper focus at exactly the moment when it matters most.
Written by the editorial team — independent journalism powered by Bitcoin News.