Bitcoin's BIP-110 fork failed: two blocks, then silence
Signal21 Editorial Desk
The Bitcoin fork that a corner of the internet spent weeks warning about is over, and it ended faster than almost anyone predicted. The chain that split away from Bitcoin at block 961,632 to enforce BIP-110's data limits mined two blocks over the weekend — and then went silent. By Sunday morning the main chain had added more than 200 blocks since the split point; the breakaway chain had added none for hours and counting. Bitcoin's price, near $65,000, barely registered that anything had happened.
For readers arriving here from the weekend's headlines: BIP-110, the "Reduced Data Temporary Softfork" written by the pseudonymous developer Dathon Ohm, would cap the arbitrary data a transaction can carry — the inscriptions and similar uses its supporters call spam — for about a year. It asked miners to signal support in 55 percent of a difficulty window's blocks. Signaling never rose meaningfully above 2.5 percent, and when the mandatory phase began at block 961,632, nodes enforcing the rules started rejecting every non-signaling block. That did not bend the network; it stranded the enforcers on their own chain. We covered the setup in detail when the window opened.
The arithmetic of the failure is stark. A chain that splits from Bitcoin inherits Bitcoin's full mining difficulty, so with a fraction of one percent of hashpower — post-mortems estimate more than 99.8 percent stayed with the main chain — each block takes not minutes but days or weeks to find. Two blocks is what that hashpower could produce before the economics caught up with it. There were no exchange listings waiting, no futures, no wallet support, no ticker. Unlike Bitcoin Cash in 2017, which launched with meaningful miner backing and day-one exchange infrastructure, this fork arrived with nothing downstream of its own conviction.
For holders, the practical answer is the reassuring one: nothing happened to Bitcoin or to anyone's coins. No new asset credibly exists, and the replay risk that technically accompanies any chain split is largely moot on a chain that is not producing blocks — though the standard caution of doing nothing exotic with on-chain transactions for a few days costs nothing. The main chain never missed a beat through the entire window.
Bitcoin has been here before. BIP 101 and Bitcoin XT tried to force bigger blocks in 2015 and collapsed when miners and users declined to follow; Segwit2x was called off in 2017 for the same reason. The pattern the weekend confirmed is the one that matters: a consensus change without overwhelming support does not weaken Bitcoin — it strands its own proponents, visibly and quickly. That is not a bug in Bitcoin's governance; it is the mechanism working exactly as designed. The underlying argument BIP-110 raised — how much non-financial data Bitcoin should carry — is genuine and will continue inside Bitcoin Core's ordinary review process, where a change with real consensus would look nothing like this.
The market read it correctly in advance. Bitcoin spent the fork weekend little changed near $65,000, holding the stabilization built above the roughly $62,000 support zone from earlier this month. Our three horizon views are unchanged by the episode — a failed minority fork with no economic weight is noise, not signal, for the forecast. What would matter is listed alongside, and none of it is fork-shaped: the levels, the flows, and whether the data-limits debate ever returns with actual consensus behind it.
This is general market commentary, not investment advice or a recommendation to buy or sell any asset.
Sources
- CoinDesk — Controversial Bitcoin fork BIP-110 mines two blocks, then stops, 2026-08-09
- The Cryptonomist — Bitcoin BIP-110 signaling starts with just 2.53% miner support, 2026-08-09
- Criptolog — BIP-110 soft fork fails to activate; network stable, replay risks explained, 2026-08
- mempool.space — main-chain heights after block 961,632, accessed 2026-08-10
- CoinGecko — BTC/USD spot price, accessed 2026-08-10