Bitcoin Unlimited Nodes Drop to 20% of Network

On March 15, 2017, one day after the devastating bug exploit, Bitcoin Unlimited's node count remained severely depressed at approximately 20% of its previous levels, hovering around 300 nodes compared to the nearly 800 that had been running before the attack. While the development team had quickly released a patch to fix the vulnerability, many node operators remained offline either because they had not yet upgraded or because they had lost confidence in the software altogether.

The sustained reduction in Bitcoin Unlimited nodes signaled a significant loss of grassroots support for the project and strengthened the hand of Bitcoin Core developers and SegWit advocates.

The extended impact of the node crash created ripples throughout the Bitcoin scaling debate. Mining pools that had been signaling support for Bitcoin Unlimited began reconsidering their positions, with some quietly switching their signaling to support SegWit or neutral positions. The incident demonstrated the risks of running alternative Bitcoin implementations that lacked the extensive peer review and testing that went into Bitcoin Core releases.

Bitcoin Unlimited's developers attempted damage control, arguing that bugs can occur in any software and that Core had experienced its own critical bugs in the past. However, the dramatic and public nature of the crash, combined with the fact that it involved a relatively simple coding error, made it difficult to rebuild trust.The incident effectively ended Bitcoin Unlimited's serious challenge to Bitcoin Core's dominance, though the larger block debate would continue through other channels.