Sparrow/bitcoin core on Linux Mint

[slowLearner2]

Hello,

I’m trying to move away from Windows OS, but I’m getting confused. I installed linux mint, and then I downloaded tar files of bitcoin core and sparrow wallet. I extracted these and then ran the executables and everything seemed to work. Then I realized that I haven’t really compiled or installed anything….

Can you do this lol? I see sparrow actually has a Deb file on the site that I could probably get to install with some software already in Linux mint, but Core only gives you tar files to work with. Are there system/security concerns if I just run the executable file for Core and Sparrow or is this a terrible idea?

Thanks! (Sorry if this is a dumb question)

[Kruw]

Are there system/security concerns if I just run the executable file for Core and Sparrow or is this a terrible idea?

It is ABSOLUTELY CRITICAL that you sync your full node first, connect your Electrum server to your node next, and then connect Sparrow to your Electrum server after that. If you don't perform these steps in this order, all of your transaction history and balance will be sent to third party servers.

This data leak is because Sparrow never implemented BIP157/158 compact filters, and the developer is apparently not interested in adding this protection: https://delvingbitcoin.org/t/state-of-the-transaction-privacy-work-in-bitcoin/2622/25

You should use Wasabi if you care about your privacy, it doesn't need to connect to a full node.

[ABCbits]

Can you do this lol? I see sparrow actually has a Deb file on the site that I could probably get to install with some software already in Linux mint, but Core only gives you tar files to work with. Are there system/security concerns if I just run the executable file for Core and Sparrow or is this a terrible idea?

Yes. Just like windows, you can run app located on "any" location. But since you appear to have security concern, have you verify the authenticity of Bitcoin Core and Sparrow Wallet by performing GPG verification?

Are there system/security concerns if I just run the executable file for Core and Sparrow or is this a terrible idea?

It is ABSOLUTELY CRITICAL that you sync your full node first, connect your Electrum server to your node next, and then connect Sparrow to your Electrum server after that. If you don't perform these steps in this order, all of your transaction history and balance will be sent to third party servers.

While i also prefer to recommend running Electrum server and configure Sparrow wallet connect to it, https://www.sparrowwallet.com/docs/connect-node.html shows you can configure Sparrow wallet to use Bitcoin Core directly.

[NotATether]

As long as you verify the signatures of the Bitcoin Core download (using hashes + PGP), and follow the advice in Kruw's post, you should be just fine.

[Forsyth Jones]

I downloaded tar files of bitcoin core and sparrow wallet. I extracted these and then ran the executables and everything seemed to work. Then I realized that I haven’t really compiled or installed anything….

If you want to install the Bitcoin Core binary (which is in the .tar) on linux, follow this installation guide: https://bitcoin.org/en/full-node#linux-instructions

Something like:

Code:

