Thread

Sparrow v2.3.1 has been released to restore BIP32 derivations for consolidation payments in PSBTs. In addition, hiding amounts is now supported, and the keystores that signed a multisig transaction are now shown on the transaction tab. Changelog here:
GitHub
Release 2.3.1 · sparrowwallet/sparrow
Support hiding amounts via the View menu (@kwsantiago) Show the signing keystores in the transaction Blockchain form for spends from multisig walle...
 View quoted note →

Replies (14)

Greetings sir, I hope you're doing wonderful. Thank you for an amazing product. I have a question please: Do you think its a good practice to skip the first account (m/0'/0') and create a new bitcoin account (HD) in Sparrow leaving the first entirely empty and use the second one. Does Sparrow allow this from a technical point? Correct me if I'm wrong, but most wallets will not scan for the next account if the first one is unused in the first place, and to simplify the process of following the standard derivation paths. I thought I'd use a seed phrase + a passphrase + the second account (m/0'/1') altogether to harden my setup, assuming most simple wallets with basic features don't allow setting a custom derivation path, and assuming an attacker don't know about such technical detail *if* they had access to the wallet. Looking forward to hear your thoughts.
↩ replying to npub1hea9...g9v2
Thank you for your response sir. Just to recap: Sparrow (or any BTC wallet with sub-account support) does allow the user to create a second account even if the first one has never been used. Next time in order to restore the wallet from scratch I must either recreate the second account or modify the derivation path manually (depending on the wallet settings / UI) Please do let me know if I'm missing something. Thank you again for your time and support.