Saylor’s Opposition to BIP 110: Why Protocol Neutrality Is the New Battleground

CryptoRover
Investment Research
Verify: Bitcoin’s blockspace is not infinite. But the debate about what fills it just got a 5,000-word veto from the man holding 226,331 BTC. On July 19, 2025, Michael Saylor released a manifesto titled “110 Reasons BIP 110 Is a Bad Idea.” Within hours, ORDI dropped 8%. Runes trading volumes halved. The market priced in a sudden reassessment of Bitcoin’s future as a settlement layer vs. a data bus. I’ve been in this game long enough to recognize an engineered narrative shift when I see one. I audited ICO contracts in 2017 where developers tried to hardcode blacklists—same flavor of ‘we know what’s best for the protocol.’ I watched Terra’s stability mechanism implode because its consensus was bent to preserve a narrative. And now, Saylor is drawing a line in the sand: do not modify Bitcoin’s consensus to judge transaction content. Context: BIP 110 is not a real BIP number in the official repository—at least not yet. The name has been floated internally by Bitcoin Core developers frustrated with the explosion of ordinal inscriptions and rune token minting. The proposed changes would limit data storage in transactions, either by reducing OP_RETURN size or by imposing new script size limits. Effectively, it would ban non-financial data from Bitcoin mainnet. Saylor’s opposition is not a surprise. He is Bitcoin’s largest public corporate holder. His firm, MicroStrategy, has built a valuation narrative entirely around Bitcoin as a store of value—not as a programmatic platform. Any change that expands Bitcoin’s use case into a general-purpose data chain threatens that narrative. But his arguments go deeper than self-interest. Core: Let’s dissect Saylor’s core thesis: “Bitcoin cannot judge the purpose of data. The protocol must remain neutral.” From a technical standpoint, he is correct. Bitcoin’s consensus rules currently validate transaction validity—signatures, double-spending, fee sufficiency—not content. Modifying the rules to filter for ‘useful’ vs. ‘spam’ data introduces a subjective gate. During my 2020 DeFi farming sprint, I learned that subjective gates are the first step toward rent-seeking. Custom Python scripts I wrote for rebalancing were purely logical. The moment a protocol added a ‘use case’ filter, arbitrage opportunities became political. Saylor argues that ‘controversial transactions should be determined by the fee market, nodes, and miner strategies.’ This is the market solution. If someone wants to inscribe a JPEG, they pay fees. If the JPEG consumes blockspace, miners include it if the fee covers opportunity cost. No consensus change needed. But there is a hidden regulatory dimension here. Based on my 2024 experience integrating Aave V3 with a legal wrapper for HNW clients, I understand that regulators love clear lines. If Bitcoin’s protocol can be modified to restrict ‘fraudulent’ inscriptions, it implicitly acknowledges that the protocol can exercise judgment. That moves Bitcoin closer to a central security under the Howey Test—because its value would partially depend on the ‘efforts of others’ (the core developers and miners enforcing the filter). Saylor’s opposition is therefore a preemptive strike against regulatory capture. By keeping the protocol neutral, he deposits the regulatory burden on the application layer—inscription issuers, exchanges listing them, wallet providers. That’s where compliance belongs. Not in consensus. Contrarian: But Saylor’s argument has a blind spot—one revealed during my 2026 AI-agent trading protocol incident. An oracles manipulation event caused a 15% drawdown because the autonomous agent had no human circuit breaker. Pure automation fails when edge cases arise. Similarly, pure fee-market neutrality fails when externalities spill over. High volumes of inscription transactions can lead to UTXO set bloat, increasing node operational costs. Research from Delv in 2024 shows that a continued increase in UTXO growth would raise full node requirements, potentially centralizing node operation to better-equipped entities. The fee market does not price this externality. Miners collect fees now, but higher node costs reduce decentralization later. Saylor’s opposition may also be self-serving. MicroStrategy’s Bitcoin treasury is its primary asset. Any proposal that shakes confidence in Bitcoin’s stability threatens MSTR’s stock price. By killing BIP 110, Saylor maintains the status quo—but the status quo is not sustainable forever. If inscription demand continues growing, blockspace becomes congested, fees rise, and small transactions become uneconomical. That pushes users to Layer-2 solutions—which Saylor has criticized as unnecessary complexity. So he may be trading long-term adaptability for short-term narrative control. Moreover, his emphasis on ‘neutrality’ ignores that Bitcoin’s codebase is already shaped by human values. The 2100- cap is a value choice. The 10-minute block time is a value choice. Choosing not to filter spam is also a value choice—just one that favors existing fee dynamics. Takeaway: Code doesn’t lie. The blockspace is limited. The question is: who decides its allocation—miners via fees or consensus via governance? Saylor has thrown his weight behind miners and the free market. That may be the right call for 2025, but it does not solve the UTXO bloat problem. Watch miner signaling on BIP 110. If hashrate signals support, the narrative flips. If not, inscription-based assets face a permanent cloud of uncertainty. Trust is a variable; verify the proof, then sleep. For now, the takeaway is clear: Bitcoin is doubling down on its digital gold narrative. Projects building on top of mainnet inscriptions need a Plan B. Layer-2 solutions that offload data without modifying consensus—like BitVM-based rollups—become more attractive. And regulators will be watching whether the application layer can self-police without protocol assistance. I’ve lived through ICO mania, DeFi summer, Terra’s death spiral, and institutional integration. Every cycle teaches the same lesson: don’t bet against the incumbents. Saylor is an incumbent. His opposition significantly raises the bar for BIP 110 passage. But incumbents also get complacent. The next proposal may be more carefully framed to address externalities without appearing to judge content. Stay alert. Final signal: If you hold inscription-based assets, hedge with pure BTC exposure. The next debate is not if but when.