I’ve been watching the BIP-110 signal rate ticker obsessively for three weeks. At press time, it’s crawling at 0.89% — a number so absurdly low that in any normal BIP activation cycle, the proposal would be dead on arrival. But this isn’t a normal cycle. This is a forced signaling path, a UASF-like mechanism that doesn’t wait for miner consensus. It triggers automatically at block height 961,632. That’s roughly two weeks from now.
Every hack is a lesson in trustless verification. This proposal, if executed without broad miner support, could become the first true test of Bitcoin’s governance immune system. The irony is thick: a rule designed to limit arbitrary data abuse may end up exposing the network’s most fragile layer — its consensus formation process.
The Context: What Is BIP-110?
BIP-110 proposes a one-year soft fork that restricts arbitrary data storage in Bitcoin transactions. It targets OP_RETURN misuse, inscriptions, and any script that embeds non-financial data. On paper, it’s a technical cleanup: reduce node resource bloat, preserve block space for value transfer. The mechanism is a “strictly-limited” soft fork with a forced signaling window from height 961,632 to 963,647. Miners must set bit 4 in their block headers or their blocks get rejected by upgraded nodes.
This is where it gets spicy. Forced signaling — also known as “user-activated soft fork” (UASF) — relies on full node operators enforcing the new rule, not miners. If enough economic nodes (exchanges, wallets, major holders) upgrade, miners are forced to comply or risk their blocks being orphaned. Historically, UASF has worked (e.g., BIP-148 in 2017), but only with massive community coordination and a clear enemy (SegWit blockers). BIP-110 has no villain; it’s a policy debate, not a civil war.
The Core: Why It’s Failing — and Why That’s Okay
Let’s crunch the numbers. Current signal rate: 0.89%. The last difficulty epoch ended July 20, and the next one begins around August 3-4. That gives a 14-day window for miners to start signaling. At current hashrate, we’d need roughly 55% of blocks within that epoch to carry the bit 4 flag. Right now, only a handful of anonymous pools are signaling — none of the top 10 pools. This is unprecedented. Even contentious BIPs like BIP-91 in 2017 had at least 20-30% early signals.
Why the silence? Based on my interviews with three mid-sized Chinese mining pool operators (off the record, of course), the answer is unanimous: “No economic incentive to change.” In 2023, when Ordinals inscriptions flooded the mempool, transaction fees briefly accounted for over 40% of miner revenue. Today, it’s stabilized around 15-20%. Miners are not eager to kill a revenue stream, even if it violates the “digital gold” narrative.
But here’s the contrarian layer: BIP-110’s forced signaling path is actually a brilliantly designed stress test. It forces the question: Who decides Bitcoin’s rules? The proposal’s creator, pseudonymous “DataReaper,” told me in a Telegram chat last month that they expected this reaction. “If miners don’t signal, the UASF path activates, and we see whether economic nodes actually care about data bloat,” they wrote. “It’s a referendum on Bitcoin’s identity.”
The Contrarian Angle: A Beautiful Failure
The mainstream narrative—led by Michael Saylor’s recent tweetstorm—is that BIP-110 is “dangerous” and “threatens network stability.” Saylor’s weight amplifies FUD, but his argument is flawed. He claims the “solution is worse than the problem,” conflating forced signaling with permanent chain split risk. In reality, a failed BIP-110 activation would not cause a persistent fork. Why? Because the economic majority—the exchanges, ETFs, custodians—will simply ignore the minority chain.
Think about it. If miners refuse to signal and the forced window opens, upgraded nodes will reject blocks without bit 4. Those miners can continue mining on their own chain, but they lose access to the main liquidity pool. There is no new coin, no coinbase giveaway. Just two incompatible consensus rules. The economic gravity will pull everyone back to the chain with the most transaction volume, which, by definition, is the chain supported by the big players. And big players hate uncertainty. They will (and already are) prepping statements to support the non-upgraded chain. I’ve seen internal emails from a top-five exchange that are explicit: “We will recognize the chain with the most hashpower and economic activity at the time of split.” That’s the original chain.
So BIP-110, as a technical proposal, is likely dead. But as a governance signal, it’s invaluable. It proves that Bitcoin’s consensus layer can reject a soft fork without any formal vote, simply through economic inertia. The system works not because the BIP process is perfect, but because the incentives are aligned: change is only accepted when it has clear, demonstrable support.
The Takeaway: What Next?
The forced signaling window is a binary trigger. Either miners suddenly signal (under 5% probability, in my estimation), triggering activation, or they don’t, leading to a brief period of two chains. In either case, the outcome is positive for Bitcoin’s long-term health. If the fork activates with low support and dies, we learn that UASF without community consensus is ineffective. If it fails entirely, we reaffirm that Bitcoin governance is conservative by design.
Personally, I’m watching the next difficulty epoch like a hawk. If signal rate crosses 5% in that window, I’ll be mildly surprised. If it crosses 20%, I’ll start preparing for a short-term price bump as “governance resolved” narrative kicks in. But my base case is a non-event: a few days of FUD, a 2-3% price dip, then back to macro narratives.
Every protocol upgrade is a lesson in trustless verification. This one teaches us that even when the machinery creaks, the gears still turn.
—