In the quiet of the bear, we count the coins. But here, we count the blocks. Only two. In eight hours, the BIP-110 fork, an attempt to force a protocol-level ban on non-financial data on Bitcoin, produced exactly two blocks before collapsing. The main chain, at block height 961,681, did not blink. This is not a story about code. It is a story about power, incentives, and the brutal efficiency of Bitcoin's governance machine.
Context: The Anatomy of a Forced Fork
BIP-110, or Bitcoin Improvement Proposal 110, was a proposed soft fork. Its core function was to restrict the use of OP_RETURN and other mechanisms for embedding non-financial data—specifically, the Ordinals inscriptions and BRC-20 tokens that had congested the mempool and driven up fees. The mechanism was a variant of a User-Activated Soft Fork (UASF). Unlike the standard BIP-9 activation process, which requires 95% miner signaling within a difficulty adjustment period, BIP-110 nodes were programmed to reject blocks that did not contain a specific signal bit starting at block height 961,632. This is a digital machete, not a surgical scalpel.
This is where the story diverges from a technical upgrade into a governance war. The proposal had only 51 out of 2,016 blocks in the previous signaling period—a mere 2.53% support. The required threshold for activation was 55%. The gap was not a chasm; it was a canyon. Yet, the nodes enforced the rule. The result was a partition of the network. The BIP-110 chain, protected by a microscopic fraction of the total hashrate, began to produce blocks. It produced two. Then it stopped.
Core: The Mechanics of Failure
Let us dissect the numbers. Bitcoin's average block time is ten minutes. In eight hours, the theoretical maximum production is 48 blocks. The BIP-110 chain produced two. This implies a hashrate share of approximately 4%. For perspective, the main Bitcoin network operates at roughly 500 exahashes per second. The BIP-110 chain was running on what amounts to a few high-end gaming rigs. This is not a blockchain; it is a ghost town with a single miner.
Why did the miners refuse to support it? The answer lies in the tokenomics. BIP-110 was not a neutral technical adjustment. It was a redefinition of Bitcoin's block space as a resource. The proposal's core economic thesis was that block space should be exclusively for financial transactions—a digital gold bar, not a digital bulletin board. This directly attacks the revenue stream generated by Ordinals-related transactions. Since the advent of inscriptions, fee income for miners has increased significantly. In the second quarter of 2024, Ordinals-related fees constituted a material portion of total transaction fees. BIP-110 would have eliminated this. The miners, rational actors maximizing their return on capital, voted with their hashrate. They voted no.
We do not predict the storm; we build the hull. The storm here was the forced activation. The hull was the miner's economic calculation. The failure was not a bug; it was a feature of the system. Bitcoin's governance is not a democracy. It is a weighted consensus where the final arbiter is economic energy. The BIP-110 proponents attempted to bypass the miners. The miners responded by ignoring the fork.
Contrarian: The Failure is a Success for the System
The conventional narrative is that a failed fork is a sign of weakness, of factionalism, of a broken governance process. This is a misunderstanding. The BIP-110 failure is the strongest evidence of Bitcoin's resilience. The system is not designed to be efficient at change. It is designed to be robust against bad change. The UASF mechanism is a powerful tool, but it is a double-edged sword. It can force a consensus shift, but only if the user base and the economic majority are aligned. Here, they were not.
Ironically, the failure is a massive win for the Ordinals and BRC-20 ecosystem. The tail risk of a protocol-level ban has been eliminated. The path to censorship through the core protocol is now provably blocked for the foreseeable future. The contrarian take is that this event actually strengthens the economic coalition between miners and the application layer. Miners have an interest in preserving diverse fee sources. The Ordinals ecosystem provides that. The BIP-110 failure solidifies this symbiotic relationship.
Takeaway: Positioning for the Next Cycle
The BIP-110 fork is dead. The lesson is not about the specific proposal. It is about the structural inertia of Bitcoin. The next attempt to restrict block space will not come through a UASF. It will come through a different vector: perhaps a change in mining software that filters certain transaction types, or a voluntary mempool policy by major nodes. The macro context is clear: the Federal Reserve's liquidity cycle, not protocol politics, remains the dominant driver of Bitcoin's price. The alpha hides in the variance others ignore.
Do not chase the ghost of the fork. Do not trade the BIP-110 chain's token—it is worth zero. Instead, watch the mempool. Watch the fees. The next battle will be fought not in the code, but in the economics of transaction inclusion. The storm has passed. The hull is intact. We build.