Monero Documentation UnstoppableSwap Previous page: Monero Index page: Documentation Next page: UnstoppableSwap How-to: Use Monero with Wallet Isolation in Qubes-Whonix^™

Isolate the network part (monerod) from the wallet part (Monero Wallet) for better security.

Introduction

These instructions explain how to isolate the network part (monerod) from the wallet part (Monero Wallet) for better security. monerod is the Monero daemon, a full blockchain-verifying background process that downloads and verifies the entire blockchain.

The advantage of this setup is that, should there ever be a vulnerability that allows malware to exploit monerod, all user funds would remain safe, since these would remain isolated in Monero Wallet in a different VM.

If monerod was ever compromised, then this setup would have the same issues as described on the Monero wiki page in chapter Remote Node Security and Privacy Considerations. This issue is unspecific to these instructions.

The connection scheme is Monero Wallet → Qubes RPC → monerod → Tor → Monero network.

Inappropriate Use of Root Rights should be avoided. Instructions on this wiki page have been carefully crafted with when to use sudo and when not to use it in mind. The user should not use sudo unless instructed to do so in the documentation. ^[1]

Warning: This is for testers-only!

Credits: These instructions are based on How to use Monero CLI/daemon with Qubes + Whonix by getmonero.org.

Prerequisite Knowledge

Since this setup is more complex and intended for advanced users only, it is highly recommended to first acquire essential knowledge about using Monero by following the "normal", simpler instructions on the Monero wiki page, without reference to the instructions on this wiki page. Only after the essential knowledge has been acquired should the more complex setup documented on this wiki page be layered on top.

Practicing with a small amount of value is recommended, but not too small (below the dust level, making it impossible to move funds because they are worth less than the required transaction fees). Practicing on Monero testnet first should also be considered. This is unspecific to Whonix.

Optional. How to use Monero Wallet GUI.

If the end goal is to use an offline (airgap) Monero Wallet, learning how to use Monero Wallet GUI would be expendable.

How to use Monero Wallet CLI.

Wallet creation, receiving funds, spending funds.

How to use monerod.

Make sure you understand how monerod works and can interpret its log.

How to use systemd.

You should have a basic understanding of systemd for debugging.

Setup

Qubes `dom0` Configuration

Create App Qubes

In dom0.

It is easier to use the exact same names as in the example below in this chapter. Otherwise, adjustments in the next chapter, "Qubes qrexec Policy Configuration", would be required.

Create monero-wallet-ws qube.

Qubes App Launcher (blue/grey "Q") → Settings Button → Qubes Tools → Create New Qube → Select type: Application

Create Qubes-Whonix-Workstation^™ App Qube
- Name: monero-wallet-ws.
- Color: Choose a color label for the Whonix-Workstation App Qube. Optional suggestion: green
- Template: Choose the Whonix-Workstation Template. For example: whonix-workstation-18.
- Network connection: Choose none.
- Press: Create new qube.

Create monerod-ws qube.

Qubes App Launcher (blue/grey "Q") → Settings Button → Qubes Tools → Create New Qube → Select Type: Application

Create monerod-ws App Qube
- Name: monerod-ws.
- Color: Choose a color label for the Whonix-Workstation App Qube. Optional suggestion: red
- Template: Choose the Whonix-Workstation Template. For example: whonix-workstation-18.
- Network connection: Choose the desired Whonix-Gateway^™ ProxyVM from the list. For example: sys-whonix.
- Press: OK.

Adjust monerod-ws storage size.

Qubes App Launcher (blue/grey "Q") → monerod-ws → Settings → Basic → Private storage max size: 200GiB

Qubes qrexec Policy Configuration

Open Qubes Policy Editor.

Qubes App Launcher (blue/grey "Q") → Settings Button → Qubes Tools → Qubes Policy Editor

Create new policy file.

File → New, for example 20-user

Allow network connection from wallet to monerod VM.

