The blockchain didn't blink. At block 961,632, the Bitcoin main chain kept churning—steady, cold, indifferent. Meanwhile, a renegade fork, BIP-110, had just thrown itself off the consensus cliff. Eight hours later, it had produced exactly two blocks. Not a revolution. A death rattle.
This wasn't a hack. There was no exploit, no stolen funds, no flash loan. This was a governance failure—pure, unadulterated, and brutally educational. BIP-110, a Bitcoin Improvement Proposal aiming to restrict non-financial data writes (read: Ordinals inscriptions), tried to force its way into existence via a User-Activated Soft Fork (UASF). The result? A chain that barely crawled, a handful of orphaned blocks, and a lesson in why Bitcoin's consensus isn't code—it's hashrate.
Context: The UASF That Forgot to Ask for Permission
BIP-110's core idea was simple: limit Bitcoin's block space to purely financial transactions, effectively banning Ordinals, BRC-20 tokens, and any other data-heavy use. The method was aggressive: at a specific block height, nodes running BIP-110 would reject any block that didn't include a signal of support for the proposal. This is a classic UASF move—nodes enforce rules unilaterally, forcing miners to choose between compliance and being orphaned.
But here's the catch: Bitcoin's governance isn't a democracy of nodes. It's a trilemma of developers, miners, and users. BIP-110 had only 2.53% signal support in the previous difficulty epoch (51 out of 2,016 blocks), far below the 55% activation threshold. The proposal didn't have a consensus; it had a wish. And wishes don't produce blocks.
Core: The Numbers Don't Lie—4% Hashrate, 100% Failure
Let's talk about what happened in those eight hours. On August 9, 2024, at block 961,632, the BIP-110 nodes split. The main chain continued to 961,681 and beyond. The fork chain stalled at 961,633. That's two blocks. In eight hours, Bitcoin's average block time is 10 minutes, meaning the expected output was 48 blocks. The fork produced 2. That's a hashrate share of roughly 4%.
Based on my months tracking Bitcoin's mining economics, this was never going to work. The 2.53% signal support wasn't just a warning—it was a death sentence. Miners aren't ideologues; they're businesses. Since Ordinals emerged in early 2023, miners have earned hundreds of millions in transaction fees from inscriptions. BIP-110 would have cut that revenue stream overnight. No miner with a functioning P&L would voluntarily adopt it.
The fork's failure wasn't technical—the code probably worked fine. It was economic. The proposal assumed that node operators could force miners to comply. But miners control the physical hardware. When the fork produced only two blocks, the message was clear: we don't care about your UASF, we care about our bottom line.
Contrarian: The Fork That Strengthened Bitcoin's Governance
Here's the counter-intuitive angle: BIP-110's failure was actually a win for Bitcoin's long-term health. The network's governance mechanism—often criticized as sluggish or chaotic—proved remarkably resilient. The "miner veto" isn't a bug; it's a feature. When a proposal lacks economic alignment, it gets rejected not through debate, but through inaction. The fork is dead; the main chain lives.
But don't celebrate too early. The battle for Bitcoin's block space isn't over. BIP-110 is dead, but the idea of "clean blocks" will resurface—maybe not as a protocol change, but as a miner-led economic filter. Imagine a major mining pool deciding to prioritize transactions below a certain byte size, effectively pricing out Ordinals through fees. That's not a fork; it's a soft censorship. And it's far more dangerous because it doesn't require consensus—just a few large pools coordinating.
Also, the Ordinals community got a temporary reprieve, but this event exposed their vulnerability. They rely on the goodwill of miners who currently profit from inscriptions. If that profit margin narrows—say, if Bitcoin fees crash or if a regulatory crackdown spooks miners—the same miners could flip and start filtering. The fork failed, but the threat didn't disappear; it just changed form.
Takeaway: Watch the Miners, Forget the Fork
What's the takeaway for a trader or builder? First, ignore the fork chain tokens. The "BIP-110 BTC" that exists on the chain with two blocks is economically worthless. It won't be listed on any reputable exchange. Don't touch it.
Second, the real signal is in miner behavior. Watch for any public statements from major pools about transaction filtering or fee restructuring. If Antpool or F2Pool starts talking about "clean blocks" as a service, that's a bigger deal than any failed UASF.
Finally, this event reinforces a core truth: Bitcoin's consensus is not a document or a vote. It's a physical, economic force. The merge wasn't that simple, but the fork was a disaster. The hackers didn't hack—they listened to the market. And the market said no.
So what's next? The next BIP will be smarter. It will come with miner incentives, not just node coercion. And the Ordinals community will need to build a moat—not just inscriptions, but actual value that miners can't afford to ignore. The clock is ticking.