Why Move Away from Old Wallet.dat?

24 replies 186 views
alpha23Member
Posts: 31 · Reputation: 79
#1Jul 31, 2021, 11:14 PM
It’s clear why new wallet.dat is better: descriptors come with cool features like PSBT, easy watch-only wallets, plus no backups needed since you get new addresses automatically. But where's the proof that these new wallets are safer? All I hear is "you need to leak your xpub" but that doesn't make me feel secure.
4 Reply Quote Share
0xNodeMember
Posts: 257 · Reputation: 80
#2Aug 1, 2021, 03:21 AM
But like, can you explain how they’re less safe? I mean leaking your xpub isn’t the end of the world. That’s like putting all your addresses out there, which most people wouldn’t do by accident. You can’t stop users from screwing up their seed phrases, so what’s the difference?
1 Reply Quote Share
alpha23Member
Posts: 31 · Reputation: 79
#3Aug 1, 2021, 05:57 AM
The legacy format has its own set of problems that seem bigger than any downsides of the new format.
5 Reply Quote Share
0xNodeMember
Posts: 257 · Reputation: 80
#4Aug 3, 2021, 05:17 PM
True, but it’s still easier for an attacker with legacy wallets. They only need a smaller amount of data to get access compared to HD wallets.
6 Reply Quote Share
alpha23Member
Posts: 31 · Reputation: 79
#5Aug 3, 2021, 05:31 PM
You’re mixing things up. There’s a clear difference. If someone compromises a legacy wallet.dat, they get everything. With an HD wallet, it’s just one key. Even if your xpub leaks, if you’re using hardened derivation, you’re fine.
4 Reply Quote Share
0xNodeMember
Posts: 257 · Reputation: 80
#6Aug 3, 2021, 06:08 PM
Managing keys with legacy wallet.dat is way more straightforward if you don't trust HD wallets. Let’s face it, it’s a hassle to create a new wallet.dat for each address.
4 Reply Quote Share
alpha23Member
Posts: 31 · Reputation: 79
#7Aug 6, 2021, 06:08 AM
I didn’t say old wallets are perfect. But it’s an option; no one’s forcing you into anything. If you really hate it, build your own wallet.
6 Reply Quote Share
0xNodeMember
Posts: 257 · Reputation: 80
#8Aug 6, 2021, 07:11 AM
Why should I have to go that far? I’m just asking why Core pushes this change without clear explanations.
2 Reply Quote Share
matrix2021Full Member
Posts: 14 · Reputation: 612
#9Aug 6, 2021, 08:16 AM
Look up technological debt. It’s a valid reason to move on.
6 Reply Quote Share
sigma2016Newbie
Posts: 26 · Reputation: 22
#10Aug 6, 2021, 01:02 PM
So what’s next then? Are they gonna drop base58 support?
0 Reply Quote Share
alpha23Member
Posts: 31 · Reputation: 79
#11Aug 6, 2021, 02:58 PM
Maintaining old code is a nightmare for developers. No one wants to handle bugs from an outdated database.
4 Reply Quote Share
sigma2016Newbie
Posts: 26 · Reputation: 22
#12Aug 6, 2021, 09:18 PM
But base58 is not even enforced by consensus. We could switch everything to base16 and it would work. Easy as that.
3 Reply Quote Share
0xNodeMember
Posts: 257 · Reputation: 80
#13Aug 9, 2021, 04:23 AM
That’s a terrible idea. We need base58, not getting rid of it. This mess started with segwit anyway.
5 Reply Quote Share
gang2015Member
Posts: 215 · Reputation: 62
#14Aug 9, 2021, 09:57 AM
You’re missing the point. Less bits required to steal funds from HD wallets doesn’t mean they’re not easier to use.
1 Reply Quote Share
sigma2016Newbie
Posts: 26 · Reputation: 22
#15Aug 9, 2021, 04:09 PM
But should we bring back P2PK? It was used in early blocks.
2 Reply Quote Share
alpha23Member
Posts: 31 · Reputation: 79
#16Aug 9, 2021, 06:44 PM
Sure, but remember, HD wallets expand a single key deterministically. If someone breaks that key, they access everything.
6 Reply Quote Share
0xNodeMember
Posts: 257 · Reputation: 80
#17Aug 10, 2021, 12:32 AM
Stop spreading false claims. If you think maintaining Bitcoin Core is easy, then go and do it yourself.
4 Reply Quote Share
alpha23Member
Posts: 31 · Reputation: 79
#18Aug 10, 2021, 02:35 AM
Anyone remember the transaction malleability issue before SegWit? This is a huge deal.
1 Reply Quote Share
sigma2016Newbie
Posts: 26 · Reputation: 22
#19Aug 10, 2021, 02:48 AM
Yeah, but legacy addresses can still be used. If they were really unsafe, they’d be completely eliminated.
4 Reply Quote Share
ColdGangMember
Posts: 57 · Reputation: 183
#20Aug 12, 2021, 10:58 AM
P2PKH is safer for sure. But if you’re okay with a single point of failure like a compromised seed, that’s your call.
3 Reply Quote Share

Related topics