The Bitcoin Core crew 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 response to the outline, “beneath uncommon circumstances” an try to convert a legacy pockets (an outdated pockets saved in Berkeley DB format) may consequence within the deletion of all pockets recordsdata hosted on the identical node if it fails.
If you do not have a backup copy, There’s a direct threat of lack of funds. The event crew really helpful 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 neighborhood 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 present 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 operating your node, use your present pockets, and function usually. This repair shall 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 helpful obtain was as soon as once more Bitcoin Core 28.1. That is an earlier model that’s thought of secure and doesn’t embody the elimination of the OP_RETURN restriction.
Reactions and criticism from the neighborhood
Bitcoiner developer Tomer Strolight referred to as this concern harshly:
That is fairly severe if I am studying you accurately. In case you are making an attempt emigrate a legacy pockets, Bitcoin Core 30.x might delete all wallets in your machine. In fact, it is best to at all times keep backups, however that is so severe that Core has eliminated v30.x from the really helpful 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 individual behind that set up ought to concern a widespread warning earlier than somebody loses all their pockets recordsdata.”
This episode highlights two essential factors. First, the significance of backups. Wallets with out backups are at all times a threat.
Second, even audited and important software program could make errors with severe penalties. The crew’s response (public warnings, binary elimination, and deliberate patches) is aimed toward containing the impression.
Till Bitcoin Core 30.2 is revealed, the steering is evident: do not migrate your v30 legacy wallets, preserve backups, and select 28.1 if you’d like a secure set up.
