qerranews 
A recently disclosed Bitcoin Core v30 wallet migration bug has raised alarms across the crypto community after developers confirmed that, under specific conditions, users could permanently lose access to their funds. While the issue does not affect Bitcoin’s consensus rules, its impact on wallet data highlights ongoing concentration risks in Bitcoin’s software ecosystem.
Bitcoin Core developers have pulled affected releases and urged caution, particularly for users running legacy wallet setups.
Bitcoin Core developers disclose wallet bug
Bitcoin Core maintainers warned users that versions 30.0 and 30.1 contain a wallet migration flaw capable of deleting local wallet files during upgrades. The bug was publicly disclosed on Monday, shortly after Bitcoin Core 30.1 was released on Jan. 1.
According to developers, the issue appears during the automatic migration process that moves older wallet formats to the newer descriptor-based structure. Under certain configurations, the migration may look successful but incorrectly trigger cleanup logic that removes the entire wallet directory.
If users lack external backups, this deletion can result in permanent fund loss.
Legacy wallet migrations face highest risk
The bug primarily affects older Bitcoin Core wallets that were never renamed or previously upgraded. Lacie Zhang, market analyst at Bitget Wallet, explained that the issue is triggered when an unnamed legacy wallet.dat file is stored in a custom wallet directory defined using the -walletdir parameter.
The risk increases further if pruning mode is enabled. In such cases, Bitcoin Core may mistakenly identify the wallet directory as temporary and delete it entirely during migration cleanup.
“The migration can appear to complete successfully,” Zhang said, “but the wallet files are silently removed, making loss of access to funds effectively guaranteed if no backup exists.”
Pruning and custom directories explained
Pruning is a Bitcoin Core feature that reduces disk usage by discarding old blockchain data. While commonly used by resource-constrained node operators, pruning adds complexity to wallet migrations.
When pruning is active alongside a custom wallet directory, Bitcoin Core’s migration logic may misinterpret directory ownership. This edge case is rare but dangerous, especially for users running very old wallet configurations that predate recent default changes.
Importantly, users with hardware wallets, modern descriptor wallets, or third-party wallet software are unlikely to be affected.
Bitcoin Core pulls releases, prepares fix
Following the disclosure, Bitcoin Core developers removed the 30.0 and 30.1 binaries from the official download site. Users were advised not to attempt any wallet migrations until a patched release, Bitcoin Core 30.2, becomes available.
The project clarified that users who are not migrating wallets can continue running their nodes without issue. The bug does not affect transaction validation, block propagation, or network consensus.
Developers emphasized that the issue is not consensus-critical, but still serious due to the potential for irreversible data loss.
How users can assess exposure
Zhang outlined several steps technically proficient users can take to determine whether they are at risk:
- Confirm whether they are running Bitcoin Core v30.0 or v30.1
- Check if their wallet is a legacy (non-descriptor) wallet
- Review debug.log to see if pruning is enabled
- Verify whether -walletdir points to a custom or mounted directory
- Identify whether a migration attempt has already occurred
“Risk is highest if all these conditions are present,” Zhang noted. Users who have not yet migrated should immediately back up their entire data directory to external storage and avoid restarts or upgrades until version 30.2 or later.
Bitcoin Core dominance magnifies wallet issues
According to Coin Dance data, Bitcoin Core powers roughly 78% of reachable Bitcoin nodes, while alternatives like Bitcoin Knots account for nearly 22%.
That dominance means even narrowly scoped bugs can have ecosystem-wide implications. Shawn Odonaghue, community lead at layer-3 blockchain Orbs, said the situation highlights software monoculture risks.
“When one implementation becomes the default, any bug or design decision has outsized impact,” he said. “There simply aren’t many truly mainstream alternatives today.”
Wallet layer risks still matter
While Bitcoin’s consensus rules remain robust, the wallet layer is where users directly interact with funds. Bugs at this level, even if rare, can scale rapidly when a single implementation dominates the market.
Zhang added that the incident serves as a reminder that decentralization extends beyond mining and nodes to client software diversity. Encouraging multiple well-maintained implementations could reduce systemic risk over time.
For now, developers stress that backups remain the strongest defense, particularly for users running legacy systems.