tldr; Bitcoin Core Version 30 (v30) and its update v30.1 have been pulled due to a critical bug that could delete wallet files, potentially causing users to lose funds. The issue affects users who migrated legacy Berkeley DataBase (BDB) wallets without backups or used the pruning feature. Developers are working on a patched version, v30.2, and advise users to back up their files. The bug highlights concerns over backward compatibility and has sparked debates among developers. The bug does not impact users with hardware wallets.
*This summary is auto generated by a bot and not meant to replace reading the original article. As always, DYOR.
frozengrandmatetris on
severe lack of client diversity. core is by far the most popular client, followed by a fork of core. everything that isn’t those two make up a tiny sliver. there is also libbitcoin, but most of the community ignores it and it is underfunded.
many people in the bitcoin community openly deny that client diversity is even necessary.
2 Comments
tldr; Bitcoin Core Version 30 (v30) and its update v30.1 have been pulled due to a critical bug that could delete wallet files, potentially causing users to lose funds. The issue affects users who migrated legacy Berkeley DataBase (BDB) wallets without backups or used the pruning feature. Developers are working on a patched version, v30.2, and advise users to back up their files. The bug highlights concerns over backward compatibility and has sparked debates among developers. The bug does not impact users with hardware wallets.
*This summary is auto generated by a bot and not meant to replace reading the original article. As always, DYOR.
severe lack of client diversity. core is by far the most popular client, followed by a fork of core. everything that isn’t those two make up a tiny sliver. there is also libbitcoin, but most of the community ignores it and it is underfunded.
many people in the bitcoin community openly deny that client diversity is even necessary.