A Bitcoin fork dubbed BIP-110 launched this week and mined exactly two blocks before grinding to a halt. The breakaway chain inherited Bitcoin's full mining difficulty without securing comparable hashpower, a fatal miscalculation that left blocks spaced hours apart.
The fork's core problem stems from how Bitcoin's difficulty adjustment works. Mining difficulty recalibrates every 2,016 blocks to maintain a ten-minute block time. BIP-110 copied Bitcoin's current difficulty but launched with a fraction of the network's total hashpower. The result was predictable. Block times stretched to multiple hours, making the chain functionally unusable for transactions.
Both chains initially accepted the same transactions, creating temporary confusion about which version held canonical status. This overlap lasted only briefly before the fork's network effects became clear. BIP-110 failed to attract meaningful miner participation, and the fork collapsed under its own technical weight.
The fork appears connected to ongoing Bitcoin protocol debates around scalability and transaction throughput. BIP-110 likely proposed changes its backers believed essential, but failed to build consensus among the broader mining community. Without majority hashpower support, launching a fork carries inherent risks that this episode highlighted.
Bitcoin's difficulty adjustment mechanism, while elegant for the main chain, punishes forks launched without sufficient hashpower. The two-block run suggests either rushed execution or unrealistic expectations about miner adoption. Some forks, like Bitcoin Cash and Bitcoin SV, secured enough hashpower to survive initial launch phases and establish independent networks. BIP-110 did not.
The episode underscores a harsh reality in fork dynamics. Protocol changes require either overwhelming hashpower at launch or gradual migration to build legitimacy. BIP-110 had neither. The fork's rapid collapse likely provides ammunition for both sides of ongoing Bitcoin scalability debates, with supporters of the status quo pointing to the fork's failure as