Sparrow Bitcoin Wallet

[dkbit98]

Today I tried to download Sparrow Wallet again and the speed was improved but there were limits on download. There is definitely a problem on their side. I'll try to contact them and let them know about this issue.

If you are the only one reporting this problem than issue can't be on their side.
Download is working fine for me, and it's not the first time I did that, but you can always use alternative option and download Sparrow from their official github page:
https://github.com/sparrowwallet/sparrow/releases

[1715192791]

1715192791

[1715192791]

1715192791

[1715192791]

1715192791

[1715192791]

1715192791

[1715192791]

1715192791

[1715192791]

1715192791

[cygan]

sparrow has published a new release today
version 1.8.5 includes the following new features:

• whirlpool over decentralized soroban
• faster initial server connections
• restart in a different home folder
• upgrade to hwi 3.0.0

the complete changelog can be found in the github link: https://github.com/sparrowwallet/sparrow/releases/tag/1.8.5
you can also download the new version for your os there as well as on the official website: https://sparrowwallet.com/download/

[zabzob]

Is there a good tutorial out there on how to set up an Electrum server to use with a Sparrow wallet? There's a guide on the Sparrow website for setting up a server with ElectrumX, but I'm wondering whether that's the best option? Is there any reason to use ElectrumX instead of other options like Electrum-Server or Electrs?

