TechFlow Logo
Login/ Sign up
ETH Gas
Gwei
Fear
gas
Only Two Blocks Mined in Eight Hours: Why Did BIP-110 Fail to Purify Bitcoin?

Only Two Blocks Mined in Eight Hours: Why Did BIP-110 Fail to Purify Bitcoin?

2026.08.10
Share
In the world of Bitcoin, idealism without hashrate support cannot go far.

By: Xiao Bing

On the evening of August 7, Bitcoin split into two chains at block height 961632.

Nodes running BIP-110 software began rejecting all blocks that did not express support signals, parting ways with the mainnet. AntPool mined the first standard block at this height, which the mainnet accepted but BIP-110 nodes rejected. Subsequently, a miner working through the Ocean mining pool mined an alternative block, which the BIP-110 chain followed.

The picture eight hours later: the minority chain had only advanced to block 961633, producing a total of two blocks. During the same period, the Bitcoin main chain had reached block 961681, leading by 48 blocks.

This fork, lasting less than a day, has technically been declared a failure.

What Does BIP-110 Want to Do?

The full name of BIP-110 is "Reduced Data Temporary Softfork," published under the pen name Dathon Ohm. Bitcoin Core developer Luke Dashjr is considered the author of the original draft and the main proponent.

What it aims to do is not complicated: temporarily restrict non-financial data storage in Bitcoin blocks using consensus rules for about one year. The specific targets are Ordinals inscriptions, BRC-20 tokens, the Runes protocol, and other behaviors that write arbitrary data such as images and text onto the blockchain via transaction scripts and witness data.

The logic of supporters is that this data squeezes block space, drives up transaction fees, increases the cost of running full nodes, and deviates from Bitcoin's core mission as a "sound money infrastructure." Dashjr refers to this data as "spam," believing that long-term accumulation will threaten Bitcoin's decentralization.

The logic of opponents is equally clear: Bitcoin's block space belongs to everyone who pays to use it. Any legitimate transaction that pays sufficient fees should be accepted, and consensus rules should not determine what data is "qualified." Michael Saylor published a 110-point long article opposing the proposal in July, with the core argument being: "Bitcoin does not need guardians of purity, it needs guardians of neutrality." Adam Back also warned that pushing BIP-110 hard without broad consensus could split the network.

BIP editor Murch added a note when assigning the number, calling it "a poorly considered and unusually rash soft fork proposal." The number represents procedural compliance only, not endorsement.

Why Were Only Two Blocks Produced in Eight Hours?

The minority chain after the fork became paralyzed, which was entirely predictable mechanistically.

Bitcoin adjusts mining difficulty every 2016 blocks, aiming to maintain an average of one block every 10 minutes. The minority chain inherited the full difficulty setting of the main chain at the time of the fork, but had only a tiny amount of hashrate. In the past two weeks, only 2.53% of blocks expressed support for BIP-110, far below the 55% required for activation, with the vast majority of signaling blocks coming from the Ocean mining pool.

This means the minority chain must use less than 3% of the mainnet's hashrate to solve mathematical problems at 100% of the mainnet's difficulty. Based on the observed block production speed, it would take the minority chain approximately 350 days to complete the next difficulty adjustment, while the main chain needs only 14 days.

Before reaching the difficulty adjustment, the minority chain will remain in a nearly stagnant state. Meanwhile, BIP-110 rules require that within the two-week window before block 963647, every block must express a support signal. At the current speed, the minority chain cannot even reach the end of this window.

As of UTC August 9, 11:40, the main chain had advanced to block 961725, while the minority chain remained frozen at 961633. None of the 113 newly produced blocks on the main chain expressed support for BIP-110.

Real Risks Faced by Ordinary Users

The death of the minority chain does not mean the risks disappear. Both chains accept signed transactions in the same format, creating a window for replay attacks.

Suppose a user wants to sell forked coins on the minority chain (if there is a trading market for forked coins); they sign a transaction to send the forked coins to the buyer. The problem is that this signed transaction is also valid on the main chain. The buyer can broadcast the same signed transaction to the main chain and withdraw an equivalent amount of real BTC from the seller.

The super slow block production speed of the minority chain exacerbates this risk; confirmation times for forked coin transactions are extremely long, giving attackers ample time to operate on the main chain. Without a built-in replay protection mechanism in BIP-110, any transaction involving forked coins carries the possibility of accidentally losing main chain BTC.

For the vast majority of Bitcoin users, the safest approach is to ignore the existence of this minority chain, not move any forked coins, and not participate in any related transactions.

Governance Issues Did Not Disappear with the Fork

BIP-110 failed, but the governance cracks it exposed will not heal automatically.

The last major soft fork for Bitcoin was SegWit (BIP-141) in 2017, which underwent two years of governance tug-of-war, requiring 95% miner signaling to activate, and barely passed. The Taproot upgrade in 2021 gained broad consensus and activated smoothly. BIP-110 lowered the activation threshold to 55%, yet still only obtained 2.53%.

Before the fork, Dashjr sent a more radical signal: if BIP-110 failed, changing Bitcoin's Proof of Work (PoW) algorithm "might be the only option left," implying that if miners refuse to cooperate, node operators might bypass miners to modify rules directly. This is a fundamental challenge to Bitcoin's security model.

The essence of this debate is: who does Bitcoin's block space actually belong to.

Saylor's stance represents one viewpoint: block space is a neutral public resource, whoever pays uses it, and consensus rules should not distinguish the "purpose" of transactions. Dashjr's stance represents another: Bitcoin's core function is currency, all use deviating from this function is an abuse of limited resources, and protecting the network's long-term viability outweighs short-term "freedom."

Now, miners have voted with hashrate, choosing neutrality. This result is positive for supporters of Ordinals and BRC-20, and a setback for the group hoping to keep Bitcoin block space "pure."

But Dashjr will not stop here. As long as inscriptions and Runes continue to consume block space, this debate about "what Bitcoin should be used for" will recur in different forms.

BIP-110 proved one thing with two blocks: In the world of Bitcoin, idealism without hashrate support cannot go far.