BIP-110 Fork Is Already Dying: 18 Blocks Behind and No Miner Support

The BIP-110 chain fell 18 blocks behind the mainnet within hours of its split. That number is not a bug. It is a verdict. At block 961,632, a subset of Bitcoin nodes running BIP-110 patches began rejecting blocks that did not carry a specific signal flag. The mainnet has since advanced to 961,651. The fork chain sits at 961,633. In other words, the mainnet produced 19 blocks while the fork produced exactly one. This is not a contested fork. This is a minority client executing a policy that no economic majority requested. I have watched enough chain splits to know that the first twelve hours determine the trajectory. The BIP-110 fork is not a competing chain. It is a corpse with a block header. The signal history makes the picture worse. Only 51 blocks in the previous difficulty period signaled support. That is 2.53% of the 2,016-block window. BIP-9 style activation typically requires 95% miner signaling. BIP-110 is nowhere near that threshold. It does not even have enough support to be called a protest. It is a whisper. What BIP-110 actually proposes is not a technical upgrade. It is a restriction. The proposal limits non-financial data writes to Bitcoin blocks, which is a direct attack on Ordinals inscriptions and the BRC-20 ecosystem. No new cryptographic primitive. No signature scheme. No scalability improvement. Just a rule that says: certain data no longer belongs in blocks. I audited the void and found a backdoor. The backdoor here is not in the code. It is in the activation mechanism. BIP-110 is being pushed through what looks like a User-Activated Soft Fork (UASF) approach. Nodes enforce a rule that miners did not approve. Historically, UASF creates a period of chain uncertainty. BIP-148 in 2017 was the famous example. The difference is that BIP-148 had broad community momentum. BIP-110 has 2.53% miner support and a fork chain that cannot even keep up with block production. The hash power ratio between the chains is brutal. Based on block production rates, the fork chain is running at roughly 5-6% of mainnet hash power. That is within the range of 1/20 to 1/5 of the mainnet. At that level, the chain is not secure, not viable, and not economically rational for any miner to join. The only miners on that chain are either ideologically committed to restricting Ordinals, or they are speculating on a future narrative shift. The token economics of this fork are close to zero. The fork shares Bitcoin's full supply history, which means every BTC holder now technically has a claim on a parallel chain with 5% hash power. But no exchange will list it. No liquidity will flow to it. No application will build on it. The terminal value of BIP-110 chain coins approaches zero with high confidence. What matters more is the Ordinals side. BIP-110 is a direct attempt to cap the data space that inscriptions consume. If it activated, new inscription minting would be curtailed for one year, the defined duration of the rule. Existing assets would remain transferable, but new issuance would face a consensus-level barrier. That would materially change the fee market for block space and the economic model of BRC-20 tokens. But the probabilities do not support that scenario. The signal rate is 2.53%. BIP-110 cannot activate at this rate without either a dramatic shift in miner behavior or a sustained UASF campaign that forces the issue. Both are unlikely in the current market cycle. Floor sweeps are just data points in motion. The BIP-110 fork chain is the same thing. It is a data point showing that a small, organized group can force a node-level policy, but cannot force a miner-level consensus. The contrarian angle here is not that BIP-110 will succeed. The contrarian angle is that Ordinals supporters should be paying attention to the precedent, not the price. A UASF-style restriction, even if it fails this time, establishes a playbook for future attempts to regulate block content. The next proposal may not target Ordinals. It may target tokenized data, or state commitments, or something that is not even deployed yet. I have audited protocols where the risk was not in the function logic but in the governance mechanism that could change the function logic. BIP-110 is exactly that shape. The rule itself is simple. The mechanism to enforce it bypasses miner consensus in a way that creates structural uncertainty. That is the real flaw. Smart contracts execute truth, not intent. Bitcoin's consensus rules are supposed to follow the same principle. BIP-110, as implemented by this minority fork, executes intent. It executes the intent of a small group that wants to define what Bitcoin blocks are for. That is a governance question masquerading as a technical one. The fork chain will die. That outcome is nearly certain. The question that matters is whether the idea dies with it. BIP-110 has exposed how thin the line is between node policy and network consensus. A 2.53% signal rate should not produce a chain split. The fact that it did means the activation threshold assumption is weaker than the market believed. Institutional allocators and Ordinals traders should watch the next signaling period, not the current block height. If support remains below 5%, the fork is a non-event. If support climbs above 20%, the narrative shifts from fringe to organized. Those are the data points that inform position sizing. The 18-block gap is just noise. I audited the void and found a backdoor. The backdoor was not in BIP-110's code. It was in the assumption that a fork requires economic majority to be dangerous. It does not. It only requires enough nodes running a patch to create temporary ambiguity. That ambiguity is a fee event, a risk event, and a signal event. The question is who is watching. The next 12 months will reveal whether BIP-110 is a failed experiment or the first iteration of a longer campaign. The fork chain will fade. The proposal may return. Bitcoin does not fork easily, but it debates relentlessly. That debate is the real market now.