BIP-110 Fork Died in Eight Hours: The Hashrate Production Record

At block height 961,632, a minority of Bitcoin nodes executed a unilateral rule change. They rejected every block that did not include a BIP-110 signaling bit. The result was a parallel chain that produced exactly two blocks in the following eight hours. The main chain, meanwhile, advanced forty-seven blocks to 961,681. This divergence is neither political drama nor a minor bug. It is a hashrate audit written into the chain itself. In a network with a ten-minute average block interval, two blocks against forty-seven is a near-perfect measure of miner conviction. I ran the numbers as soon as the report crossed my desk. The fork chain's effective hashrate was just above four percent. That is not a network. That is a liability. Context is why this happened. BIP-110 is a Bitcoin Improvement Proposal that attempts to restrict block space to financial transactions, specifically targeting Ordinals inscriptions, BRC-20 tokens, and other data-bearing outputs. Its sponsors frame it as purification; its critics see it as an attempt to eliminate a competing asset class. The proposal did not follow the standard BIP-9 activation path, which demands 95% miner signals over a 2016-block difficulty window. Instead, it deployed a user-activated soft fork (UASF) with a flag day. Client nodes were patched to reject any block lacking the BIP-110 signal, regardless of miner intent. The stated activation threshold was 55% of blocks. The previous cycle recorded 51 of 2016 blocks carrying the signal — a 2.53% support ratio. The chasm between 2.53% and 55% is not a negotiation dynamic. It is a structural absence. The fork triggered on August 9 at height 961,632. The alt chain produced block 961,633 and then largely went quiet. Over eight hours, only one additional block appeared. The main chain reached 961,681 without breaking stride. No major mining pool declared support. No exchange listed the fork token. The only visible activity came from a small cluster of nodes running self-compiled versions of Bitcoin Core. These are the mechanics of a failed mutiny. Now examine the production record as a market signal. Eight hours equals 28,800 seconds. At the target interval of 600 seconds per block, the network is expected to produce forty-eight blocks. The BIP-110 chain produced two. That is roughly four percent of total hashrate. The number is consistent with the 2.53% signal rate, once you allow for variance and the possibility that some of those signaling miners continued to point a small portion of their machines at the fork. In other words, the signals were honest. The problem is that honesty does not create security. A four percent hashrate chain is a hostage. Any miner or pool controlling more than four percent of global hashrate can reorganize the chain at will. That condition describes nearly every commercial mining operation in the industry. The BIP-110 fork chain does not enjoy independent security; it exists only because the rest of the network has not decided to extinguish it. This is the definition of a zombie chain. No exchange can responsibly list its token, and no rational user will accept its transactions as final. The security math is even uglier when you account for confirmation times. A chain with four percent hashrate cannot give its users a reasonable finality guarantee. A normal six-block confirmation would take, on average, two and a half hours, and even then a reorg remains trivial. For any participant with meaningful capital, the fork chain is unusable. This is not an opinion; it is a calculation from the block interval distribution. There is also the question of who mined those two blocks. The report does not name the miners. Based on my experience with failed forks, the participants are likely small pools or individual miners with ideological motives, not commercial entities. The absence of hashrate continuity proves they did not have a business plan. They had a patch. Miners had an even more direct reason to reject the proposal: economics. Ordinals transactions have emerged as a meaningful source of fee revenue. During peak inscription activity, fees from these outputs represent a measurable share of miner income. BIP-110 would render those outputs invalid, eliminating that revenue stream. From a tokenomic standpoint, the proposal is a unilateral transfer of value away from miners and toward a small ideological faction. Miners respond to incentive signals encoded in their balance sheets, not in philosophical whitepapers. The failure of BIP-110 is a textbook case of misaligned tokenomics. The asset-side consequence is just as clear. Had BIP-110 activated, BRC-20 tokens and inscriptions would lose their validity under the new rules. Wallets and indexers would face a binary choice. Liquidity would collapse as exchanges paused or delisted the affected assets. The fork failure removes that terminal risk. For current Ordinals holders, this is a short-term positive. It does not make the assets safe. It simply cancels one particular failure mode. The tokenomic asymmetry is worth exploring further. BIP-110 would have reduced the value of block space for data-heavy applications while not increasing any other utility. In economic terms, it is a supply-side restriction with no corresponding demand-side increase. The result would be lower miner fees, lower network security, and a higher real cost per financial transaction. The main chain would become more expensive for ordinary users, not less. That is the opposite of scale. I have audited enough protocol code to recognize a structural assumption failure. In 2017, I spent three weeks tracing an ICO smart contract and found three integer overflow bugs. The team had a polished website but no testnet. My report was ignored until the project collapsed. That lesson shaped my entire approach: code is only as valid as the environment in which it is deployed. In 2023, I reverse-engineered EigenLayer's slasher system and found a bond edge case not documented in their materials. The core team patched it before mainnet. Both cases share the same pattern with BIP-110: the logic may be internally sound, but the incentive layer is broken. When the people who must enforce a rule have no economic reason to do so, the rule becomes a suggestion. Let me stress-test the proposal's assumptions the way I would a smart contract. The first assumption is that node operators can dictate protocol rules. That is false; they can only express preferences. The second assumption is that a 55% threshold is a reasonable consensus. Bitcoin's own history suggests otherwise. The BIP-9 mechanism settled on 95% for a reason: any lower bar invites disputes. The third assumption is that Ordinals transactions are a net negative. The data says they have brought new users and fee diversity to the ecosystem. Each assumption fails under examination. Let's walk through the order flow during those eight hours. The fork chain minted two coinbase rewards, approximately 6.25 BTC plus transaction fees. That BTC is stranded. It cannot be moved to the main chain without a trusted two-way peg. No legitimate team will build such a peg for a chain with four percent hashrate and an unknown operator. The only realization path is exchange listing, which would require a plausible due-diligence story. No credible exchange would review a chain that produced two blocks in eight hours and conclude that it deserves liquidity. The order flow stayed on the main chain, where 47 blocks continued to capture economic activity. Capital seeks security, not ideology. The order flow analysis has a practical trading application. If you monitor the fork chain's block production and see it climb to one block per hour or more, that would signal a shift in miner behavior. As of the report, the production rate was 0.25 blocks per hour. That is less than the noise level of the main network. Any rally in a fork token based on such production is a short-selling opportunity, not a long-term investment. Bitcoin has a history of forks, and each successful one had real economic backing. Bitcoin Cash drew in major miners and exchanges in 2017. Bitcoin SV had a deep-pocketed promoter in Craig Wright. BIP-110 had none of that. It had a handful of nodes and a 2.53% signal count. This is why the governance lesson is unambiguous: a flag-day partition heals by abandoning the side with less work. Consensus is not a vote; it is a production record. The main chain's uninterrupted output to 961,681 proves where the economic majority stood. The governance health of Bitcoin is often judged by the strength of its social contract. This event proves the social contract is still intact, but only because miners provide the enforcement. The 'users' who ran BIP-110 nodes exercised a form of minority rule that was invalidated by the majority's production. That is a healthy outcome, but it is also a warning: if miner economics and user values ever diverge enough, the same mechanism that stopped this fork could eventually drive one. But there is an uncomfortable layer underneath. The anti-inscription movement did not disappear with the fork. It lost a battle, not the war. Forced activation was always the bluntest instrument, and it failed because it ignored miner incentives. The next attempt will likely be more sophisticated. A future proposal might target fee structures, making inscription-heavy blocks unprofitable for the miners themselves. Alternatively, miners could individually implement transaction selection filters that drop Ordinals outputs, no consensus change required. That would achieve the same goal without a dramatic fork. It would be less visible, harder to resist, and more dangerous to the ecosystem. Regulatory risk is the second hidden consequence. The fork's failure demonstrates that Bitcoin cannot easily self-limit in response to political pressure. The SEC and other regulators have already shown interest in inscription-based assets. If the protocol refuses to restrict them, external policymakers may see a justification for intervention. A government-mandated ban on certain Bitcoin transactions would be a far greater structural shock than any soft fork. The short-term survival of Ordinals may actually invite that outcome. The victory is a honeypot. For traders, the actionable level is straightforward. Do not touch any token labeled BIP-110 or fork-derived. If a minor exchange lists a fork token, the reorg risk alone makes it a guaranteed loss. Avoid the narrative noise. Monitor the next miner signaling period. If a similar proposal approaches 90% support, then treat it as a serious threat. Until then, the production record is the only meter that matters. We do not predict the future; we hedge against it. Structure defines value; chaos destroys it. The structure here is the 47 blocks that kept going, not the two that stopped.