Write qubes.ConnectTCP +18081 monero-wallet-ws monerod-ws allow in the newly created config file.

Click Save and Exit.

`monerod-ws` VM Configuration

Install Monero using Flatpak in monerod-ws.

Install Monero in monerod-ws by following this document: Install Monero

Create data folder for monerod.

mkdir -p ~/.bitmonero

Create folder for systemd --user.

mkdir -p ~/.config/systemd/user

Create file ~/.config/systemd/user/monerod.service.

Open file ~/.config/systemd/user/monerod.service in a text editor of your choice as a regular, non-root user.

If you are using a graphical environment, run. featherpad ~/.config/systemd/user/monerod.service

If you are using a terminal, run. nano ~/.config/systemd/user/monerod.service

Paste the following contents into ~/.config/systemd/user/monerod.service. ^[2]

Notes:

--prune-blockchain is optional. It can significantly lower disk usage without any negative impact on privacy.
--db-sync-mode=safe is optional. It will slow down the sync process, but it prevents the monerod database from being corrupted if you accidentally kill the monerod VM.

[Unit] Description=Monero daemon (Flatpak, user service) After=network.target Wants=network.target [Service] Type=simple ExecStart=/usr/bin/flatpak run \ --command=monerod \ --share=network \ --filesystem=%h/.bitmonero:rw \ org.getmonero.Monero \ --prune-blockchain \ --db-sync-mode=safe \ --data-dir=%h/.bitmonero \ --non-interactive ExecStop=/usr/bin/flatpak kill org.getmonero.Monero Restart=on-failure RestartSec=30 StandardOutput=journal StandardError=journal [Install] WantedBy=default.target

Save and close file.

Reload the systemd user instance.

systemctl --user daemon-reload

Optional: Enable autostart for the monerod systemd user service.

systemctl --user enable monerod

Start the monerod systemd user service.

systemctl --user restart monerod

Check monerod status.

curl -s http://127.0.0.1:18081/get_info

You should see detailed dictionary output from monerod reporting its status; if nothing appears, the monerod service is not functioning properly.

`monero-wallet-ws` VM Setup

Install Monero using Flatpak in monero-wallet-ws.

Install Monero in monero-wallet-ws by following this document: Install Monero

Open file /rw/config/rc.local in an editor with administrative ("root") rights.

Select your platform.

Notes.

Sudoedit guidance: See Open File with Root Rights for details on why using sudoedit improves security and how to use it.
Editor requirement: Close Featherpad (or the chosen text editor) before running the sudoedit command.

Open the file with root rights.

sudoedit /rw/config/rc.local

Notes.

Sudoedit guidance: See Open File with Root Rights for details on why using sudoedit improves security and how to use it.
Editor requirement: Close Featherpad (or the chosen text editor) before running the sudoedit command.
Template requirement: When using Qubes-Whonix, this must be done inside the Template.

Open the file with root rights.

sudoedit /rw/config/rc.local

Notes.

Shut down Template: After applying this change, shut down the Template.
Restart App Qubes: All App Qubes based on the Template need to be restarted if they were already running.
Qubes persistence: See also Qubes Persistence
General procedure: This is a general procedure required for Qubes and is unspecific to Qubes-Whonix.

Notes.

Example only: This is just an example. Other tools could achieve the same goal.
Troubleshooting and alternatives: If this example does not work for you, or if you are not using Whonix, please refer to Open File with Root Rights.

Open the file with root rights.

sudoedit /rw/config/rc.local

Append the following line at the bottom.

qvm-connect-tcp 18081:monerod-ws:18081

Save and close file.

Make the /rw/config/rc.local script executable.

sudo chmod +x /rw/config/rc.local

Restart the monero-wallet-ws VM.

Check monerod access in monero-wallet-ws.

curl -s http://127.0.0.1:18081/get_info

You should see detailed dictionary output from monerod; if you do not, it indicates that monero-wallet-ws was unable to connect to the monerod service in monerod-ws. You should check your Qubes RPC configuration.

