Bitcoin Core V30 Bug Risks Fund Loss During Legacy Wallet Upgrades

Why It Matters

The bug exposes a critical data‑loss risk for a sizable portion of Bitcoin’s node infrastructure, underscoring the need for robust backup practices and diversification of client implementations.

Key Takeaways

• Bug deletes wallet directory during migration with pruning enabled
• Affects legacy wallets using custom -walletdir in v30.0/30.1
• No fix until Bitcoin Core 30.2 release
• Users should backup data and avoid migration now
• Concentration risk: Core runs 78% of Bitcoin nodes

Pulse Analysis

The wallet‑migration bug in Bitcoin Core 30.0 and 30.1 stems from a cleanup routine that mistakenly removes the entire wallet directory when pruning is active and a custom -walletdir points to an unnamed legacy wallet.dat. This edge‑case scenario is rare, affecting only users who have never renamed or upgraded their original wallet files. Mitigation steps are straightforward: verify the client version, confirm pruning status, and back up the full data directory before any migration attempt. By pausing upgrades until version 30.2, users can avoid irreversible fund loss.

Beyond the immediate technical flaw, the incident spotlights the concentration risk inherent in Bitcoin’s ecosystem. With Bitcoin Core operating roughly 78% of reachable nodes, a single client‑side vulnerability can ripple through a vast majority of the network, even though it does not affect consensus rules. Analysts warn that such dominance limits resilience, as alternative implementations like Bitcoin Knots hold a modest share. The episode reinforces calls for greater client diversity to mitigate systemic exposure.

For the broader crypto community, the bug serves as a reminder of best‑practice security hygiene. Regular external backups, cautious use of pruning, and vigilant monitoring of debug logs are essential safeguards for any node operator. As the development team prepares the 30.2 patch, the episode also illustrates the importance of rapid response mechanisms—pulling binaries and issuing clear guidance can contain potential damage. Looking ahead, increased scrutiny of wallet‑layer code and encouragement of multi‑client environments will be key to preserving trust in Bitcoin’s infrastructure.