Michael Saylor posted 110 tweets opposing BIP-110. That’s not debate; it’s a coordinated signal. The proposal is simple—restrict non-financial data in Bitcoin transactions—but the subtext is war over Bitcoin’s identity. I don’t buy the neutrality argument. It’s a screen for economic interests, and it masks a structural vulnerability that most analysts ignore.
Context: The Soft Fork with No Name
BIP-110 is a Bitcoin Improvement Proposal targeting non-financial data embedded in transactions. Currently, Bitcoin’s witness field—introduced via SegWit—allows arbitrary data, from text to images. Ordinals and BRC-20 tokens exploit this to store digital artwork and token metadata directly on the network. The proposal would classify such data as invalid under new consensus rules, effectively banning inscriptions post-activation.
It’s a soft fork: backward-compatible, but old nodes will reject blocks containing restricted data. The stated goal is to reclaim block space for financial transactions, reducing block size growth and potentially lowering fees. The unstated goal is to curb the Ordinals ecosystem, which has injected volatility into fee markets. Saylor’s 110-tweet blitz frames the opposition as a defense of protocol neutrality—the idea that Bitcoin should not discriminate between data types.
Core: The Technical Architecture of Control
Let me unpack the actual code-level implications. Based on my experience auditing DeFi protocols, I’ve seen how seemingly neutral restrictions can cascade into centralization. BIP-110’s mechanism, while not yet coded in a public repository, likely relies on a consensus-enforced rule that parses the witness stack and flags transactions exceeding a data-to-value ratio or containing specific OP_RETURN patterns. The challenge is defining “financial data.” Does a multisig transaction with a memo string count? What about Lightning Network funding transactions that embed channel parameters?
If the rule is too strict, it could break legitimate use cases like atomic swaps or timelocked contracts that embed small metadata. If too loose, Ordinals will simply refactor their encoding to bypass detection—shifting from witness fields to OP_RETURN or exploiting script pubkeys. The arms race would negate the intended efficiency gain.
More critically, BIP-110 changes the economic incentives for miners. Ordinals have inflated transaction fees significantly—at peak periods, inscription-related fees constituted over 20% of total miner revenue. Post-halving, when the block reward drops, that percentage will rise. Limiting non-financial data effectively reduces the fee pool. The security budget—the sum of fees plus subsidy required to sustain hash rate—shrinks. This is the hidden tension Saylor won’t address.
Contrarian: Saylor’s Neutrality Is a Smokescreen
Here’s the counter-intuitive angle. Saylor’s claims of impenetrable security for Bitcoin’s current state ignore the economic pressure of declining block rewards. By opposing BIP-110, he’s defending the status quo—where Ordinals provide a temporary fee lift. But that lift comes at a cost: block space becomes congested, fees spike for ordinary users, and the network’s fungibility narrative erodes when certain transactions are categorized as “spam” by social consensus rather than protocol rules.
What if Saylor’s real fear is precedent? He stated that restricting data types could “jeopardize neutrality” and set a dangerous precedent for protocol-level censorship. That argument has merit—once the Bitcoin Core team decides what constitutes a valid transaction beyond financial integrity, they’ve crossed a line. Future proposals could target transactions from certain addresses or block mixes to comply with sanctions. The slippery slope is real.
But the blind spot is that doing nothing is not neutral. Currently, Ordinals crowd out financial transactions, creating a fee burden that pushes smaller users off-chain. The network’s neutrality is already compromised by economic inequality. BIP-110 attempts to restore a level playing field—not by policing content, but by defining the protocol’s primary function: value transfer. The whitepaper is fiction. The bytes are reality, and reality says block space is finite.
Takeaway: The Illusion Is Broken
This debate will not end with BIP-110’s fate. The rift it exposes—between maximalists who see Bitcoin as a settlement layer and pragmatists who accept non-financial uses as necessary for fee sustainability—will persist. Watch for miner signaling. If Foundry USA or Antpool publicly support BIP-110, the soft fork could activate despite Saylor’s opposition. If they remain silent, ordinals boom until the next halving squeezes fee revenue further. Either way, the illusion of a unified Bitcoin community is shattered, and the governance crisis beneath the surface is now visible to anyone who reads the bytes.