On July 20, 2025, the Bitcoin-dev mailing list logged a 400% spike in thread replies within 72 hours. The cause? BIP-110, a proposal that doesn't just tweak block space—it rewires the governance circuit. The central mechanism? Lower the soft fork activation threshold from the sacred 95% hashpower to a mere 55%.
The ledger never lies, only the interpreter does.
I’ve been on the other side of similar audits. In 2018, I spent four months auditing Compound’s initial lending protocol. We found three integer overflow flaws that would have drained millions. The lesson: code changes in consensus layers require extreme verification. BIP-110 lacks that. Its author remains pseudonymous. Its code contains a critical vulnerability—dubbed "BlockSlop"—that can cause nodes running the modified client to permanently diverge on historical chain data. That’s not a bug; it’s a consensus bomb.
Context: BIP-110 targets two perceived problems. First, the explosion of non-monetary data in Bitcoin blocks—specifically Ordinals inscriptions and BRC-20 tokens, which use Taproot outputs to embed arbitrary data. Second, the argument that this "bloat" increases node operational costs and slows block propagation. The proposal caps all script data at 34 bytes per output, effectively restoring the pre-Taproot OP_RETURN limit, and temporarily restricts Taproot-specific functionality until a more permanent solution is designed. To force it through, the threshold for miner signaling is halved to 55%, with a backup User-Activated Soft Fork (UASF) path if miners resist.
Core analysis: Let’s follow the on-chain evidence chain.
- Miner support: As of July 20, signals for BIP-110 remain below 0.5% of total hashrate. The top five mining pools (F2Pool, Antpool, ViaBTC, BTC.com, Poolin) have released no official statements of support. In a 2024 ETF flow analysis I led, we tracked institutional accumulation patterns—miners vote with hash, not words. The silence is deafening.
- Developer opposition: Jameson Lopp (Casa CTO, Bitcoin Core contributor) called the proposal "a trojan horse for centralization." Michael Saylor (MicroStrategy) warned it would create a "devastating precedent for censorship." These aren’t fringe voices; they represent the conservative capital-thesis camp. Their public rejection anchors the network’s expectation.
- The BlockSlop vulnerability: Discovered by independent researcher Dathon Pwn, this flaw means a node running BIP-110’s modified code would disagree with the canonical chain when validating old blocks containing certain OP_RETURN data. This is not a minor edge case—it’s a consensus fork in waiting. No responsible node operator would deploy this without a fix, and no fix has been submitted.
The result? The proposal is currently dead on arrival. But the drama isn’t the proposal itself—it’s what it reveals about Bitcoin’s governance immune system.
Contrarian angle: Here’s where most pundits get it wrong. They frame BIP-110 as a technical debate over data limits. It’s not. It’s a stress test of Bitcoin’s social contract. The 95% threshold isn’t arbitrary—it forces overwhelming consensus before any change. Lowering it to 55% transforms Bitcoin from a “conservative ledger” into a “voting machine” where a simple majority can dictate protocol rules. That frees the door for future proposals to change monetary policy, block reward, or even the 21 million cap. Correlation does not equal causation—but a governance precedent does.
During the 2022 Terra collapse, I spent 72 hours verifying wallet movements to reject the “market correction” narrative. I learned that real risk isn’t in the obvious attack—it’s in the erosion of norms. BIP-110’s biggest threat isn’t its 34-byte limit; it’s the normalization of low-threshold upgrades. Yield is a function of risk, not magic. The market hasn’t priced this governance risk yet, but it will if UASF preparations surface.
Takeaway: The miner signaling window opens in early August. If support remains below 1%, BIP-110 will wither like dozens of failed proposals before it. But the conversation will persist. Code is law, but data is truth. Track the hash, track the developer mailing list traffic, track the UASF-related GitHub repos. If no credible client emerges by August 10, the crisis passes. If one does, Bitcoin faces its most serious fork threat since 2017. The narrative will shift from “data cleanup” to “governance revolution.” And the data will tell us which camp has the real consensus.
Quantify the chaos, then reveal the pattern.