July 19, 2025. Michael Saylor published a 110-reason manifesto against BIP 110. That single action signals more than a policy dispute—it reveals a fracture in Bitcoin's consensus layer that no amount of proof-of-work can weld shut.
Context
BIP 110, a Bitcoin Improvement Proposal that emerged from the core developer mailing list, aims to restrict non-transactional data storage on the main chain—effectively targeting Ordinals inscriptions and Runes. Its proponents argue that such data clogs blocks, degrades fungibility, and invites regulatory scrutiny. Saylor, chairman of MicroStrategy and the largest single corporate Bitcoin holder, fired back with a structured, 110-point takedown. His central thesis: modifying consensus rules to judge transaction content transforms Bitcoin from a neutral protocol into a gatekeeper—a dangerous precedent.
Before we parse his arguments, note the context. This is not a technical debate about block size or opcodes. It is a battle over Bitcoin's identity: digital gold or programmable money? Saylor's response anchors the former.
Core: The Clinical Code Autopsy
Let's start with the assumption that code does not lie. BIP 110's implementation—whether through a soft fork tightening OP_RETURN limits or altering script size boundaries—would embed a judgment function into the consensus layer. That is the technical equivalent of a moral filter. Based on my forensic audits of protocol-level changes, this is a red flag for any system that claims to be permissionless.
Saylor's 110 reasons decompose this flaw. Reason #12: "Bitcoin cannot determine the purpose of data; therefore it must remain neutral." This is not opinion—it is a logical deduction rooted in the impossibility of a decentralized network distinguishing between a fraudulent NFT metadata and a legitimate timestamp proof. The protocol sees bytes. It does not see intent.
Reason #47: "By modifying consensus to restrict data, you change Bitcoin's security model from neutral execution to content censorship." This is precise. Bitcoin's security relies on miners validating transactions based on cryptographic rules, not semantic evaluation. Once you introduce semantic filtering—even for good reasons—you open a vector for social engineering attacks. A future BIP could restrict transactions labeled as "toxic" by a government. The principle of least privilege applies to consensus: give it the minimum power needed. Here, the minimum is pure verification, not curation.
Reason #73: "The fee market is the only efficient allocator of block space." This is mathematical skepticism at its finest. Economists have proven that price signals (fees) allocate scarce resources more efficiently than central planning (rules). BIP 110 is central planning. It assumes that developers can predict which data adds value and which does not. History shows otherwise. I recall from my time modeling Impermax's yield mechanics that any system relying on human judgment to filter transactions quickly degrades into rent-seeking. BIP 110 would create an "approved data" status, incentivizing insider deals to bypass restrictions.
Code does not lie, but it often omits the truth. The omission here is that BIP 110's draft never specifies how to define "non-transactional data." The devil lies in that ambiguity. If you cannot define it precisely, you cannot enforce it fairly—only arbitrarily.
Contrarian: Where the Bulls Got It Right
Let me pause. Saylor's opposition is not without its own blind spots. The bulls—supporters of BIP 110—have a valid point: the main chain is not an infinite data blob. Inscriptions have caused UTXO bloat, increased node requirements, and created a parallel fee economy that often outbids legitimate financial transactions. One bull argument is that a modest, tightly scoped restriction—say, limiting OP_RETURN to 80 bytes as originally defined—would preserve neutrality while restoring efficiency.
Further, Saylor's blanket dismissal ignores the possibility that Bitcoin could evolve its consensus without compromising its core. For instance, introducing a dust limit increase is not censorship—it's resource management. The line between "content filtering" and "performance optimization" is blurry, but the bulls argue that BIP 110's proponents intended the latter.
Yet, Saylor's 110 reasons systematically dismantle that nuance. Reason #89: "Even a small restriction sets a precedent for larger ones." This is the inevitability narrative. Once you accept that the protocol can judge data efficiency, you accept that it can judge data morality. The slippery slope is real in governance systems without formal constraints. Bitcoin has no constitutional court—only community consensus. And today, Saylor's consensus says no.
Takeaway: The Debris of Hype
Trust is a variable; verification is a constant. Saylor's manifesto verifies that Bitcoin's governance is not purely technical—it is political, financial, and ideological. His intervention has likely killed BIP 110, at least in its current form. But the underlying tension remains. The inscription ecosystem now faces a binary choice: migrate to Layer-2 solutions that do not pollute the main chain, or prove their value through fee market survival. The former is the logical path. The latter is gambling with better UI.
Hype builds the floor; logic clears the debris. Saylor has cleared the debris of this proposal, but the debris of neglected innovation will pile up elsewhere. The real test for Bitcoin is whether it can accommodate programmable money without sacrificing neutrality. My bet is on Layer-2 protocols using BitVM and ZK proofs—they verify logic without altering the base layer. But that is an analysis for another audit.
For now, remember: the code was ready. The community was not. Saylor's 110 reasons are a warning to anyone who thinks Bitcoin's protocol can be bent without breaking.