Michael Saylor posted 110 tweets on a single Sunday morning. Not price predictions, not corporate updates — just a sustained, line-by-line attack on a Bitcoin Improvement Proposal he never named until tweet 47. The target: BIP-110, a soft fork designed to restrict non-financial data embedding in Bitcoin transactions. Why 110 tweets? Because the BIP number is 110. The man who holds 21,000 BTC for his company didn't just disagree — he orchestrated a digital filibuster.
Context: The BIP That Targets Inscriptions
BIP-110 is, on paper, a minimalist change. It proposes a new consensus rule that forbids transactions from carrying data that cannot be economically justified as financial metadata. No more JPEGs in witness fields. No more BRC-20 token inscriptions. No more Ordinals art stored on the most secure immutable ledger in existence. The proposal is still in draft stage — no code implementation has been merged into Bitcoin Core, no testnet deployment. But the intent is clear: reclaim the block space that Ordinals and its derivatives have consumed since the protocol’s activation in early 2023.
As of February 2025, inscriptions account for roughly 15% of Bitcoin’s daily transaction volume and contribute an estimated 7% of miner fee revenue, according to Dune Analytics dashboards I’ve been tracking. The proponents of BIP-110 argue that this non-financial data inflates UTXO sets, increases node storage requirements, and distorts the fee market — turning a settlement layer into a cheap storage tape. Opponents, led now by Saylor, claim that any protocol-level restriction on data content violates Bitcoin’s core principle of permissionless neutrality.
Core: The Code That Doesn’t Exist Yet
Let’s be precise. BIP-110 has no public repository with Solidity or Rust — because Bitcoin doesn’t use those languages. It’s a consensus change written in C++ for Bitcoin Core. From my experience reverse-engineering protocol changes for the 0x v4 audit, I can tell you that the devil is in the definition of “non-financial data.” How do you programmatically distinguish between a transaction that encodes a dollar amount and one that encodes a poem? The proposal likely relies on parsing the OP_RETURN output or the witness stack for specific byte patterns — but that introduces a slippery slope.
Consider this: a transaction that sends 0.0001 BTC to a new address and includes a 40-byte string “#FreeRoss” in its witness. Is that financial? The string isn’t a payment instruction. A strict parser would flag it as non-financial and reject the block. But what if that string is actually a cryptographic commitment to a proof-of-reserve document? Suddenly, a legitimate audit protocol gets classified as spam. The detection mechanism becomes a censorship machine.
Code does not lie, but it often omits context. BIP-110’s proponents have yet to release a technical specification that defines the boundary. Without that, we are debating a ghost — a philosophical stance wrapped in soft-fork packaging.
From a security standpoint, the soft fork itself is low risk: old nodes remain compatible, and miners signal readiness with a 95% threshold. But the economic implications are not trivial. If BIP-110 passes, the 7% fee contribution from inscriptions disappears. Miners lose that revenue stream. In a post-halving world where block rewards are 3.125 BTC, every percentage point matters. The security budget of Bitcoin — already a debated topic — would shrink further, potentially making the network more vulnerable to 51% attacks if hashrate drops.
Parsing the chaos to find the deterministic core. The deterministic core here is that BIP-110 is not a technical optimization — it is a value judgment about what Bitcoin should be: a pure monetary network or an evolving ecosystem.
Contrarian: Saylor’s Neutrality is a Mirage
Saylor’s central argument, as extracted from his 110-tweet barrage, is that restricting data types compromises Bitcoin’s neutrality. He claims that the protocol must remain agnostic to the content of transactions. But that’s a convenient fiction. Bitcoin already enforces many content restrictions: it forbids transactions that exceed block size limits, it rejects scripts that violate standardness rules, and it bans certain opcodes for security reasons. Neutrality is not binary — it’s a spectrum.
The real question is who benefits from maintaining the status quo. Saylor’s MicroStrategy has billions in Bitcoin exposure. Any disruption — including a contentious fork or a decline in miner profitability — threatens his paper gains. By opposing BIP-110, he aligns himself with the Ordinals ecosystem, which has generated millions in fees for miners and created a new narrative for Bitcoin as a store of art. But he also aligns with the very crowd that many purists consider “spammers.” Irony is a feature, not a bug.
Moreover, Saylor’s opposition lacks technical depth. He didn’t publish a counter-BIP. He didn’t offer a scalable alternative to limit spam without censorship. He just tweeted. That’s the weakest form of governance — signaling without building.
The standard is a ceiling, not a foundation. If Bitcoin adopts BIP-110, it sets a precedent that protocol layer can define “legitimate” use. That could be weaponized by regulators tomorrow to demand a ban on privacy-enhancing transactions. If it rejects BIP-110, it accepts that the network will become increasingly bloated with non-financial data, potentially pushing node operation costs higher and centralizing validation.
Takeaway: The Unforked Future
This debate will not resolve quickly. BIP-110 is still a seedling in the Bitcoin-Dev mailing list. The next 6 months will reveal whether the community prefers purity or plasticity. Watch for two signals: first, whether any major mining pool (Foundry USA, Antpool) publicly supports or rejects the proposal. Second, whether Ordinals transaction volume grows or declines — if it continues to climb, the economic incentive to curb it strengthens.
I predict neither side wins outright. BIP-110 will be modified into a watered-down version that restricts only egregious abuse (e.g., > 100KB of non-financial data per transaction) while leaving room for small inscriptions. That’s the typical Bitcoin outcome — a compromise that pleases no one but keeps the chain intact. Saylor’s 110 tweets will become a footnote in the ledger of governance theater.
But if the debate escalates into a UASF-style standoff, we are back to 2017. And everyone loses. The true cost of this controversy is not the BIP itself, but the fracture it reveals: Bitcoin is still struggling to define its own identity, 16 years after genesis.