Bitcoin split into two chains overnight. But the enforcing branch died after just two blocks. The narrative of a contentious fork, one that had exchanges scrambling and node operators bracing for impact, evaporated into a silent miner boycott. As of 6:34 a.m. UTC on Aug. 9, the dominant chain stood at block 961,690, while the BIP-110 enforcing branch remained frozen at 961,633—its last block roughly eight hours old. The ghost of a fork, but no real conflict. That's the story the chart hides, and I'm here to hunt it.
Context: The BIP-110 Mandatory Signaling Window
BIP-110 is a proposed temporary soft fork that restricts several methods of embedding arbitrary data into Bitcoin transactions. Think of it as a spam filter: it aims to keep the blockchain focused on money, not NFT metadata or unverifiable claims. Its activation mechanism uses a 55% threshold—1,109 out of 2,016 blocks must signal version bit 4 during the mandatory signaling window from height 961,632 through 963,647. If the chain reaches 963,648 with the threshold met, the proposal enters LOCKED_IN, and becomes ACTIVE at height 965,664. Simple enough on paper.
But the reality is messier. The window opened at height 961,632, and enforced nodes immediately began rejecting blocks without the signal. The dominant chain, however, kept producing blocks without a single bit-4 flag. In the first 59 blocks, zero signals. The enforcing branch, run by miners using OCEAN, managed two blocks—at 961,632 and 961,633—and then stopped. For enforcing nodes, this is a consensus split. For the rest of the network, it's a minor glitch.
Core: The Data Behind the Narrative
Let's trace the ghost in the code. I reviewed the block headers of the dominant chain's first 59 blocks in the window. Foundry, F2Pool, AntPool, ViaBTC, and MARA all contributed blocks—none with the signal. The BGeometrics data shows BIP-110 miner signaling at a paltry 0.42% since May 1. That's not a near-miss; it's a boycott. The split is real in a technical sense: enforcing nodes see a different chain. But the proof-of-work weight is overwhelmingly on the side of the non-signaling majority.
Why does this matter? Because the narrative of a "Bitcoin split" triggers FOMO and FUD. Exchanges like Coinbase and Kraken reported normal operations, but the perception of a fork can cause panic. Yet the data tells a different story: miners are not just indifferent—they are actively ignoring the proposal. The enforcing branch produced two blocks from OCEAN, then nothing. Over eight hours, no other pool joined. This is not a signal of support; it's a signal of apathy or opposition.
Based on my years of auditing blockchain governance mechanisms, I've seen this pattern before. A proposal with genuine technical merit can fail not because of flaws, but because of miner coordination. Miners hold the keys to activation, and they have a veto. In this case, the veto is silent. They don't need to vote against; they just need to not vote for. The BIP-110 state machine requires 55% of blocks in a 2,016-block window. With 59 blocks and zero signals, the probability of reaching that threshold is already negligible. The window still has 1,957 blocks remaining, but the momentum is dead.
Contrarian: The Boycott Is the Story
The conventional take is that BIP-110 failed because it lacked support. But the contrarian angle is more nuanced: the failure reveals a deeper tension in Bitcoin's governance. The proposal's supporters argued that arbitrary data (like inscriptions or ordinals) clogs the network and degrades user experience. Opponents say filtering valid transactions weakens Bitcoin's neutrality. The miner boycott, however, isn't about ideology—it's about economics. Miners earn fees from those transactions. By not signaling, they protect their revenue stream. The narrative didn't die because of a technical flaw; it died because of an economic incentive misalignment.
Furthermore, the node-count surge reported earlier this year—where a sudden wave of BIP-110 signaling nodes appeared—now looks like a coordinated attempt to inflate support. Jameson Lopp flagged that as a possible actor posing as thousands. The real signaling rate from miners tells the truth. The fork is a ghost, but the ghost is a warning: miner veto power is absolute, and any proposal that threatens their fee income will be silently boycotted.
Takeaway: The Next Narrative
So what's next? BIP-110 is effectively dead. The enforcing chain will likely never reach LOCKED_IN. The question is whether this triggers a reaction from the community. Will there be a push for alternative activation mechanisms, like BIP-9 or BIP-8 with mandatory lock-in? Or will the miner boycott become the new normal for controversial proposals? I hunt the story that the chart hides, and this time the chart shows a flat line where the fork should be. The takeaway is clear: Bitcoin's governance is not a democracy of nodes; it's a plutocracy of hashrate. The narrative of a decentralized, permissionless upgrade process is a myth sustained by silence. The next time a proposal threatens miner revenue, expect the same silent veto. The ghost fork of BIP-110 is just a preview of the battles to come.
Mining for meaning in a sea of volatility, I see a pattern: the market may be euphoric, but the technical foundations are always under pressure. The BIP-110 episode is a reminder that code is not law—miner incentives are. And until that changes, every contentious fork will be decided not by votes, but by vetoes.