BIP-110 Failed. The Minority Fork Proves Bitcoin Governance Works.

The mainstream coverage of BIP-110 was pitched as a showdown. Articles told readers to track the battle live, as if a dramatic confrontation over Bitcoin's soul was about to play out. The headline treatment implied a coin flip: the proposal either succeeds and transforms the protocol, or it fails and the community splits. That framing treats Bitcoin governance as a contest of wills. It is not. It is a mechanism with structural constraints that make certain outcomes inevitable before the final block is mined.

BIP-110 - formally the Reduced Data Temporary Softfork - proposed seven consensus-level restrictions limiting arbitrary data in Bitcoin transactions for roughly one year. The practical target was Ordinals inscriptions, BRC-20 tokens, and Runes. The proposal was authored under the pseudonym Dathon Ohm, with veteran developer Luke Dashjr credited for the original draft, and assigned its BIP number in December 2025. Bitcoin Improvement Proposals receive sequential numbers; publication does not signal endorsement. BIP editor Mark "Murch" Erhardt assigned BIP-110 its number while describing it as "a misguided and unusually careless softfork proposal". He published it anyway because it met the repository's formal criteria.

The proposal activates through a user-activated soft fork (UASF), the same mechanism that eventually forced SegWit's activation in 2017. Under a UASF, nodes running the new rules enforce them on a predetermined date regardless of whether miners agree. If enough economic participants adopt the enforcing software, miners have no choice but to comply or find themselves mining on a chain nobody prices. BIP-110 also included a miner-driven fast-track: if 55% of blocks within any 2,016-block difficulty adjustment period signaled support via bit 4, the proposal would lock in early. The mandatory signaling window opened at block 961,632 around August 7 and closes at block 963,647. Activation would follow at block 965,664, approximately September 6.

None of it matters. The proposal is dead, and it has been dead for weeks.

The Participant Ecology

To understand why BIP-110 failed, you need to map who has what and what they gain. The debate around BIP-110 is often framed as a philosophical disagreement about what Bitcoin is for. It is not. It is a conflict between participants whose economics are served by the status quo and participants whose grievance is real but whose leverage is structural zero.

Miners receive fees from every transaction that confirms, regardless of whether it transfers BTC or embeds a JPEG. Ordinals and Runes inscriptions have generated competitive fee revenue since 2023, and miners have no incentive to give that up. The four major pools - Foundry Digital, AntPool, ViaBTC, and F2Pool - collectively control more than 70% of Bitcoin's hashrate. None of them signaled support. F2Pool refused outright. AntPool remained silent. Foundry USA ran a hashrate-weighted miner vote with non-responses counted as No. The math was settled months ago: with less than 1% of blocks signaling in any difficulty period, the 55% threshold was unreachable. SegWit's 2017 UASF entered its enforcement phase with roughly a third of the network's hashrate already signaling. BIP-110 entered August at 0.6%.

Node operators - particularly those running Bitcoin Knots, an alternative client to the dominant Bitcoin Core - represent a genuine constituency. Knots nodes account for roughly 22% of reachable nodes, according to Coin Dance data from late June 2026. Their grievance is legitimate: non-monetary data inflates the blockchain, increases node storage and bandwidth costs, and drives up fees during inscription surges. But nodes verify transactions; they do not produce blocks. Running a BIP-110-enforcing node does not change consensus. It places you on a minority chain.

The economic majority - exchanges, wallets, institutional custodians, merchants - never aligned behind BIP-110. This is the decisive difference from 2017. The SegWit UASF worked because the economic ecosystem credibly threatened to ignore blocks from non-compliant miners, making it economically self-defeating for miners to resist. BIP-110 had none of this. No major exchange committed. No wallet provider adopted the enforcing software. Bitcoin Core... never merged the BIP-110 implementation.

