Bitcoin Core Developers Uncover Critical Wallet Migration Bug in Versions 30.0 and 30.1 – What You Need to Know
- What’s the Bitcoin Core Wallet Migration Bug?
- How to Check If You’re at Risk
- Developer Response and Community Backlash
- FAQs: Bitcoin Core Wallet Bug
Bitcoin Core developers have publicly disclosed a critical bug affecting wallet migrations in versions 30.0 and 30.1, warning users of potential fund loss if unsaved legacy wallets are migrated under rare conditions. The team has removed binaries for the affected versions and urges users to avoid migrations until the patched v30.2 releases. Here’s a deep dive into the issue, community reactions, and actionable steps for users. ---
What’s the Bitcoin Core Wallet Migration Bug?
The bug, discovered in bitcoin Core v30.0 and v30.1, disrupts the migration process from legacy Berkeley DB (BDB) wallets to modern descriptor wallets. In rare cases, attempting this migration could delete all wallet files on a node if pruning is enabled and the wallet is unloaded mid-process. Developers emphasize the risk is limited to users with unnamed defaultfiles—a format deprecated since Bitcoin Core 0.21 (2020).
According to the team’s statement, the flaw doesn’t impact regular wallet usage or nodes running without wallets. “You can continue using Bitcoin Core normally, including existing wallets,” they clarified. A fix is slated for v30.2, but binaries for the faulty versions have been pulled as a precaution.
---How to Check If You’re at Risk
Lacie Zhang, a market analyst at BTCC, suggests technically adept users verify their exposure by:
- Checking their Bitcoin Core version (30.0/30.1 = vulnerable).
- Reviewing
debug.logfor pruning activity or prior migration attempts. - Confirming whether
-walletdirpoints to a custom or mounted location.
“The highest risk occurs when these conditions align and a migration is attempted,” Zhang noted. “If untouched, users should immediately back up their entire data directory and avoid system restarts until upgrading to v30.2.”
---Developer Response and Community Backlash
The Bitcoin Core team’s swift acknowledgment and corrective measures were praised as professional, but the crypto community on X (formerly Twitter) erupted in criticism. Some users lambasted the platform’s reliability, while others seized the moment to advocate for alternative wallets. The incident follows earlier tensions among developers over Bitcoin Core v30’s controversial data-storage features, which critics argue clutter the blockchain.
Notably, the bug’s discovery delayed v30’s final release by weeks—only for a significant flaw to slip through. “If you’re reading this, you’re already ahead,” quipped one developer, urging users to stay updated via official channels.
---FAQs: Bitcoin Core Wallet Bug
Is my Bitcoin safe if I’m not migrating wallets?
Yes. The bug only triggers during migration attempts. Existing wallets and nodes without wallets operate normally.
When will the fix (v30.2) be released?
Developers haven’t specified a date but prioritize a stable patch. Followfor updates.
Can I downgrade to a pre-v30 version?
Downgrading isn’t recommended due to compatibility risks. Instead, back up your wallet and wait for v30.2.
