Two Blocks, Eight Hours, One Veto: The BIP-110 Fork Was Never a Fork — It Was a Hashrate Referendum

Two blocks. Eight hours. Height 961,633. Then nothing. On August 9, at block height 961,632, Bitcoin nodes running a modified client enforcing BIP-110 executed a forced activation. The rule was unambiguous: reject any block that does not carry the proposal's signaling bit. Standard Bitcoin Core nodes and BIP-110 nodes split at that height, producing a de facto chain fork. Within eight hours, the BIP-110 chain had produced exactly two blocks — block 961,633 and nothing after it. The main chain advanced to 961,681 and beyond, adding more than forty blocks in the same window. The arithmetic is unforgiving. Bitcoin targets a ten-minute block interval. Eight hours of theoretical production capacity is forty-eight blocks. The fork chain produced two. That places its effective hashrate at roughly four percent — and that figure is an upper bound, because the Poisson distribution of block-finding events at such a small sample size means two blocks in that window is statistically indistinguishable from a chain with two percent, one percent, or even sub-one-percent hashrate. No plausible scenario exists in which the BIP-110 chain was ever secure, economically viable, or close to constituting a competing consensus. But the failure was not a technical malfunction. The code executed exactly as written. The failure was a valuation event. The market priced the fork chain's blockspace at zero, and no economically rational miner extended it. In Bitcoin, that is the only consensus mechanism that actually matters. I have spent years auditing protocol-layer logic: consensus clients, governance contracts, incentive-alignment rules. A failure mode recurs across nearly every governance episode I have examined in this industry's history, and BIP-110 is a pure specimen: substituting code enforcement for consensus-building. Code defines what is possible. Consensus defines what persists. The BIP-110 proponents wrote a rule, forced it at node level, and assumed that was sufficient to produce a new Bitcoin reality. The network's answer was a two-block chain with no economic weight. Context matters, because the mechanism is more revealing than the narrative. BIP-110 was not a scaling proposal. It had no throughput ambitions. It was a restriction mechanism targeting the most commercially active transaction category on Bitcoin's main chain: non-financial data writes. In ecosystem terms, that means Ordinals inscriptions and BRC-20 token operations. The proposal's ideological foundation rests in the Bitcoin-purity position: blockspace should be reserved exclusively for financial transfers, and data-bearing inscriptions are network spam that dilutes the chain's monetary signal. That position has a coherent internal logic. It also has a coherent economic opponent: the miners, who receive a meaningful share of their revenue from inscription-related fees. And the miners hold the only vote that matters. BIP-110 asked them to vote for a pay cut. To understand what actually happened, you have to read the activation mechanism closely. Standard Bitcoin upgrades follow BIP-9: miners embed signal bits in block headers, signals accumulate over a difficulty-adjustment period of 2,016 blocks, and activation occurs only after a designated threshold — conventionally 95% — is reached. The design is deliberately miner-majoritarian and deliberately slow. BIP-110 broke from this process twice. First, its activation threshold was set at 55%, far below the consensus norm — an attempt to lower the bar to a level that might plausibly be reached. Second, and more consequentially, the client implemented a flag-day activation rule. At the preset height of 961,632, acceptance of non-signaling blocks simply stopped. No threshold verification. No gradual accumulation. A hard-coded binary switch that flipped on a fixed date, converting node validation into political enforcement. This is the User-Activated Soft Fork pattern — UASF — the same architecture as BIP-148 in 2017. The comparison, however, fails under scrutiny. BIP-148 had near-universal node support, a precisely time-boxed objective (forcing SegWit lock-in after years of miner signaling obstruction), and a credible majority-hashrate threat behind it. BIP-110 had none of those preconditions. The prior cycle's signaling data is dispositive: 51 of 2,016 blocks carried BIP-110 support. That is 2.53%. Against a 55% gate, this is not a controversial minority. It is a total absence of multistakeholder mandate. Let me zoom in on what a 2.53% signal rate actually communicates. In Bitcoin's governance history, even contentious proposals accumulated meaningful early support. SegWit, for all its controversy, reached activation thresholds through sustained miner signaling. The Taproot activation of 2021 passed with overwhelming support. BIP-110's 51 blocks out of 2,016 — across an entire two-week difficulty period — is not a low polling number. It is a complete failure of persuasion. No meaningful constituency among miners, node operators, or users chose to align with the proposal before it launched. The activation despite this backdrop was not an exercise of democratic process. It was a violation of the social contract that keeps Bitcoin governance functional. The signature of this governance pathology is familiar to anyone who has read the code: a client that decided to hold a network hostage to an ideological rump. And the miners, acting with near-total coordination, responded by not responding. Their abstention was the network's verdict. Now the security analysis, because the fork's corpse has a lesson for anyone tempted to interact with it. A chain at four percent hashrate or below is trivially attackable. Any entity with access to moderate hashrate — a mid-tier pool, a rented burst, a coordinated cluster of small miners — can reorganize the BIP-110 chain at a cost that is orders of magnitude below an equivalent attack on the main chain. The fork chain's two-block existence implies no security budget, no checkpoint protection, and no community willingness to defend it. If any exchange had listed the fork's native tokens, those tokens would carry a 51% attack price measured in thousands of dollars and a liquidity floor of zero. I have examined dead-fork dynamics since the 2017 BCH split. The decisive variable is always hashrate participation. BCH retained value because it captured a legitimate fraction of mining power and built exchange infrastructure. BSV degraded precisely as its hashrate remained a shrinking fraction of the network. The BIP-110 chain skipped straight to the terminal state: no hashrate, no liquidity, no users, no future. The tokens on it — call them "fork BTC" — are artifacts with no market anchor. They will approach zero value asymptotically. Any exchange that lists them is assuming regulatory exposure while offering a product with negative technical prospects. The economic dimension is where the real governance signal lives. Miners are not ideological actors in the long run. They are capital allocators. A miner deciding whether to extend a fork chain performs a straightforward calculation: expected revenue from the fork chain's blocks minus the opportunity cost of the main-chain blocks forgone. The fork chain's expected revenue is zero. No liquidity. No user demand. No fee-market history. And, by design, no inscription traffic. The opportunity cost is not abstract: Bitcoin's main chain fee market, buoyed at the margin by Ordinals transactions, generates the revenue that keeps mining operations solvent — especially in the post-halving environment, where the base subsidy was cut in half. The prior cycle's signal data — 51 out of 2,016 blocks — is not a random sampling artifact. It is a public, non-binding disclosure of economic intent across the entire mining ecosystem. Nearly every miner declined to align with BIP-110 before the fork even launched. The activation despite this backdrop was a deliberate confrontation, and the miners' response — unanimous non-participation — was the cheapest possible enforcement of Bitcoin's governance contract. There is a deeper structural reading here that most commentary misses. The Ordinals fee stream has integrated itself into miner income models since early 2023. Data-heavy inscriptions consume significant blockspace and pay disproportionate fees relative to simple transfers. BIP-110's design would have eliminated that revenue category outright. It was, in subsidy-adjusted terms, a proposal to reduce miner revenue at precisely the moment the subsidy halving made fee income more important than ever. The miners did not need to debate the merits of inscription-based NFTs. They needed to value the blockspace market and protect their share of it. The outcome — forty main-chain blocks versus two fork blocks — is the market's version of a unanimous vote. For the Ordinals ecosystem, the fork's death is unambiguous tail-risk clearance. The existential threat was never the fork chain itself; it was the precedent that a node-level enforcement rule could make data-bearing transactions invalid through unilateral action. The failure eliminates that precedent for the medium term. The reputational damage to forced-activation proponents — transparently measurable in the 2.53% support signal — will deter similar attempts. No serious developer wants to attach their name to a proposal that nets two blocks in eight hours. But that is where the narrative gets its contrarian twist, and it deserves careful attention. BIP-110's failure is not a victory for Ordinals. It is a consolidation of miner power — and that consolidation is a conditional protection, not a principled one. The miners did not vote for inscriptions because they believe in Bitcoin-native art. They voted for fees. The same fee stream that protected Ordinals today can be redirected tomorrow through a far quieter mechanism: pool-level transaction selection policy. A mining pool can decline to include data-heavy transactions in its block templates without changing a single line of consensus code. That is not a fork. It is not a BIP. It is an economic filter. And it is strategically invisible compared to a contentious activation. This is the attack vector the Ordinals community should actually be watching. The next phase of this conflict will not produce an identifiable block-height failure. It will produce a gradual degradation of inscription inclusion rates, an increase in mempool latency for data-heavy transactions, and an erosion of Ordinals utility through fee-channel friction — all without a single protocol-level change. The first wave was code. The second wave will be policy. And unlike BIP-110, pool-level filtering is reversible, deniable, and nearly impossible to classify as a governance attack. It is simply a pool optimizing its own block template construction. The strategic lesson extends beyond Ordinals. Anyone building on Bitcoin's main chain — whether they are issuing BRC-20 assets, deploying ordinal-based protocols, or experimenting with inscription-adjacent infrastructure — now knows that their survival depends on the continued economic alignment of miners. That alignment is contingent on fee revenue. The moment inscription fees cease to be material, the tolerance evaporates. Builders who understand this will maintain fee-generating utility rather than speculative issuance. Builders who ignore it will wake up one morning to find their transactions systematically excluded from block templates, with no protocol-level recourse available. Regulators receive a footnote in this story. BIP-110's failure has a counterintuitive consequence for the compliance landscape. Had the proposal succeeded, Ordinals assets would have been eliminated at the protocol layer — a technical answer to what regulators treat as a securities-law question. The failure preserves the gray zone. Inscription-based assets continue to exist, continue to trade, and continue to invite scrutiny under the Howey test. The SEC's enforcement posture toward NFT-like assets does not shift because a fork died. If anything, the event clarifies that regulatory outcomes will be determined through legal channels, not through code choices. That is a less elegant path, but also a more transparent one. From a node operator's perspective, the event carries a usability warning. Running a BIP-110 modified client means isolation from the canonical chain. The fork's two-block output is not a foundation for anything — it is a cliff. Any node operator who adopted the modified client must revert to standard Bitcoin Core and perform a chain reorganization manually. The operational cost of ideological enforcement is paid not by the proposal's authors, but by the operators who trusted them. That asymmetry is another reason the UASF path is now effectively discredited for low-support proposals. What should be watched going forward? Three signals. First, terminal-state confirmation. If no additional blocks appear on the BIP-110 chain within days, the fork is inarguably dead. The probability of resurrection is low — the hashrate coalition that declined to participate once will not reverse a unanimous decision. Second, fee composition. The share of Ordinals transactions in Bitcoin's total fee revenue is the variable that determines whether miners' tolerance for data-heavy blockspace persists. If the post-halving fee environment pushes pools toward different revenue optimization strategies, the BIP-110 faction's restriction ideology could resurface through the economic channel described above — without a single BIP number. Third, the migration of restriction ideology. With forced activation discredited, proponents will shift toward mempool policy proposals, pool-incentive analyses, and community-level narratives about blockspace "purity." The battle will be more diffuse, harder to audit, and more dependent on economic argument than on code enforcement. Bitcoin is not governed by code. It is governed by hashrate, by fee revenue, and by the decentralized choices of economically motivated actors deciding which ledger to extend. Code is the language of proposals. Blocks are the only votes that matter. BIP-110 produced two votes. The main chain produced forty. Turnout was the verdict. The cleverest attacks on Bitcoin's open blockspace will never arrive as contentious forks with low hashrate. They will arrive as default configuration changes inside mining software, as mempool policy adjustments, as invisible economic filters. The fork is dead. The conflict is not.