admin Most Monero users never run a node. They install a wallet, point it at a remote node run by someone else, and never think about it again. That works, but it costs you privacy and it costs the network capacity. If you hold XMR seriously, running your own node on a cheap VPS is one of the best hours you can spend. This guide covers what a node actually does, what hardware it needs, and what it costs per month in 2026.
What a node does and why remote nodes leak information
A Monero node stores the full blockchain and answers your wallet’s questions. Every time your wallet refreshes, it asks a node to scan blocks for outputs that belong to you. When you use a remote node, the operator sees your IP address, when you sync, and can log which blocks you request. The operator cannot see your balance or your counterparties, because Monero’s one-time addresses and RingCT amounts hide those from everyone, including node operators. But the pattern of your requests, combined with timing, is metadata. Running your own node removes that observer entirely.
There is a second reason that matters more than people admit: the supply of good remote nodes is thin. Public remote nodes carry the load of thousands of lazy wallets, and when they rate-limit you, your transactions stall at the worst moment. Your own node never queues you behind anyone.
What the blockchain actually requires in 2026
The Monero blockchain passed 200 GB some time ago and grows by roughly 40 to 60 GB per year depending on network activity. That means the old advice of “any 40 GB VPS works” is dead. Here is a realistic minimum for a pruned node in 2026:
- Disk: 120 GB minimum, 160 GB comfortable. A pruned node stores about one third of the full dataset but still needs headroom during sync, when temporary files can double the footprint.
- RAM: 2 GB works with a pruned node if you add 2 GB of swap. 4 GB lets you run unpruned without sweating.
- CPU: almost irrelevant. Two cores of any modern VPS will do. Monero verification is light compared with mining.
- Traffic: budget 1 to 2 TB per month. Initial sync pulls the chain once, then steady-state relay traffic is a few GB per day.
Pruning is the key trick. Start the daemon with monerod --prune-blockchain and the node keeps the data it needs to verify new blocks while discarding about two thirds of historical data. A pruned node is still a full consensus participant. It is not a light client. If you later want to run a node that serves the full chain to others, skip pruning and budget the full disk.
Setup in five steps
The setup is shorter than most wallet tutorials. On a fresh Ubuntu or Debian VPS:
- Create a dedicated user. Do not run the daemon as root.
adduser monerois enough. - Download the official binaries from getmonero.org and verify the GPG signature of the hash file. This step matters. Fake Monero binaries circulate on mirrors, and a tampered daemon on your own server is a perfect spy.
- Run
monerod --prune-blockchain --detach. Initial sync takes anywhere from a few hours to two days depending on disk speed. NVMe storage syncs several times faster than SATA or network-attached storage. - Open port 18080 inbound in your firewall so your node relays transactions to the network. A node that only leeches still works, but an open node contributes.
- Point your wallet at it: in the GUI wallet, set the daemon address to your VPS IP with port 18081 for restricted RPC, or run the CLI wallet with
--daemon-address.
Restrict the RPC port with --rpc-restricted-bind-ip 0.0.0.0 --rpc-restricted-bind-port 18081 --no-igd --confirm-external-bind if you want to use the node from outside without exposing full RPC. The restricted RPC mode hides sensitive daemon commands from remote callers.
Monthly cost reality check
You do not need a dedicated server. A 160 GB NVMe VPS with 4 GB RAM costs 6 to 12 dollars a month from most providers in 2026, and smaller providers running Black Friday deals often land under 5. Paying a year upfront on a mid-tier provider is the sweet spot. What you should not do is pick the absolute cheapest KVM with network storage: sync speed and pruned-node responsiveness live and die by disk I/O.
One privacy note worth the money: pay for the VPS with Monero itself if the provider accepts it, and skip the provider’s managed-add-ons that log your activity. Your node IP is associated with your wallet usage pattern, so choosing a provider that accepts XMR keeps the whole chain of custody clean. If you need to buy XMR first, our guide on where to buy Monero and where to store it covers the current options.
Going one step further: serving the network
Once your node runs smoothly, you can open it as a public remote node for others, or set up monero-wallet-rpc behind it to accept payments for a store. Merchants running their own infrastructure get faster confirmation handling and no dependency on a stranger’s node staying up. If you accept XMR payments and currently rely on a public node, you are one VPS reboot away from a broken checkout page.
Common failure modes
Three things break home-grown nodes in practice. First, disk full: unpruned nodes on 100 GB disks die silently around month eight. Second, swap death: 1 GB RAM with no swap will get OOM-killed during a mempool spike. Third, provider NAT: some cheap VPS plans block the P2P port, leaving your node connected to eight peers that found it through limited channels. Test with monerod print_pl | head -30 and check the status line shows a healthy peer count, usually above 20 once warmed up.
Verifying your own balance without trusting anyone is the whole point of Monero. If you want to go further and let others verify payments to you without revealing anything, read our walkthrough on verifying a Monero transaction with a view key. A node plus a view key covers most of what people actually want from financial privacy.