Hook
2 blocks. 8 hours. That’s the production tally of the BIP-110 fork chain. In the same window, the main Bitcoin chain minted 49 blocks. The fork didn’t just fail—it collapsed under the weight of its own economic irrelevance. On March 15, 2025, a group of node operators triggered a user-activated soft fork (UASF) at block height 961,632, rejecting blocks that failed to signal support for BIP-110. The proposal aimed to limit non-financial data in Bitcoin transactions—a direct assault on the Ordinals ecosystem. The response from miners: a deafening silence. The fork chain stopped at height 961,633, while the main chain continued to 961,681. This wasn’t a battle. It was a foreclosure.
This is not a story about a near-miss protocol upgrade. It’s a case study in how Bitcoin’s governance truly works—where power resides not in proposals, but in hash rate. The BIP-110 fork is a microcosm of the tension between Bitcoin’s original vision as a pure monetary network and its current reality as a platform for arbitrary data. The numbers tell the story. The code executed. The miners voted with their ASICs. The result: a 2-block chain and a lesson for anyone who thinks rule changes can override economic incentives.
Context
BIP-110 was a Bitcoin Improvement Proposal designed to restrict the size and scope of data embedded in transactions. It targeted the script data capacity used by Ordinals inscriptions—the NFT-like assets that had exploded onto Bitcoin’s base layer. The proposal required a 55% signal rate within a 2,016-block difficulty period (approximately two weeks) to activate. If miners signaled, nodes would enforce the new rules. If not, the fork would trigger anyway—a UASF-style activation where nodes reject blocks without the signal.
In practice, the activation threshold was a gamble. The previous cycle saw only 51 blocks (2.53%) signal support. Yet the fork was triggered. The mechanism: nodes at block 961,632 refused to accept blocks that did not include the BIP-110 signal. This forced miners to either comply or mine on a separate chain. The result was a split: the main chain kept producing blocks under the old rules, while the fork chain limped forward with two blocks from unknown miners—likely amateur hobbyists or the proposal’s own advocates.
The fork’s failure was not a surprise to anyone who understands Bitcoin’s power structure. Miner support was the missing ingredient. The same dynamic played out during the 2017 SegWit UASF (BIP 148), where miners ultimately signaled to avoid a chain split. But that case had a critical difference: SegWit offered long-term benefits to miners (increased capacity, lower fees). BIP-110 offered only restrictions—a direct hit to fee revenue from Ordinals transactions. The economic calculus was clear. Code does not negotiate. It executes or it fails.
Core Analysis
The fork’s technical failure is a textbook case of UASF without miner backing. Let’s break down the numbers.
- Block height divergence: Fork chain at 961,633, main chain at 961,681 after 8 hours. A difference of 48 blocks.
- Average block time on fork: 4 hours per block vs. ~10 minutes on main chain.
- Previous cycle signal rate: 2.53% (51/2016 blocks).
These metrics reveal a chain that never had a chance. The two blocks mined were likely from a single miner or a small pool with negligible hash power. The fork chain’s security was effectively zero—any miner with a few hundred TH/s could have 51% attacked it. But no one bothered. The chain had no economic value, no exchange listing, no wallet support. It was a ghost.
Why did miners ignore the fork? The answer lies in the fee market. Ordinals inscriptions have become a significant source of transaction fees for Bitcoin miners. In 2024, Ordinals-related fees accounted for 15-20% of total miner revenue on some days, according to on-chain data from Glassnode. BIP-110 would have effectively banned large inscriptions, eliminating this revenue stream. The chart shows fear; the order book shows intent. The miners’ intent was to preserve their income. They didn’t need to signal opposition—they just didn’t switch chains.
From my own experience running arbitrage bots during the 2017 altcoin boom, I learned that miner incentives are the ultimate governor of Bitcoin’s protocol evolution. I once wrote a script that exploited latency between Binance and Huobi to capture triangular arbitrage. It worked for six weeks until the market corrected. But the lesson was deeper: code exploits inefficiencies, but it cannot override fundamental economic incentives. The same principle applies here. The BIP-110 code was sound—it executed the UASF logic correctly. But the economic environment was hostile. Patience is a tactical advantage, not a virtue. The miners waited, and the fork died.
Another technical angle: the fork’s activation mechanism was a hybrid of MASF and UASF. The 55% threshold was set to give miners time to adapt, but it was too low to force a decision. In practice, the threshold became irrelevant because the signal rate never approached it. The fork triggered anyway, but without the legitimacy of a supermajority. This is a governance failure—the proposal’s authors overestimated their support.
Contrarian Angle
Most market commentary will frame this as a victory for the Ordinals ecosystem. “BIP-110 failed, Ordinals are safe, buy the dip on ORDI.” That’s the surface narrative. But the contrarian take is more nuanced: the fork’s failure is a warning, not a celebration.
First, the failure does not mean the debate is over. It means the first attempt failed. The forces behind BIP-110—the “Bitcoin purists” who see Ordinals as spam—are not going away. They are node operators, developers, and ideologues. They have the ability to fork again, possibly with a more targeted proposal, such as limiting only very large inscriptions (>100 KB) or setting a per-block data cap. This would be a “compromise” proposal that miners might accept if Ordinals traffic continues to bloat the mempool.
Second, the fork’s failure reinforces the power of miners. But this is a double-edged sword for Ordinals. Miners are profit-maximizers. If Ordinals transactions cause persistent congestion or drive up the unconfirmed transaction mempool size, miners might eventually support limits to maintain user experience. The current fee boost is a short-term benefit. Long-term, if the network becomes unreliable, miners will adapt. They are not ideological allies of Ordinals—they are economic actors.
Third, the retail perception of this event is likely to be distorted. Many casual traders will see “Bitcoin fork fails, Ordinals survive” and book profits on ORDI. But smart money is watching the next BIP. The real risk is not the fork itself, but the regulatory and governance tailwinds that could favor data limits. The European Union’s MiCA framework, for example, could impose rules on digital assets that include “environmental sustainability” metrics, indirectly penalizing high-data transactions. Survival precedes profit in the unregulated wild. Ordinals traders should not mistake this fork’s failure for permanent safety.
Takeaway
For Bitcoin holders, the BIP-110 fork is a non-event. The main chain continues to produce blocks every 10 minutes. The price of BTC has not moved more than 0.5% on this news. There is no actionable trade here.
For Ordinals traders, this is a short-term bullish signal—the immediate threat of a rule change has passed. But the medium-term risk remains. Watch for two signals: (1) any new BIP that proposes a softer limit (e.g., 80% threshold, data cap per block), and (2) any change in miner sentiment, as reflected in pool voting or public statements. If you’re holding ORDI or other inscription tokens, consider setting stop-losses at recent support levels (e.g., $3.20 for ORDI). The price might spike on the “relief rally,” but don’t get caught in the euphoria.
The real lesson from this fork is about Bitcoin’s governance. The network is not a democracy—it’s a meritocracy of hashing power. Proposals that attack miner revenue will be rejected, regardless of ideological merit. The chart shows fear; the order book shows intent. The order book here is the hash rate allocation. And it says: Ordinals stay, for now.
But the fight is not over. The next BIP will be smarter. The next fork will be more prepared. Or the Ordinals community will proactively build second-layer solutions to reduce on-chain footprint. Either way, this event is a chapter in a longer story. The question is: which side learns faster?