From: "'Ava Chow' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] Wallet Migration Failure May Delete Unrelated Wallet Files In Bitcoin Core 30.0 and 30.1
Date: Mon, 05 Jan 2026 20:38:23 +0000 [thread overview]
Message-ID: <f498b9ad-c3e1-40bb-8325-4df6bbf74cd7@achow101.com> (raw)
Hi all,
We have become aware of a wallet migration bug introduced in Bitcoin
Core 30.0 and 30.1. Under rare circumstances, when the migration of a
wallet.dat file fails, all files in the wallet directory may be deleted
in the process, potentially resulting in a loss of funds. A fix is
forthcoming and will be released as 30.2, but out of an abundance of
caution we have removed the binaries for affected releases from
bitcoincore.org.
At this time, we ask users to not attempt wallet migrations using the
GUI or RPC until v30.2 is released. All other users, including existing
wallet users, are unaffected and can keep using existing installations.
Specifically, it requires the presence of a default (unnamed) wallet.dat
file, which has not been created by default since 0.21 (released 5 years
ago), that fails to be migrated or loaded. One condition that may
trigger this is when pruning is enabled, and the wallet was unloaded
while pruning happened.
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/f498b9ad-c3e1-40bb-8325-4df6bbf74cd7%40achow101.com.
reply other threads:[~2026-01-06 1:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f498b9ad-c3e1-40bb-8325-4df6bbf74cd7@achow101.com \
--to=bitcoindev@googlegroups.com \
--cc=lists@achow101.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox