The Bitcoin Core group warned on January fifth of a essential error within the pockets migration course of that exists in variations 30.0 and 30.1 of the software program.
In line with the outline, “beneath uncommon circumstances” an try to convert a legacy pockets (an outdated pockets saved in Berkeley DB format) might outcome within the deletion of all pockets recordsdata hosted on the identical node if it fails.
If you happen to don't have a backup copy, There’s a direct danger of lack of funds. The event group really useful not performing the migration course of till a brand new fastened model of Bitcoin Core (on this case, similar to 30.2) is revealed.
The incident will happen one yr later intense dialogue within the bitcoiner group For Bitcoin Core v30, amongst different adjustments, it was an expanded model of the usage of the OP_RETURN opcode to embed arbitrary information in transactions, a call that sparked controversy in 2025.
Bitcoin Core v30 bug solely impacts migration of outdated wallets
Legacy pockets migration is a mechanism to transform older wallets to the newer format utilized by Bitcoin Core.
he bug It doesn’t have an effect on the overall performance of the node or the day-to-day use of current wallets. Solely impacts migration of legacy wallets utilizing v30.0 or v30.1..
Bitcoin Core has made it clear that every one different usages stay the identical. This implies you possibly can proceed working your node, use your current pockets, and function usually. This repair will likely be delivered in Bitcoin Core 30.2. Till then, we suggest not migrating legacy wallets to 30.0/30.1.
As an extra measure, the binary (set up executable) v30.0 and v30.1 have been labeled “unsecure”. On the official web site, the really useful obtain was as soon as once more Bitcoin Core 28.1. That is an earlier model that’s thought of steady and doesn’t embrace the removing of the OP_RETURN restriction.
Reactions and criticism from the group
Bitcoiner developer Tomer Strolight known as this concern harshly:
That is fairly severe if I'm studying you accurately. In case you are attempting emigrate a legacy pockets, Bitcoin Core 30.x might delete all wallets in your machine. In fact, it is best to all the time preserve backups, however that is so severe that Core has eliminated v30.x from the really useful variations of their web site.
Tomer Strolight, Bitcoin developer.
Strolight added that given the main target to date on putting in v30 to enhance safety, there must be widespread and proactive communication about this. bug: “The particular person behind that set up ought to concern a widespread warning earlier than somebody loses all their pockets recordsdata.”
This episode highlights two necessary factors. First, the significance of backups. Wallets with out backups are all the time a danger.
Second, even audited and demanding software program could make errors with severe penalties. The group's response (public warnings, binary removing, and deliberate patches) is geared toward containing the influence.
Till Bitcoin Core 30.2 is revealed, the steering is obvious: don't migrate your v30 legacy wallets, preserve backups, and select 28.1 if you need a steady set up.
