BIP-110 Is Not a Fork. It's a Wish That Forgot to Check the Incentives.

At block 961,651, the Bitcoin main chain is still alive. At block 961,633, the BIP-110 chain is staring at a gap it cannot close. That is 18 blocks. That is also roughly one produced block versus nineteen. The signal count in the last period was 51 blocks out of 2,016, or 2.53%. Do not call this a fork. Call it a wish that forgot to check the incentives. I read the block headers before the headlines. The headers tell a simple story: the dissent is real, but the hashrate is imaginary. BIP-110 is a soft fork proposal, though 'proposal' is doing heavy lifting. It aims to restrict non-financial data writes to Bitcoin blocks for about one year. If you have been following Ordinals, you know what that means: inscriptions, including BRC-20 data, get a temporary time-out. The mechanism is not a new opcode or a cryptographic primitive. It is a simple rule tied to miner signaling, in the same family as BIP-9 style countdowns. The stated goal is to say that a Bitcoin block should be for financial settlement, not for JPEG storage. The actual effect of activation would be a one-year ban on new inscriptions, not a purge of existing ones. Existing assets can still be transferred; new minting would be constrained. The activation design is the first red flag. BIP-9 style signaling requires a supermajority to activate, usually 95%. This proposal reportedly wants about 55% of blocks in a 2,016-block period to carry the signal. Current support is 2.53%, which is not a near miss; it is a rounding error. Yet the chain split happened anyway. Nodes running BIP-110 simply rejected blocks that did not contain the signal at height 961,632. That is not a soft fork waiting for consensus. That is a UASF without the user majority. I have seen this pattern before. In 2017, BIP-148 was contentious, but it had broad social support and a clear coordinator. BIP-110 has neither. It has a fork that is already dying and a timeline that expires in about a year. One question nobody has answered: who compiled this patch under a BIP badge? The proposal described as BIP-110 has no disclosed peer-review record. The fork's existence is public, but its authorship is not. That is not open-source consensus. It is a unilateral deployment with a GitHub label. Let's do the arithmetic. If the main chain has produced 19 blocks while the BIP-110 chain has produced 1, the naive hashrate estimate is roughly 5% of the network. The confidence interval is ugly; with such a small sample, the true number could be as high as 20%. But even the bull case for this fork is eighteen blocks behind the main chain. It does not profit from its losses. It has no exchange listings, no stablecoin flows, no active DeFi. It has a rule change and a prayer. The miners who signal support may be ideological, but ideology does not pay power bills. A miner on a 5% hashrate chain faces a block interval stretched toward twenty times Bitcoin's average. Orphans become more likely, fees become thinner, and the chain's deepest liquidity—the security provided by the majority hash—is gone. Based on my audit experience, when a chain's hashrate drops below the threshold of patience, the chain falls into a death spiral. The BIP-110 chain is not falling; it has already fallen. The real metric to watch is not the 18-block gap. It is the next 2,016-block signaling window. If support stays below 5%, this episode is a footnote. If it jumps toward 40%, the market should stop laughing and start stress-testing Ordinals liquidity. A rule change that appears dead today can be resurrected tomorrow with better framing. I have audited enough minority chains to know the pattern. I spent 2022 reconstructing the Anchor Protocol's death spiral, and one lesson carried over: a model that depends on a tiny subset of actors to keep a system alive is not a model; it is a honeypot for entropy. BIP-110's security assumption is that 55% of miners will signal within a 2,016-block window. Current support is 2.53%. The assumption fails. In the absence of miner buy-in, the chain is a technical ghost. The logic held until the liquidity dried up. In this case, the liquidity is hashrate. The token economics section is unusually clean because no new token exists. Bitcoin's supply remains capped at 21 million. The fork coins are a mirror image with no separate issuance. Their terminal value is close to zero because no rational exchange will list a chain with less hashrate than a medium-sized mining pool and no legal or community entity willing to answer for it. The Ordinals economy is another story. If BIP-110 ever activated, inscriptions would face a one-year customs inspection. New mints would be artificially limited, and the data-space cost for BRC-20 projects would spike. That is not a monetary upgrade. It is a subsidy for existing inscription holders and a tax on new entrants. The governance layer is where the exploit lives. This is not a code vulnerability; the code is simple. The exploit is in the trust model. A small group of node operators has decided that their environmental view of block space should override both market demand and miner economics. They do not need a majority contract. They just need enough memory to run their own chain and enough stubbornness to say they are the true Bitcoin. History is not kind to that posture. The 2017 SegWit2x fiasco should have taught us that signaling thresholds are not norms, and minority chains are not communities. In my risk register, I would mark this as centralized veto: a few operators can force a temporary policy on the network without majority mining power and without public peer review. Code does not lie, but incentives do. The incentive here was always clear: there is no profit in a year-long timeout for Ordinals, but there is a lot of noise. Now the uncomfortable part. The BIP-110 supporters are not entirely wrong. Bitcoin block space is a shared resource, and the inscription era has made full-node operation costlier. Every JPEG that lands in a block becomes part of every node's permanently growing ledger. That is a real externality, not a moral panic. If a significant chunk of the network genuinely believes non-financial data is a problem, they have a right to push for a rule change. The correct path, though, is a normal BIP process: public review, realistic signaling, and a long runway. That process is slow and boring. It is also the only process that gives a rule change the one thing it needs: legitimacy. The fork's failure does not prove the concern is invalid. It only proves the method is broken. And the opponents who laughed at the fork may be missing a signal: the protest is alive even if the chain is dying. The next version will be better designed and will have more support. The question is whether the community will build a real proposal before the next protest builds a real minority. Ignoring the issue is not safer than debating it. Entropy always wins if you stop watching, and the entropy here is a growing stock of full-node data that nobody owns and nobody cleans. The deeper problem is the precedent. If any node operator can fork Bitcoin over a policy disagreement and call it BIP-110, then every future disagreement becomes a fork threat. That is not decentralization; it is fragmentation theater. It produces headlines, not consensus. BIP-110's chain is 18 blocks behind and falling. It will not survive. But the desire to shape Bitcoin's block-content policy is not going away. Let the chain fail. Let the lesson land. Then do the slow, tedious, consensus-generating work of drafting a proper BIP, reviewing it in public, and recruiting miners through incentives, not ultimatums. The 5% chain is already a corpse. The question is whether the next policy fight will happen in a BIP draft or on a dying block height.