node_wallet

Exactly, don’t think that pricey SSDs are a magic fix for backup. Even they can fail pretty quickly.

That’s a bit off-putting. Seems like a manual process. I’d rather have a standardized way to do backups.

I think the lack of a solid paper-backup format is kinda lame. Has Bitcoin Core's team recommended a physical backup method yet?

Yeah, I hear you. But for folks who often misplace passwords, especially those linked to wallets, this might help. Users need to grasp how BIP-39 and BIP-85 work, though. There’s still the chance of losing a traditional…

Exactly! Ideally, she’d hold onto everything needed for recovery if she ever forgets the password from BIP85. But since she’s not really tech-savvy, I keep copies so she can access them, like the BIP-39 passphrase. I…

Recently, there have been some cool updates in the Bitcoin space like BIP32, BIP39, Segwit, and taproot. But honestly, BIP85 is what really got my attention. It’s all about managing those pesky seed phrases and I think…

Looks like you forgot to activate the descriptor meant for receiving. You need to add the "active":true argument to that descriptor. Also, for the change address, make sure you have both "active":true and…

As others here have said, this could easily be abused. Decoy wallets may be the way to go. Get a cheap hardware wallet and regularly make transactions to build up some history.

This could help negotiate with criminals, but Bitcoin wasn’t designed for that. Glad it’s not an option; imagine the chaos if it was.

Yeah, that’s a good suggestion. But honestly, I wouldn’t recommend using iancoleman for seed phrases anyway. It's all JavaScript, you know? Not the best setup.

But what about credit cards that hold crypto? They’re bound by strict rules. Plus, they sacrifice privacy compared to true crypto transactions.

I’m with you on that. Using another password for GPG encryption helps too. Just make sure not to compromise the Bitcoin Core password!

I sometimes miss the obvious things. You suggesting there’s something else to worry about with BIP38?

You nailed it. Software can be secure but if the system is compromised, it’s like locking a gold bar in a safe with an impossible PIN and leaving it on the street.

That’s why I wouldn’t bother with a pruned node. If your transactions go back further than what’s saved, guess what? You’re downloading the blockchain and reindexing all over again. My advice? Keep a full node if you…

We need more info. Are you loading the exact same wallet file on both PCs? What version of Bitcoin Core are you dealing with here? Also, what's the prefix of the addresses? 1 for legacy, 3 for p2sh-segwit, or bc1 for…

Here’s something interesting about how Bitcoin Core handles importing extended private keys. If you set the descriptor at the root node (m) and export them later using something like the gethdkeys command, it won’t…

Seriously, OP, watch out for those offers. New accounts offering help are usually shady. Plus, was this wallet backed up with a password? What software are you using?

Brain wallets are risky, no doubt. You can play around with them if you want to see how they work, but there are secure options out there. Just go for a seed phrase and maybe a hidden wallet with a BIP39 Passphrase.…

Try just importing the receiving descriptor into Sparrow. No need for the change descriptor; Sparrow calculates that automatically using the extended public key. I tested this and it worked fine for me!