What happens when a UASF fires without economic backing is not a protocol change. It is a chain split. Farside UK... declared the proposal mathematically finished on August 1. "BIP-110 has now failed to reach a 55% threshold and can never reach such a threshold," the account posted. Nodes running BIP-110-enforcing software began rejecting non-signaling blocks on the mandatory window date. Because the overwhelming majority of blocks do not signal, those nodes are now on a minority chain that will persist as long as someone mines on it, but carries no economic weight.

The Governance Mechanism

BIP-110 reveals something structural about Bitcoin's governance that runs deeper than this specific proposal. The proposal's activation mechanism was designed to lower the bar - 55% rather than the traditional 95% miner threshold - and to add a user-activated escape hatch in case miners refuse. Both shortcuts were necessary precisely because the proposal lacked broad support. And both shortcuts failed in the ways the governance structure predicts.

The lowered threshold was a concession to the fact that no one expected widespread miner enthusiasm. The UASF mechanism was a concession to the fact that no one expected the economic majority to rally behind it. A proposal that needs every structural workaround to force activation does not have a path to activation. It has a path to a minority fork.

This is not a criticism of BIP-110's proponents. The question they are asking - what happens when block space is allocated to data storage that only the paying user values while the entire network bears the storage cost indefinitely - is a legitimate one about misaligned incentives. The problem is not the question. The problem is the mechanism. You cannot change consensus rules without the hash power to produce blocks on the new chain and the economic weight to make those blocks valuable. When those two forces do not align, you get an orphan chain, not a protocol upgrade.

The 2017 SegWit episode is the historical reference point, and it is often misread. The lesson was not that nodes can force miners to comply. The lesson was that the economic ecosystem - exchanges, wallets, businesses - can credibly threaten to abandon the chain that miners produce, making capitulation the rational choice. BIP-110 had no such economic coalition. Invoking SegWit as a blueprint without the underlying economic alignment is not governance strategy. It is governance fiction.

What the Split Means

The minority chain that is now forming is not an existential threat to Bitcoin. It is a structural echo - a signal that a segment of the community is willing to run software enforcing rules that the rest of the network rejects. That signal is informative but not dangerous. The minority chain will persist as long as sufficient hashrate mines on it, and the Ocean Mining pool (which controls roughly 5 EH/s out of a network approaching 940 EH/s) has signaled by default. That is enough to keep the chain alive but not enough to make it competitive.

The real question is whether the minority chain creates operational confusion. Custodians, exchanges, and wallets need to ensure they are routing transactions to the main chain, not the BIP-110-enforcing chain. Bitcoin at $65,000 with a $1.3 trillion market cap is no longer the protocol where running an unusual node client is a harmless hobby. Chain splits that produce dual-valid chains... create replay risk, custody confusion, and settlement ambiguity. The fact that this is happening with less than 1% miner support means the operational risk is low. The minority chain has no economic weight to confuse pricing or settlement. But it is a reminder that every contested protocol event, even a failed one, carries residual friction.

Verdict: BIP-110 failed not because miners are obstinate or because inscription users are incorrigible. It failed because the proposal attempted to change Bitcoin's consensus rules without the hash power to produce blocks on the new chain and without the economic weight to make those blocks valuable. A UASF without economic backing produces a minority fork, not a protocol upgrade. That is not a bug in Bitcoin's governance. It is the feature that prevents a determined minority from rewriting the rules. The minority chain will persist as a structural echo, and the debate over what Bitcoin block space should be for will continue. But the mechanism for change requires alignment across miners, economic participants, and the reference software - and when those forces do not converge, Bitcoin stays exactly where it is.

The broader lesson is about any protocol that requires near-unanimity for change. Governance structures optimized for stability are structurally incapable of responding to minority grievances, even legitimate ones. That is the tradeoff. Bitcoin was built to be hard to change. BIP-110 proves it still is.

What data would change this view? A scenario where the economic majority - exchanges, custodians, wallets - credibly aligns behind a contested proposal. That alignment would create economic leverage over miners that the UASF mechanism can then exploit. Without it, every future UASF with thin economic support will produce the same result: a minority chain, not a protocol change. The participant ecology determines the outcome. The activation mechanism is secondary.