Wasabi Pockets 2.0.2.1
My purpose is to attach the Wasabi Pockets to my Bitcoin Core node working on a unique machine on my native community over IPv4. However it looks as if Wasabi Pockets connects to its personal set of nodes and ignores my settings.
Within the Bitcoin tab of the Settings window, there’s a area referred to as Bitcoin P2P Endpoint. The documentation says:
When you’ve got a Bitcoin full node already on a distant pc, then
Wasabi Pockets can use this too. Within the Bitcoin settings, specify the
native IP handle and port or the Tor onion service of your full node.
I assume, since they’re speaking about connecting to a distant pc, that they’re referring to the native community once they say I ought to specify the native IP handle. Nonetheless, the instance they present is that this:
The documentation additionally says:
Wasabi will present up as one of many related friends whereas it’s
downloading a block.
However I by no means see it in my peer checklist.
After I enter my node’s IP handle and port 192.168.1.27:8333 into this area, the pockets seems to begin up simply fantastic, with a message saying Downloading and processing Bitcoin community knowledge.
Nonetheless, I can change that area to one thing like 192.168.1.23:1111, an handle that doesn’t even exist on my community, and once I restart the pockets I see precisely the identical message.
There’s a small white circle with a checkmark in it within the decrease proper nook of the principle window, and once I hover over that circle, it says:
Tor is turned off
Backend is related
Friends 11 related
The place are these 11 related friends coming from? How can I do know if one among them is mine once I do not see it as a related peer? Is there a approach to management which friends the pockets connects to?
