Wasabi Wallet 22.214.171.124
My goal is to connect the Wasabi Wallet to my Bitcoin Core node running on a different machine on my local network over IPv4. But it seems like Wasabi Wallet connects to its own set of nodes and ignores my settings.
In the Bitcoin tab of the Settings window, there is a field called
Bitcoin P2P Endpoint. The documentation says:
If you have a Bitcoin full node already on a remote computer, then Wasabi Wallet can use this too. In the Bitcoin settings, specify the local IP address and port or the Tor onion service of your full node.
I assume, since they are talking about connecting to
a remote computer, that they are referring to the local network when they say I should
specify the local IP address. However, the example they show is this:
The documentation also says:
Wasabi will show up as one of the connected peers while it is downloading a block.
But I never see it in my peer list.
When I enter my node's IP address and port
192.168.1.27:8333 into this field, the wallet appears to start up just fine, with a message saying
Downloading and processing Bitcoin network data.
However, I can change that field to something like
192.168.1.23:1111, an address that does not even exist on my network, and when I restart the wallet I see exactly the same message.
There is a small white circle with a checkmark in it in the lower right corner of the main window, and when I hover over that circle, it says:
Tor is turned off Backend is connected Peers 11 connected
Where are those 11 connected peers coming from? How can I know if one of them is mine when I don't see it as a connected peer? Is there a way to control which peers the wallet connects to?