Sparrow v2.3.0 released with:
Send to Silent Payments
Pay to DNS address
Min fee rate from server
And more: https://github.com/sparrowwallet/sparrow/releases/tag/2.3.0
https://sparrowwallet.com/download/
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: https://github.com/sparrowwallet/sparrow/releases/tag/2.3.1
Hi Craig, do you know why I can’t see the fiat amount when I download and export transactions on csv? Running v 1.9.1
Best to update for that, currency rate providers change APIs
Not sure which sparrow I’m running but how do I actually update? Is there a tab on the wallet? Thanks.
Download from https://sparrowwallet.com/download/, verify and install - the method differs depending on your OS
Good work! Congrats 💜
Hidding ammounts 💪💪👏👏🍻🙏
Congrats 🫶🏼
Legend, writing yourself into future Bitcoin lore!
Love it 🔥
Thank you!
This is the one 💪
Ur literally the best
Amazing! restoring BIP32 derivations, hiding amounts, and showing signing keystores makes managing PSBTs much smoother. Can’t wait to try it out!
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.
You can do it with Sparrow, how much it helps is difficult to say - depends on your threat model.
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.
Some wallets (eg Trezor Suite) do not allow you to create a second account if the first one is unused. Sparrow does, however. Otherwise all correct.
