BIP-110 Is 18 Blocks Behind: A Hash Power Autopsy of a Stillborn Fork

Block 961,651. Block 961,633. The distance between those two numbers is the entire story of the BIP-110 chain split. Eighteen blocks. Since the fork point at 961,632, the Bitcoin mainnet has produced nineteen blocks. The BIP-110 fork chain has produced exactly one. That is not a fork. It is a stillbirth. The chain that chose to enforce BIP-110 — a node-level soft fork designed to restrict non-financial data writes, including Ordinals inscriptions — has been running at roughly five percent of mainnet hashrate. In a system where security is measured in cumulative proof of work, five percent is not a minority faction. It is a rounding error. I have spent eighteen years in this industry. I have watched chains die for pride and die for principle. The mode of death is always the same: arithmetic first, then consensus, then the market. BIP-110 is in the first phase right now. The arithmetic is not favorable. We do not guess the crash; we trace the fault. The fault here begins at 961,632 — and everything after it is just the record of a wound that never healed. Let me be precise about what BIP-110 actually is. It is not a code fork in the traditional sense. It introduces no new cryptographic primitives, no signature scheme upgrades, no performance changes. Block size and block interval remain untouched. What changes is the permitted use of block space: inscriptions like Ordinals and BRC-20 token mints become non-compliant. It is, in essence, a data policy proposal written into consensus rules — a rule modification that treats non-financial data writes as violations of network policy. The activation mechanism follows a BIP-9-style signaling pattern. Approximately fifty-five percent of blocks in a 2,016-block window must carry a support signal before the rule activates. Once activated, the restriction lasts roughly one year. That is the full technical surface area. No new primitives. No new features. A restriction, not an expansion. Comparing it to Taproot — which introduced MAST and Schnorr signatures — is comparing a door frame to a cathedral. BIP-110 adds nothing; it subtracts a use case. The support level tells you everything. In the last signaling window, fifty-one blocks out of 2,016 carried the BIP-110 signal. That is 2.53 percent. The threshold is 55 percent. The distance between 2.53 and 55 is not a debate; it is a chasm. To put that in terms any finance professional understands: this proposal has less support in its intended constituency than a failed proxy resolution has in a shareholder meeting. It did not lose the vote. It was not at the vote. It was in the parking lot. Now the fork itself. At block height 961,632, nodes running the BIP-110 patch began rejecting blocks that did not include a support signal. This is textbook UASF behavior: user-activated, node-enforced, miner-ignored. We have seen this pattern before. In 2017, BIP-148 ran on similar logic. But BIP-148 had substantial community momentum and eventual miner accommodation. SegWit2x, by contrast, was miner-led and collapsed under user resistance. BIP-110 has neither the miners nor the users. It has a patch, a few nodes, and eighteen blocks of attrition. Now let me run the numbers the way I would in a due diligence audit. The block height differential gives us a rough hashrate estimate. Mainnet produced nineteen blocks; the fork produced one. Assuming similar difficulty, the fork chain commands roughly one-nineteenth to one-twentieth of mainnet hash. Call it five to six percent. At that level, the fork chain's average block interval stretches to roughly one hundred minutes — ten times the mainnet's ten-minute target. The chain is not producing blocks; it is producing occasional witnesses to its own decline. That is not survivable. Not over days, not over weeks. A chain at five percent hashrate is vulnerable to the simplest possible attack: a 51 percent assault on a 6 percent chain requires less than 4 percent of total Bitcoin hash. Any large mining pool could destroy it in hours. The fork chain is not competing; it is waiting to be deleted. I have traced this exact failure mode before. In May 2022, when Terra's UST depegged, the market narrative blamed a death spiral. My team's code-level analysis found something different: a race condition in the seigniorage share distribution logic inside Anchor Protocol that cascaded during high volatility. The price action was a symptom. The architecture was the cause. The same lens applies here. BIP-110's architecture — a signaling-based activation gated on miner support — was always going to produce a fragile minority chain if the miners refused to signal. That fragility was not a design flaw. It was the arithmetic consequence of a proposal without consensus. The economics compound the problem. A fork chain at five percent hash power produces roughly 2.4 blocks per hour on good days. Its transaction fee income is negligible. Its miners are subsidizing a chain the market does not recognize. Exchanges will not list a chain that cannot secure itself. Liquidity will not flow to an asset nobody can trade. The fork chain's coin is financially indistinguishable from an unlisted token with zero volume. Terminal value: zero. Confidence: high. For the Ordinals ecosystem specifically, I want to be precise. BIP-110 does not threaten existing inscriptions. The proposal restricts new non-financial data writes. Existing assets remain transferable, in the sense that the underlying UTXOs still exist. But the creation of new inscriptions and BRC-20 token mints would be constrained during the activation window. If the proposal ever activated, the Ordinals economy would not disappear — it would freeze in place. No new supply. No new mints. Just a library of existing artifacts, locked in amber. Here is the key insight most commentary misses: the Ordinals ecosystem is the reason this proposal exists, but it is also the reason the proposal will fail. Miners derive meaningful fee income from inscription activity. The 2.53 percent support level tells you that miners are not suffering under Ordinals; they are profiting from them. A rule that removes a revenue stream will never reach 55 percent signal support unless the fee environment changes dramatically. That is the arithmetic of self-interest, and it is the strongest resistance BIP-110 faces. Verification precedes trust, every single time — and the verification here is straightforward: check the signaling blocks, check the fee data, check the incentive alignment. It is not aligned. I also need to flag a governance detail. The proposal has a roughly one-year window. That means there are multiple 2,016-block signaling cycles left. The 2.53 percent is a snapshot, not a prophecy. If inscription-driven fees collapse — say, if the bear market suppresses mint activity to negligible levels — miners might see less reason to protect that revenue. If a major security incident involving inscriptions occurs, the political calculus shifts. The threshold remains distant, but the window is wide. Predicting the death of a proposal that has not yet expired is premature; predicting the death of a fork chain that is already eighteen blocks behind is arithmetic. The fork chain, I will be direct, is not viable. It will either reorg back into mainnet or be orphaned into irrelevance. The proposal, however, is a different question. It is weak. It is under-supported. But it is not dead until the window closes. Now let me step back and say something uncomfortable. The blind spot in this analysis is not the fork. It is the precedent. BIP-110's critics and supporters are both misreading the event. The supporters think a minority chain is a showing of strength. It is not. Five percent hashrate is not a negotiation position; it is a casualty count. The fork chain's existence does not legitimize BIP-110. It merely demonstrates that node software can always be patched to reject blocks, regardless of network consensus. That is a feature of Bitcoin's permissionless design — and a liability of it. The critics, meanwhile, celebrate the fork's weakness as proof that BIP-110 is irrelevant. That is complacency. The fact that a UASF-style activation was attempted at all — even at 2.53 percent support — establishes something new: the normalization of node-enforced policy changes as a pressure tactic. We are in a bear market. Minority forks are cheap to run. If nodes can threaten chain splits over data policy, they can threaten chain splits over anything. The next BIP might target a different class of transactions. The mechanism, once demonstrated, becomes reusable. In 2017, we argued about block size. In 2022, I spent three weeks tracing the actual race condition in Anchor's code while everyone else watched the price action. In 2026, we are arguing about what data belongs on a monetary ledger. BIP-110 is the first shot in that argument, delivered by a chain that is eighteen blocks behind. History will not judge the fork's viability. History will judge the door this attempt has opened. The financial engineering parallel is worth drawing. In my forensic audit of the 2x Capital leverage token contracts in 2017, I found three slippage calculation errors that the whitepaper's math model did not reveal. The public-facing document was coherent. The implementation was broken. The same pattern repeats here: BIP-110's proposal document describes a clean policy outcome — restrict non-financial data. But the implementation path — a signaling soft fork with a 55 percent threshold — was never coherent with the actual distribution of miner incentives. The gap between marketing and code was the whole story, then and now. There is also a structural point about the fork chain's miners. They may not be true believers. That five percent hashrate could be strategic — miners hoping to mine rare blocks that might later carry an airdrop value, or pools running the patch on a trial basis. I have seen this behavior before in minority forks. The loyalty is transactional. When the transaction stops paying, the hash disappears. The fork chain is not a movement; it is a position that can be closed. The real question is not whether BIP-110 dies. It will. The question is what the next BIP-110 looks like — and whether it arrives with 20 percent support, or 40 percent, or the full 55. I will be watching the next signaling window. So should anyone holding Ordinals assets, and anyone who believes that consensus rules should change only when the consensus actually agrees. The fork chain will be orphaned. The Ordinals ecosystem is safe from immediate restriction. Those are the easy calls. The hard call is the signal BIP-110 has sent across the ecosystem: node-enforcement is now a political tactic, and data policy has become a consensus-layer battleground. Code is law, but history is the judge. The chain remembers what the ego forgets — and what the ego forgets, in this case, is that every failed fork leaves sediment behind. Each attempt normalizes the mechanism, regardless of the outcome. Watch the next signaling window. Watch the next proposal. The battle over block space has just begun. And the chain, as always, will keep the score.