Thread

Nuevo release de la mejor Bitcoin only wallet de escritorio, @SparrowWallet. Como siempre con mejoras muy interesantes y correcciones que dan más versatilidad y seguridad! Más info en el mensaje de la propia cuenta de Sparrow y en el link de Github: https://github.com/sparrowwallet/sparrow/releases/tag/2.1.3 👇👌👇 nostr:nevent1qvzqqqqqqypzp0n622gm2vhghyv09hyczjy53gea8cx6qaug6aqk7ua5cag57z8xqqszwelv7hn7pq5dkgg7pm4n5azmng2daw2dk7c8z5le8vyjzdnrvxsekqkan

TY

Hi there. Since v. 2.1.2, Sparrow (in Ubuntu Linux, .deb package) does not find bitbox hww. I click on Scan and nothing happens. Before that version it was working flawlessly. Any ideas on what might be happening?

Actually since v. 2.1.0

Open a Github issue.

Should the OneKey Pro Integration work via QR (I think it should)? Cannot find that option under “Airgapped HW Wallets” 😞

Thank you for Sparrow! 🙏 Question about its use with tails.net . On each boot, I manually run sudo dpkg -i ~/Persistent/path/to/sparrow.deb , wallets & config are saved with dotfiles feature. Is an appimage a possibility so I can just run that, or should I try to find a way to automate the running of the dpkg command?

You have to import the wallet over USB first.

Hm… I’d like to remain it air gapped. Is there a chance this will be added latter?

I have never used Sparrow but have it downloaded on my desktop now. I've heard lots of good things about it.

The standalone version works just fine in the persistent folder. There're easy tutorials how to install it with a menu entry in tails. There's one in the German forum of "blocktrainer" that worked for me

Inspired by your bitcoin.review BR096 conversation I heard today about upgrading Bitcoin on nodes. I don't want to upgrade my node or my Sparrow if I don't have to. I'm using Sparrow 2.0.0 as my online watch-only wallet. I rarely touch it, only to transfer off the exchange every few months (to keep my utxos large). It works perfectly fine for my use-case. In fact, I've found no other wallet that works for me, thank you! Is there a way to tell on the GitHub /releases page that I really should update for any security reasons? Is there a flag or string I should search for on that page? Is there an industry standard way to communicate such an upgrade urgency in release notes? Thanks for all you do for all of us. nostr:nprofile1qyv8wumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wsq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5qqsqfjg4mth7uwp307nng3z2em3ep2pxnljczzezg8j7dhf58ha7ejgqgzx3h