Bitcoin Core developers on Monday warned users of a wallet-migration bug in versions 30.01 and 30.1 which can result in the loss of funds and delete files.
You can also find out more about the following: issue Migrations to new Bitcoin Core wallets, which were not renamed and upgraded after the old ones have been implemented are affected by this issue.
Lacie Zhang is a market analyst for Bitget Wallet. She told Cointelegraph the bug occurs when the software tries to migrate a legacy file that has not been named. “wallet.dat” The file is stored within a wallet custom directory. “-walletdir” Setting while pruning is active.
The migration might appear to be successful but, if the user has no external backup, cleanup logic may delete all the files in the wallet directory. “loss of access to funds is effectively guaranteed because all local wallet files are removed.”
Shawn Odonaghue is the community leader at layer-3 Blockchain Orbs. He told Cointelegraph about the bugs. “very old wallet setups,” Users with a hardware wallet or modern wallet software It is unlikely that you will experience any such issues.
Related: Bitcoin Core wins rare praise as independent audit finds no serious flaws
Bitcoin Core removes binaries, prepares fix
Bitcoin Core 30.1 The wallet migration bug has been publicly disclosed since the release of version 1.1.0. disclosed Developers removed the binaries 30.0 and 30.1, from the download page, on Monday.
The project told users not to use the wallet‑migration tools until a fixed release, Bitcoin Core 30.2, is available, stressing that existing users who are not attempting migrations can continue running their nodes as normal.
Zhang said that users who are technically adept can determine their risk by checking if they’re running Bitcoin Core version 30.0 or 30.1, ascertaining whether their wallets are legacy wallets, and inspecting “debug.log” By checking the directory structure to verify whether or not pruning has been enabled, any migrations have occurred and whether “-walletdir” Points to an installed or custom location.
“Risk is highest if all these conditions are present and a migration has either been attempted or is pending,” “She said” “If no migration has occurred yet, users should immediately back up the entire data directory to external media and avoid restarting or upgrading until moving to version 30.2 or later.”
Related: Bitcoin devs flocked back to work amid a big year for crypto
Bitcoin Core dominates nodes
Bitcoin Data tracker Coin Dance is Bitcoin Core, which currently makes up 78% (or more) of all Bitcoin nodes. Bitcoin Knots and other implementations like it make almost 22%.
This dominance also means that even a wallet bug with a limited scope can have ramifications for the wider eco-system.
“The bigger takeaway is concentration risk,” Odonaghue said. “Bitcoin Core has a massive share of the ecosystem, there aren’t many truly mainstream alternatives… when one implementation becomes the default, any bug or design decision has outsized impact.”
Zhang also added that although the bug was not “consensus-critical,” Its impact shows that wallet-layer problems can scale to ecosystem-wide issues when one implementation is dominant.
“This article is not financial advice.”
“Always do your own research before making any type of investment.”
“ItsDailyCrypto is not responsible for any activities you perform outside ItsDailyCrypto.”
Source: cointelegraph.com
