Evidence shows Michael Saylor just torched BIP-110. The MicroStrategy CEO called it a threat to Bitcoin's core value proposition. He's right. But the deeper issue isn't about Ordinals clogging blocks. It's about a protocol rule change that shifts trust from code to miners. That's a dangerous pivot.
Let me unpack the technical machinery. BIP-110 formally names "Reduced Data Temporary Softfork." Its goal: limit non-monetary transactions—like Ordinals inscriptions—from block space. Activation threshold? 55% miner signaling. That's far below the traditional 95% for soft forks. This isn't a bug fix. It's a governance shortcut.
Context first. Bitcoin's block space is a scarce resource. Ordinals proved there's demand for storing images, text, and even entire applications on-chain. That activity drives up fees and congestion. Purists argue Bitcoin is for monetary transfers only. Open network advocates see no reason to filter arbitrary data. This debate isn't new. It dates back to the block size wars.
But BIP-110 changes the rules of engagement. It's a soft fork that treats certain data as invalid. The code is simple: reject transactions exceeding a defined data size or containing specific patterns. Execution-wise, this is trivial. The real complexity lies in social consensus.
Here's the core analysis. From a protocol engineering standpoint, BIP-110 introduces a new trust assumption. Currently, Bitcoin nodes verify transaction validity—signatures, scripts, UTXOs. They don't judge content. BIP-110 gives miners the power to filter based on arbitrary criteria. That's a regression. In my 2020 DeFi summer audits, I saw how minor rule changes in Uniswap V2 forks created exploits. The principle holds: once you add a gate, you create a target.
The activation threshold matters. 55% is not consensus. It's a majority. Under 55%, a single mining pool could force through BIP-110. That reduces decentralization. The code executes, not the promise. And the promise here is "temporary." But temporary soft forks often become permanent. See SegWit.
The slippery slope is real. If BIP-110 passes, what stops the next proposal from filtering CoinJoin transactions? Or transactions to certain addresses? The line between "non-monetary data" and "monetary data" is blurry. A crypto kitten on Bitcoin is just a transaction with an OP_RETURN. BIP-110 doesn't define what counts as non-monetary. That ambiguity is a disaster waiting to happen.
From my experience during the 2022 LUNA crash, I coordinated emergency patches for a DeFi protocol. The root cause? A cascading liquidation logic flaw that only appeared under extreme conditions. Protocol-level rules can have second-order effects. BIP-110's low threshold makes activation easier, but it doesn't account for the long-term erosion of trust.
Zero knowledge, infinite accountability. Bitcoin's value lies in its neutrality. It doesn't discriminate. If you have a valid signature, your transaction is valid. BIP-110 breaks that. It says: "We know bad data when we see it." That's a statement from authority, not code.
Now the contrarian angle. Most critics focus on Ordinals getting killed. I see a different risk: BIP-110 strengthens the narrative that Bitcoin can be managed. That's exactly what regulators want. A Bitcoin that filters data is easier to regulate. The SEC could argue that Bitcoin is not fully decentralized because miners decide what data is allowed. That weakens the "commodity" argument. During my 2025 zero-knowledge audit, I saw regulators push for compliant rollups. They want control points. BIP-110 gives them one.
The hidden danger: governance precedent. BIP-110 sets a low bar for future changes. If 55% becomes the new normal, expect more aggressive proposals. OP_CAT, CTV, even state-level censorship. The blockchain's immutability is a feature, not a flaw. But BIP-110 treats it as a bug.
Market implications. BIP-110 passing would kill Ordinals ecosystem assets: ORDI, SATS, atomicals. That's a clear short. But it also creates a window for Bitcoin L2s like Stacks and RGB. If Bitcoin restricts data, data applications move to sidechains. That's a net positive for L2s. But it fragments the user base.
My takeaway. BIP-110 is not a technical improvement. It's a governance experiment. It tests whether Bitcoin's community is willing to discard neutrality for cleanliness. Based on my audit of twelve ICO contracts in 2017, I learned that small changes in rules can lead to $15 million losses. BIP-110's potential loss is Bitcoin's value premium.
The code executes, not the promise. BIP-110's promise is temporary relief from data spam. Its execution could permanently damage Bitcoin's most valuable feature: trustless neutrality.
Audit first, invest later. Before forming an opinion, check the miner signaling. Watch for core developer statements. Track Ordinals inscription volume. If BIP-110 gains momentum, the market will reprice Bitcoin's risk. The real question: Is neutrality a bug or a feature? I know my answer.