Usage

Introduction

Note: On the host (Qubes users: in dom0).

The involved VMs need to be started using any usual method (using Qubes VM Manager (QVMM), starting a terminal emulator, or otherwise).

Start monerod-ws VM.

Check synchronization status.

Run the command in monerod-ws:

curl -s http://127.0.0.1:18081/get_info | grep synchronized

If you see "synchronized": true, your node is ready.

Start monero-wallet-ws VM.

Note: The following instructions should be applied in Whonix-Workstation (Qubes-Whonix: App Qube monero-wallet-ws).

Start Monero Wallet. Either:

A) Start Monero Wallet GUI using any method (from the start menu, from the command line, or through autostart), or
B) Start Monero Wallet CLI using any method.

Done.

The required VMs and Monero Wallet have been started.

Monero Wallet GUI First Time Setup

This first time setup only needs to be performed once.

Optional. The user could also avoid using Monero Wallet GUI and use Monero Wallet CLI instead.

Monero Wallet GUI lacks support for multisig and offline signing.

Note: The following instructions should be applied in Whonix-Workstation (Qubes-Whonix: App Qube monero-wallet-ws).

Monero Wallet GUI → Choose Advanced Mode.

After Monero Wallet GUI has started, it will ask you to create or restore a wallet as usual. This is unspecific to these instructions.

Configure Monero Wallet GUI to use local monerod (which is running in the monerod-ws VM).

The following setting is called remote node. There is no need for concern. See footnote. ^[3]

Monero Wallet GUI should now be running. Go to: ^[4]

Connect to a remote node → Add Remote Node → Address: 127.0.0.1 → Port: 18081

Daemon username: No modifications required. Leave empty.
Daemon password: No modifications required. Leave empty.

(If Monero Wallet GUI was already started, these settings can be found under: Settings → Node)

Done.

Monero Wallet GUI First Time Setup has been completed.

Monero Wallet CLI First Time Setup

Alternatively, Monero Wallet GUI can be used.

Note: The following instructions should be applied in Whonix-Workstation (Qubes-Whonix: App Qube monero-wallet-ws).

Start Monero Wallet CLI.

Outdated command. Requires monero-wallet-cli in /usr/bin.
- monero-wallet-cli
Untested command:
- flatpak run --command=monero-wallet-cli org.getmonero.Monero

Monero Wallet CLI is more "clever" and automatically detects the already available monerod. ^[5] Therefore, as opposed to Monero Wallet GUI, no "remote node" configuration is necessary.

This might not work easily with Flatpak because the host listening port might not be visible from within the Flatpak chroot. This will most likely require additional Flatpak options.

Monitoring

Note: The following instructions should be applied in Whonix-Workstation (Qubes-Whonix: App Qube monerod-ws).

Check the status of the monerod systemd user service.

systemctl --user status monerod

Monitor block height.

curl -s http://127.0.0.1:18081/get_info | grep height

Follow the journal log of the monerod systemd user service.

journalctl --boot --user -f -u monerod

Follow the log file of monerod.

tail -f ~/.bitmonero/bitmonero.log

View the log file of monerod.

Open file ~/.bitmonero/bitmonero.log in a text editor of your choice as a regular, non-root user.

If you are using a graphical environment, run. featherpad ~/.bitmonero/bitmonero.log

If you are using a terminal, run. nano ~/.bitmonero/bitmonero.log

For the initial author of this wiki page, it took approximately 7 minutes from monerod logging SYNCHRONIZATION started until further synchronization progress was actually reported.

2021-11-02 10:53:55.204	[P2P4]	INFO	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:413	SYNCHRONIZATION started
2021-11-02 11:00:20.821	[P2P9]	INFO	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:1680	Synced 201/2484385 (0%, 2484184 left)

Donations

After setting up Monero with wallet isolation, please consider making a donation to the Monero and Whonix projects (Donate) to help keep them running for many years to come.

Donate Monero (XMR) to Whonix.

