Michael Saylor just dropped a bombshell on BIP-110. And it’s not about ordinals.
It’s about the backdoor.
The proposal—officially a technical tweak to limit script and witness data—has been quietly cooking in the Bitcoin Core discussion channels. Seven consensus changes. Limiting script public key lengths. Killing certain Taproot paths. The stated goal? Curb the forever-growing blob of inscriptions on the blockchain. A logical move on paper.
But Saylor’s not buying the packaging. He spent 48 hours compiling a thread that digs into the real danger: the activation mechanism. And he’s right.
The activation trap.
BIP-110 doesn’t use the old BIP-9 framework, which required 95% miner signaling and a clear FAILED state for proposals that fizzle out. Instead, it introduces a 55% threshold. No FAILED state. A supermajority of miners can force a consensus change, and if the remaining 45% don’t comply, the chain splits—no soft reset built in.
Typical mining pool configuration? Top three pools can easily hit 55%. Pump, dump, debug. Repeat.
This isn’t a design oversight—it’s a governance loophole. Saylor’s core argument: the process is more dangerous than the problem. I’ve sat through enough BIP debates to know that once you lower the consensus bar, you invite a flood of worse proposals. And this one doesn’t even have a kill switch.
The technical layer—fiddly but fixable.
The seven restrictions themselves are messy. They touch on script opcodes, witness item limits, and Taproot script path validation. Based on my audit experience, these changes could break legitimate protocols like RGB or Taproot Assets without careful re-factoring. The complexity spike will scare off 90% of developers—sound familiar?
But that’s not the real story. The real story is that Saylor wants to solve the inscription problem via market forces—higher fees, node-level filtering—not by changing the consensus layer. He’s pushing the “Layer2 or bust” narrative. And it’s a strong one.
The contrarian angle nobody’s talking about.
Everyone is focused on whether BIP-110 kills ordinals. Missing the bigger picture: Saylor’s opposition might actually be protecting Bitcoin’s flexibility.
Think about it. If BIP-110 passes with a 55% gate, it sets a precedent: the next proposal could increase the block size, change the supply cap, or re-enable OP_RETURN spam—all with a simple mining majority. The “immutable” brand cracks.
But here’s the twist: if BIP-110 fails (likely now with Saylor’s influence), the inscription mess continues. Block space gets choked. Fees spike. That pushes real usage to Lightning, RGB, Ark—which is exactly what Saylor wants. A cleaner L1, a messy L2 ecosystem.
Gas fees higher than the yield. Typical.
The real battlefield: miner signaling.
Over the next 3–6 months, watch for miner signaling in the coinbase fields. If >30% of hashrate signals support, the market will start pricing in a split. Core developer stance matters more than any tweet—if they denounce the BIP-110 mechanics, it dies.
Saylor’s thread already put the community on notice. The old guard hates the precedent. The ordinals crowd hates the restrictions. The only ones who love it? Possibly the top three miners who could coordinate a quick activation—and then cash out on the chaos.
My take.
Bitcoin’s governance is its Achilles’ heel. Every few years, someone tries to “improve” it by lowering the barrier to change. BIP-110 feels like a stress test—a deliberate exploit of the governance vacuum.
Saylor’s reaction is a signal: the big HODLers are watching. They’ll oppose any mechanism that makes Bitcoin easier to capture. And honestly? I’d rather have a bloated L1 with messy inscriptions than a version of Bitcoin that can be rug-pulled by three mining pools.
Pump, dump, debug. Repeat. t check.
What to watch next: - GitHub activity on bitcoin/bips for BIP-110 PRs. - Public statements from Bitcoin Core maintainers (e.g., achow101, sipa). - Miner signaling logging on platforms like btc.com.
If the proposal gets enough traction, the real battle shifts to Layer2 adoption. Either way, Bitcoin’s governance is entering a new phase—and it’s not pretty.