Bitcoin BIP-110 Fork Collapses After Mining Just Two Blocks as Roughnecks Halts Operations

Aug 8, 2026

The controversial Bitcoin BIP-110 fork has collapsed after mining just two blocks. The split occurred at block 961,632 on August 8, 2026, when enforcing nodes rejected a non-signaling block. However, miner support capped at 2.53%, far below the 55% threshold. The primary mining group, Roughnecks, halted operations on August 9, causing Ocean's hashrate to collapse by 96.5%. Lacking hashrate and replay protection, the minority chain stalled under Bitcoin's high mining difficulty.

BIP-110 fork collapse

▪The BIP-110 fork collapsed and fell dozens of blocks behind the main Bitcoin chain, which continued to produce blocks normally.
▪The BIP-110 minority chain effectively stalled after producing only two blocks following its split from the main Bitcoin network.

Roughnecks mining halt

▪The mining group Roughnecks announced on August 9, 2026, that it stopped mining operations on the BIP-110 chain.
▪Ocean's displayed hashrate collapsed by roughly 96.5%, falling from about 36 EH/s on August 8 to 1.25 EH/s on August 9, 2026.
▪Roughnecks advised other miners on the BIP-110 chain to halt their operations until further notice.

Low miner support

▪Miner support for the BIP-110 proposal capped at approximately 2.5% to 2.6% during the signaling period, far below the 55% threshold required for activation.
▪No major Bitcoin mining pools publicly expressed support for the BIP-110 proposal prior to the chain split.

Chain split mechanics

▪The BIP-110 chain split occurred at block height 961,632 when enforcing nodes rejected a non-signaling block mined by AntPool.
▪The BIP-110 minority chain inherited Bitcoin's mining difficulty of roughly 127 trillion, making block production extremely slow without substantial hashrate.

Replay risk exposure

▪The BIP-110 minority chain lacks automatic replay protection, exposing users to risks of losing real Bitcoin if they attempt to transact on the fork.
▪Developers cautioned Bitcoin holders against treating the BIP-110 split as a risk-free airdrop due to transaction replay vulnerabilities.