84ZZSsqyh5niztCgxmWAejDLu9eDerWo4Wsx8woEhDGpdKP3BWPtqenNjKuv8vojrB968U3hqYTKgLGt2zEcGopX1qaEPew

Footnotes

↑ The systemctl --user command must be run as a normal, non-root user without sudo because these are systemd user units and not systemd system units.
↑ Do not use --detach. This is an outdated style for daemons. Error handling is better without it.
↑
- This is safe, because the connection will be made from Monero Wallet in the monero-wallet-ws VM to a self-hosted monerod server running in the monerod-ws VM.
- Only in case of using a "real" remote node hosted by a third-party it is discouraged to select Mark as Trusted Daemon.
↑ Monero Wallet GUI fails to detect already running monerod
↑ monero-wallet-cli detects that monerod's default port 18081 is open on localhost. The detection mechanism is port-based, not process-based.

Whonix

The most watertight privacy operating system in the world.

Dark mode

Supported by Power Up Privacy

Whonix is proudly supported until 2026 by Power Up Privacy, a privacy advocacy group that seeks to supercharge privacy projects with resources so they can complete their mission of making our world a better place. (Strictly subject to our sponsorship policy.)

At Whonix we value freedom and trust, supporting Open Source and Freedom Software

By using this website, you acknowledge you have read, understood, and agree to be bound by these agreements: Terms of Service, Privacy Policy, Cookie Policy, E-Sign Consent, DMCA, Imprint

2012- 2026 ENCRYPTED SUPPORT LLC

Your support makes
all the difference!

We believe security software like Whonix needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 14 year success story and maybe DONATE!

[1] The systemctl --user command must be run as a normal, non-root user without sudo because these are systemd user units and not systemd system units.

[2] Do not use --detach. This is an outdated style for daemons. Error handling is better without it.

[local-vs-remote-3] 
This is safe, because the connection will be made from Monero Wallet in the monero-wallet-ws VM to a self-hosted monerod server running in the monerod-ws VM.

Only in case of using a "real" remote node hosted by a third-party it is discouraged to select Mark as Trusted Daemon.

[4] This is safe, because the connection will be made from Monero Wallet in the monero-wallet-ws VM to a self-hosted monerod server running in the monerod-ws VM.

[5] Only in case of using a "real" remote node hosted by a third-party it is discouraged to select Mark as Trusted Daemon.

[4] Monero Wallet GUI fails to detect already running monerod

[5] monero-wallet-cli detects that monerod's default port 18081 is open on localhost. The detection mechanism is port-based, not process-based.

[1]

[2]

[3]

[4]

[5]

How-to: Use Monero with Wallet Isolation in Qubes-Whonix^™

Page version status

Contents

Introduction

Prerequisite Knowledge

Setup

Qubes `dom0` Configuration

Create App Qubes

Qubes qrexec Policy Configuration

`monerod-ws` VM Configuration

`monero-wallet-ws` VM Setup

Non-Qubes-Whonix

Qubes-Whonix

Others and Alternatives

Usage

Introduction

Monero Wallet GUI First Time Setup

Monero Wallet CLI First Time Setup

Monitoring

See Also

Donations

Footnotes

Navigation menu

How-to: Use Monero with Wallet Isolation in Qubes-Whonix™

Introduction

Prerequisite Knowledge

Setup

Qubes dom0 Configuration

Create App Qubes

Qubes qrexec Policy Configuration

monerod-ws VM Configuration

monero-wallet-ws VM Setup

Non-Qubes-Whonix

Qubes-Whonix

Others and Alternatives

Usage

Introduction

Monero Wallet GUI First Time Setup

Monero Wallet CLI First Time Setup

Monitoring

See Also

Donations

Footnotes

Navigation menu

Search

How-to: Use Monero with Wallet Isolation in Qubes-Whonix^™

Qubes `dom0` Configuration

`monerod-ws` VM Configuration

`monero-wallet-ws` VM Setup