So I just saw that Bitcoin Core 30 and 30.1 got taken down. Apparently, they could wipe some really old Satoshi wallets during migration. How does that even happen? You’d think they would catch that in testing.
Bitcoin Core 30 Issues and Wallet Concerns
22 replies 108 views
Yeah I saw that too. Someone posted about it last night here.
I’m curious about the testing process. How did they miss this bug? Seems like a major oversight.
I think it’s kinda niche. Like if you had an unnamed wallet, custom directory, pruning on, and then it tried to auto-migrate. That’s a lot of specific conditions.
matrix2021Full Member
Posts: 92 · Reputation: 612
#5Feb 8, 2025, 07:03 AM
But unnamed wallets aren’t that rare. Bitcoin Core had those for years! And you can still create them now. Custom directory isn’t even needed, that’s a distraction.
Totally agree. They should make it clear that not all old wallets are affected. Otherwise, people are gonna freak out.
matrix2021Full Member
Posts: 92 · Reputation: 612
#7Feb 8, 2025, 09:30 AM
Yeah, and it’s not the first time backward compatibility issues slipped through. They should really consider better tests for these older wallet formats.
AtomicForkFull Member
Posts: 352 · Reputation: 479
#8Feb 8, 2025, 02:24 PM
Spot on. It’s not just legacy wallets at risk. It deletes the entire wallets directory, which is a serious issue.
Automatic migration seems like a bad move overall. Wallet formats should be kept around for legacy support, like how SQLite does it.
True, but it’s tough to guarantee old versions will always work. They need a solid plan for converting older wallets.
Exactly! They can’t test every single possibility, but it’s key to mitigate these types of bugs.
This bug is a big deal. Losing access to funds is a nightmare, and it’s way worse than standard software issues.
Yeah, that’s why banking software stays old and stable. Any change is risky and needs tons of testing.
There have been other serious bugs though. Like the value overflow incident was pretty bad, right?
True, but those affected more than just wallets. Some were exploitable across the network, which is a different level of risk.
Heard there’s a similar bug in Knots too. They don’t seem to review their changes as thoroughly as Core.
I’m still on 28.0 with my coins. I’ve got a backup, but I’m holding off on updates for now.
I’m on 25, and I’m worried I might run into this bug too. Got backups, but still.
Proof that Knots is more insecure than Core. If they’re just copying code, who knows what slips through?
Nah, you’re safe if you’re on older versions. This issue only popped up in the latest Core releases.