Which anonymity network is better

Connect a local wallet to your own background service via Tor

Below you will find an exemplary configuration with which you can run a Monero background service (e.g. on a home server or VPS), to which you can connect from another computer on which your wallet is running. The transaction information required for your wallet is restored via the Tor anonymity network. The good thing about this approach is that the background service () can be operated at all times and can therefore permanently send / receive blocks, while the wallet can only be connected to it when required - if it requires access to the entire blockchain. Monerujo should also run via Orbot. Since Tor's hidden services offer encryption and authentication, you can be sure that your RPC credentials will not be sent to the "Clear (net)". Tor also fixes problems (such as port forwarding or IP address switching) that are common with private servers - it just works. This facility also disguises the fact that you are connecting to a Monero remote node. The connection of a Mac laptop to a Linux remote node (Ubuntu 18.04.2) with the Monero version was tested.

Create a hidden Tor service for RPC

Make sure Tor is installed and running properly. Only then do you continue.

The RPC server only has to be set up in such a way that it runs as a hidden service, here on port.


Restart Tor:

Make sure Tor started correctly:

If everything looks good so far, make a note of the name of the hidden service (onion address):

It will look something like "4dcj312uxag2r6ye.onion". You use it for below.

Set up background service for RPC

In this example, Tor is not used to interact with the P2P network, only to connect to the Monero node; this means that only the hidden RPC service is required.

File: (in the home directory of the Monero user)

(Think of a USERNAME and a PASSWORD for the RPC)

Restart the background service:

Make sure the background service started properly:

Connect to your node from a local wallet

Make sure Tor is running locally so that you can connect to the Tor network. On the Mac, an easy way to do this is to simply start the Tor browser and use the Tor background service.

Then test a simple RPC command like:

Replace, and with the values ​​above. Change to a different port if required by your local Tor background service.

If all goes well, you should get information about the remote background service after running the command. If not, add `-v` to the beginning and then test for what reason the connection is not being made; check firewalls, password etc.

As soon as everything works, you can connect via the CLI wallet:

Substitute the values ​​as needed.


If you're interested in experimenting with the GUI via Tor, you can give it a try (be aware that this could leak information - better not rely on it if your life depends on maintaining your anonymity). This example is for MacOS, you can adapt it as needed for the Linux GUI:

This allows the GUI to communicate with the Tor network. Once the GUI is open and a wallet is loaded, you'll need to set it up to connect to the Tor network. You do this by adding your onion address here: "Settings> Node> Remote-Node> Address".

We anticipate that direct Tor / I2P support will be included in future versions of the GUI so that + command lines are not required.

"Back to the list