Another question I have (which I don't see answered on Sparrow site) is whether it's advisable to run the Electrum server on the same laptop that Sparrow (and Bitcoin full node) is running on. I remember reading somewhere (forget where) that doing that can cause security/privacy issues and it's better to run Electrum server on separate hardware. Is this the case?

[Cricktor]

...

The setup of an Electrum server is off-topic to this thread regardless if you want to use it specifically for a Sparrow wallet. If you dare to use the forum's search, it doesn't hurt by the way, you will find a few threads that discuss various Electrum servers (let me throw in Fulcrum as another option) and also provide valuable instructions how to setup one.

If you dislike the built-in forum's search, try https://ninjastic.space/search instead...

[zabzob]

...

The setup of an Electrum server is off-topic to this thread regardless if you want to use it specifically for a Sparrow wallet. If you dare to use the forum's search, it doesn't hurt by the way, you will find a few threads that discuss various Electrum servers (let me throw in Fulcrum as another option) and also provide valuable instructions how to setup one.

If you dislike the built-in forum's search, try https://ninjastic.space/search instead...

Thanks for the reply and info--Fulcrum looks like the way to go. Didn't mean to be off-topic, I'll look elsewhere for info on setting up an Electrum server. I don't think my second question is off-topic though, since it's asking a specific question about how best to set up a server for use with Sparrow (i.e. is it safe to install both on a single device). But I will search for answers to this question as well.

[Cricktor]

...

I run a dedicated energy efficient device 24/7 for my personal Electrum server on a Raspi 4B 8GB RAM and a 1TB SSD as storage device. Based on a RaspiBlitz node with little mods my Electrum server is Fulcrum. Basically my RaspiBlitz runs a headless bitcoind (as Core), Fulcrum as Electrum server and LND as Lightning node.

As an experimental playground I have another Raspi 4B which runs an Umbrel node which has electrs as Electrum server component. This Umbrel Electrum server can easily be accessed via local network and Tor from outside if necessary.

I run any wallet software, be it a software wallet or to communicate with hardware wallet devices, on a different dedicated computer in my local network. This Linux box is only for wallet software (Electrum, Sparrow, BitBox app, Trezor suite, Bisq) and not used for daily internet stuff.

No particular recommendation, just my personal setup.

[zabzob]

...

I run a dedicated energy efficient device 24/7 for my personal Electrum server on a Raspi 4B 8GB RAM and a 1TB SSD as storage device. Based on a RaspiBlitz node with little mods my Electrum server is Fulcrum. Basically my RaspiBlitz runs a headless bitcoind (as Core), Fulcrum as Electrum server and LND as Lightning node.

As an experimental playground I have another Raspi 4B which runs an Umbrel node which has electrs as Electrum server component. This Umbrel Electrum server can easily be accessed via local network and Tor from outside if necessary.

I run any wallet software, be it a software wallet or to communicate with hardware wallet devices, on a different dedicated computer in my local network. This Linux box is only for wallet software (Electrum, Sparrow, BitBox app, Trezor suite, Bisq) and not used for daily internet stuff.

No particular recommendation, just my personal setup.

Thanks for sharing, that looks like a robust setup.

[ABCbits]

sparrow has published a new release today
version 1.8.5 includes the following new features:

• whirlpool over decentralized soroban

--snip--

I didn't expect they'd implement it quickly. After all, Samourai only announce it on their wallet last month[1].

Another question I have (which I don't see answered on Sparrow site) is whether it's advisable to run the Electrum server on the same laptop that Sparrow (and Bitcoin full node) is running on. I remember reading somewhere (forget where) that doing that can cause security/privacy issues and it's better to run Electrum server on separate hardware. Is this the case?

At least for privacy issue, other people might say that since spying company could find out which node/IP address broadcast certain transaction for first time. In this case, configuring Bitcoin Core to use VPN or Tor should solve the issue.

[1] https://blog.samourai.is/decentralized-whirlpool-stage-1/[/list]

[cygan]

and the next release is out today.
the 1.8.6 version includes the following new features

• wallet search improvements
• all open wallets summary
• mix from postmix
• import Samourai backup file

there are numerous other new functions and various bug fixes. you can read all about them under the following link and also find the download files there: https://github.com/sparrowwallet/sparrow/releases/tag/1.8.6

[satscraper]

Following the latest development with Samourai Wallet , Sparrow team hurriedly released v.1.9.0

Sparrow got rid of the mixing feature, which is a bad birdcage at the current circumstances.

"Remove Whirlpool client, and other Soroban related features and dependencies".

They also  removed "mixing with whirlpool" section from the wallets docs.

[apogio]

Following the latest development with Samourai Wallet , Sparrow team hurriedly released v.1.9.0


"Remove Whirlpool client, and other Soroban related features and dependencies".

They also  removed "mixing with whirlpool" section from the wallets docs.

I prefer to lose the whirlpool feature, rather than losing the wallet.
Do you think it was a wise choice? The question obviously goes to everyone who have been using Sparrow

[satscraper]

Do you think it was a wise choice? The question obviously goes to everyone who have been using Sparrow

Sure, it is a wise movement to prevent the risk of being caught   in the neck by feds, good riddance!

I prefer to lose the whirlpool feature, rather than losing the wallet.

So do I. To be frankly I have never used it because I think such mixing results in the illusion  of improved privacy, thus there's no feeling of deprivation.

Sparrow allows PayNym payments, which serve better in this respect.

[NotATether]

"Remove Whirlpool client, and other Soroban related features and dependencies".

JFC.

I can understand Sparrow Wallet wanting to reduce their liability, but damn, are we going to consider Whirlpool malicious software now?

[Cricktor]

I definitely don't like it that Sparrow has removed mixing. For me it was a nice to have, but I didn't use it very often or all the time. Sad to see that it's handled like something criminal. But OK the devs aren't paid to maintain and develop the software and that alone is likely some hassle. I have to accept that they don't want and need any legal trouble.

[ABCbits]

Following the latest development with Samourai Wallet , Sparrow team hurriedly released v.1.9.0

Sparrow got rid of the mixing feature, which is a bad birdcage at the current circumstances.

"Remove Whirlpool client, and other Soroban related features and dependencies".

They also  removed "mixing with whirlpool" section from the wallets docs.

Based on my memory, the only up-to-date wallet which support CoinJoin are only Wasabi Wallet and Join Market. Sparrow developer also use major number change (1.8.6 to 1.9.0) even though they only remove CoinJoin feature. For average Bitcoiner, we only can see whether someone decide to fork either Sparrow or Samourai Wallet, while preserving it's CoinJoin feature.

[satscraper]

Following the latest development with Samourai Wallet , Sparrow team hurriedly released v.1.9.0

Sparrow got rid of the mixing feature, which is a bad birdcage at the current circumstances.

"Remove Whirlpool client, and other Soroban related features and dependencies".

They also  removed "mixing with whirlpool" section from the wallets docs.

Sparrow developer also use major number change (1.8.6 to 1.9.0) even though they only remove CoinJoin feature.

Yeah, they did a great work on refining Sparrow wallet.  In fact it has almost all  I need to deal with bitcoin. What I would want to have else are WalletConnect interface and the ability to use OP_RETURN when building send transactions. These features and those ones that wallet has already should  cover all my needs.

[dkbit98]

I prefer to lose the whirlpool feature, rather than losing the wallet.
Do you think it was a wise choice? The question obviously goes to everyone who have been using Sparrow

I dont think whirlpool is going to survive in the form it worked in last few years, so yes it was only reasonable decision they could do to avoid the same destiny as another wallet with Japanese name 
However, that doesn't mean that we should now all give up the fight for more privacy on bitcoin just because it's hard and dangerous thing to do.

[shield132]

I prefer to lose the whirlpool feature, rather than losing the wallet.
Do you think it was a wise choice? The question obviously goes to everyone who have been using Sparrow

It's better to have something compared to having nothing. It would be a big loss if we didn't have Sparrow wallet, so losing the whirlpool feature was better than losing the whole wallet. It's like, losing a hand vs losing a life.

I definitely don't like it that Sparrow has removed mixing. For me it was a nice to have, but I didn't use it very often or all the time.

Like you, I haven't used the mixing feature but it was really a great feature for privacy seekers.

A few hours ago I signed and broadcasted a transaction with Sparrow but for some reasons, it wasn't really broadcasted but Sparrow was showing me that it was. I waited an hour, but nothing, the transaction wasn't searchable in the blockchain. Then I input a raw Bitcoin transaction in hex format on Blockchain.com and broadcasted the transaction that way. Then within minutes, my transaction appeared in every blockchain explorer and I also got a confirmation within minutes.
Can anyone tell me why did that happen? Why Sparrow didn't broadcast my transaction? It showed me that it did. Btw Electrum has never failed me.

[satscraper]

Can anyone tell me why did that happen? Why Sparrow didn't broadcast my transaction? It showed me that it did. Btw Electrum has never failed me.

To broadcast transaction Sparrow must be connected to node, either yours or public one.

Probably in your setup Sparrow was  connected to public node, sent to this node your transaction but there was a problem with that node, so the transaction has actually not been broadcast to net.

[Cricktor]

That's another reason why I run my own node for my wallets and for my own Electrum server. I know what going on with my node and I don't need to rely on foreign and unknown other nodes to submit a transaction from my wallet or when my Electrum or Sparrow wallet has to inquire transaction history and transaction updates.

I know, my own Electrum server doesn't collect my wallet's addresses for nefarious address analysis purposes.

I value my privacy.