BTC BIP-110 fork stalls as miners quit

TLDR

Bitcoins BIP-110 soft fork has effectively stalled after a minority chain split, as key miners abandoned the effort and hashpower collapsed.

1. BIP-110 enforcement nodes created a tiny forked chain that mined only two blocks before the main supporting group, Roughnecks, told miners to stop.
2. The main Bitcoin (BTC) chain continues normally, but the failed fork highlights replay and operational risks for anyone interacting with fork coins.
3. BIP-110 backers are now discussing a proof-of-work change and other tactics, so the next signals to watch are hashpower shifts, exchange policies, and any node software updates.

Deep Dive

1. What Actually Stalled

BIP-110 is a proposed Reduced Data Temporary Softfork that would restrict non-financial data in Bitcoin transactions for about a year, targeting Ordinals-style inscriptions and large payloads. Miner signaling never exceeded roughly 2.5 percent, far below the 55 percent threshold its activation logic assumed, yet enforcing nodes still began rejecting non-signaling blocks at height 961632.

That created a minority chain. Ocean-linked miners under the Roughnecks label mined the only two blocks on this BIP-110 chain, then announced they were quitting and urged others to stand down, causing Oceans hashrate to collapse from around 36 exahash per second to about 1.25 exahash per second on the BIP-110 endpoint. With inherited difficulty near 127 trillion and almost no hashpower, the forked chain froze at two blocks while the dominant Bitcoin chain kept advancing, as described in the Roughnecks coverage on news.bitcoin.com.

2. Impact on Bitcoin Users and Risk

For everyday BTC holders and exchanges, the key point is that the main chain, supported by more than 97 percent of hashpower, has not been disrupted. Reports show major pools and venues continued operating on the dominant chain with no BIP-110 signaling and no service interruption.

However, the episode underscores how minority forks can create replay risk. Because the BIP-110 chain does not have built-in replay protection, a transaction broadcast on the fork can potentially be replayed on the main chain, affecting balances on both networks. Hardware wallet providers and analysts have warned users not to accept coins from the BIP-110 fork or treat it as a separate, safe asset without clear tooling, as noted in Ledger-related commentary.

3. Governance Lessons and What To Watch

With miner support near zero and the minority chain stalled, BIP-110 backers are discussing more radical moves, including changing the fork chains proof-of-work algorithm to fire the miners and escape SHA-256 ASIC dominance. Developer discussions around alternative algorithms like RandomX or Scrypt are ongoing, and experimental code for a PoW switch has been rebased but not activated, according to technical reporting.

Governance-wise, the episode is a live test of user-activated soft forks: BIP-110 shows that without substantial economic and miner coordination, enforcing nodes can end up on an economically irrelevant chain. The next meaningful signals are whether any major pool sends hashpower to a revived fork, whether large exchanges list or ignore any fork asset, and whether mainstream node software like Bitcoin Core changes its stance on blockspace spam in response.

Conclusion

The BIP-110 fork stalled because almost all miners refused to follow enforcing nodes onto a high-difficulty minority chain, leaving the experiment hashpower starved and operationally impractical. Bitcoins main chain continues unaffected, but the episode exposes real replay and coordination risks around contentious soft forks and highlights how difficult it is to change Bitcoins rules without wide economic backing. Watching hashpower, exchange treatment of any fork coins, and future consensus proposals will show whether this was a one-off misstep or a catalyst for a deeper rethink of Bitcoin governance and blockspace policy.