Tails-BitcoinCore-Wasabi icon indicating copy to clipboard operation
Tails-BitcoinCore-Wasabi copied to clipboard

Ensure that Wasabi is connected to Core

Open degenprivacy opened this issue 5 years ago • 1 comments

I followed your documentation but I do not think my Wasabi is connected to my Bitcoin Core node. The official Wasabi docs say that you can verify this by seeing Block acquired from local P2P connection. in the logs. I don't see that in my Wasabi logs so I assume that my Wasabi instance is not actually connected to my Core node.

degenprivacy avatar Nov 22 '20 17:11 degenprivacy

Hey,

My guide only covers how to create the setup, not how to combine different parts.

Tails is firewalled, if you want Wasabi to be able to connect to the local Bitcoin Core you'll have to allow from iptables using something like this (needs admin privilege, you should double check for yourself with an Internet search) every time you start Tails:

sudo iptables -I OUTPUT -p tcp -d 127.0.0.1 --dport 8333 -m owner --uid-owner amnesia -j ACCEPT

Also remember, Wasabi connects to your full node to get the blocks, but a pruned node only has few blocks; if your wallet is older than your pruned height, Wasabi will have to connect to external peers to get those blocks. I.e., when you look for the log comments, make sure you are downloading recent enough blocks.

A different solution is to import your Wasabi XPUB/addresses into Bitcoin Core as watch-only (e.g. using wallet descriptors with the import multi command) and then you can follow/see your new (no rescan with pruned node) activities/balance directly from Bitcoin Core.

PulpCattel avatar Nov 22 '20 21:11 PulpCattel