tar xzf bitcoin-31.1-x86_64-linux-gnu.tar.gz
cd bitcoin-31-1
sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-31.1/bin/*

or

sudo install -m 0755 -o root -g root -t /usr/local/bin bin/*

It is ABSOLUTELY CRITICAL that you sync your full node first, connect your Electrum server to your node next, and then connect Sparrow to your Electrum server after that. If you don't perform these steps in this order, all of your transaction history and balance will be sent to third party servers.

I would say that 99% of people won't be able to do this due to the high complexity, unless they buy a ready-made node like umbrel, mynode or download the Umbrel .iso

A more viable alternative would be to use Sparrow Wallet (it can easily connect directly to Bitcoin Core) > https://sparrowwallet.com/docs/connect-node.html

[slowLearner2]

Are there system/security concerns if I just run the executable file for Core and Sparrow or is this a terrible idea?

It is ABSOLUTELY CRITICAL that you sync your full node first, connect your Electrum server to your node next, and then connect Sparrow to your Electrum server after that. If you don't perform these steps in this order, all of your transaction history and balance will be sent to third party servers.

This data leak is because Sparrow never implemented BIP157/158 compact filters, and the developer is apparently not interested in adding this protection: https://delvingbitcoin.org/t/state-of-the-transaction-privacy-work-in-bitcoin/2622/25

You should use Wasabi if you care about your privacy, it doesn't need to connect to a full node.

That’s sort of depressing. I’m sure I don’t fully understand, but does this mean anyone using QT as their wallet is leaking info about their transactions, or this is limited to “light clients” which Sparrow acts as on top of your node?  Are old full node wallets actually more private than Sparrow by default? Lastly, does a VPN or Tor help at all? You can still see the btc addresses but not linked to IP address? Thanks for the heads up

[slowLearner2]

Can you do this lol? I see sparrow actually has a Deb file on the site that I could probably get to install with some software already in Linux mint, but Core only gives you tar files to work with. Are there system/security concerns if I just run the executable file for Core and Sparrow or is this a terrible idea?

Yes. Just like windows, you can run app located on "any" location. But since you appear to have security concern, have you verify the authenticity of Bitcoin Core and Sparrow Wallet by performing GPG verification?

Are there system/security concerns if I just run the executable file for Core and Sparrow or is this a terrible idea?

It is ABSOLUTELY CRITICAL that you sync your full node first, connect your Electrum server to your node next, and then connect Sparrow to your Electrum server after that. If you don't perform these steps in this order, all of your transaction history and balance will be sent to third party servers.

While i also prefer to recommend running Electrum server and configure Sparrow wallet connect to it, https://www.sparrowwallet.com/docs/connect-node.html shows you can configure Sparrow wallet to use Bitcoin Core directly.

(Hope I didn’t screw this up. Apparently I can only post every so often because I’m new. I changed my response color so my text is easy to pick out of this saved draft)


Thanks, I’m starting to look into running an electrum server or using wasabi as suggested. Now I’m wondering if I’m setting up a server why not just run Electrum? I did verify the downloads (manifests, file hashes). You know more about the operating systems, what’s the advantage of installing these two? The executables still are able to find all the dependencies on their own without compile/install?

[nc50lc]

-snip- but does this mean anyone using QT as their wallet is leaking info about their transactions, or this is limited to “light clients” which Sparrow acts as on top of your node? 

Not particular to GUI clients, it's due to how SPV wallet works.
Sparrow for example, has an option to connect to public Electrum servers if you haven't set it to connect to your own server or Bitcoin client.
Since those are owned by a third-party, you wouldn't know if they're spying on your addresses and transactions.

But not all light clients have terrible privacy, those that are utilizing BIP-158 (Compact Block Filters) should have a pretty good privacy,
although not as good as using your own server/node.

BTW, you can directly connect your Sparrow to your Bitcoin Core if you don't prefer setting-up an Electrum server.
The options in Sparrow's network setting should be self-explanatory.

[ABCbits]

--snip--

(Hope I didn’t screw this up. Apparently I can only post every so often because I’m new. I changed my response color so my text is easy to pick out of this saved draft)

For information, you can quote and response to multiple reply in one reply.

Thanks, I’m starting to look into running an electrum server or using wasabi as suggested. Now I’m wondering if I’m setting up a server why not just run Electrum?

Both Electrum (the wallet application) and Sparrow wallet can connect to Electrum server, so it comes to your own choice and preference.

You know more about the operating systems, what’s the advantage of installing these two?

If you install with .deb file, the application will show on list of application/start menu so you can launch the application in more convenient manner.

There are also other theoretical advantage, such as the application will be placed on more standard location and you can use apt or other application manager to remove the application more conventionally.

The executables still are able to find all the dependencies on their own without compile/install?[/b][/color]

I'm not developer or contributor for either software, but it's likely the executable already include it's own dependency or can automatically find the location of the dependency file.

[Kruw]

That’s sort of depressing. I’m sure I don’t fully understand, but does this mean anyone using QT as their wallet is leaking info about their transactions,

No, Bitcoin Core synchronization is fully private.

or this is limited to “light clients” which Sparrow acts as on top of your node?

It's a specific issue with Sparrow's light client. Other light wallets like Wasabi, Bitcoin-Safe, Zeus, Blixt, and Breez protect your privacy during synchronization by using BIP157/BIP158 compact block filters.

Are old full node wallets actually more private than Sparrow by default?

Almost every other wallet is more private than Sparrow by default.

Lastly, does a VPN or Tor help at all? You can still see the btc addresses but not linked to IP address? Thanks for the heads up

Tor is a nice privacy improvement, satoshi thought so himself: https://bitcointalk.org/index.php?topic=7.msg66987822

Wasabi uses a unique Tor IP for every tx broadcast, peer connection, and coinjoin registration by default. No configuration required.