Is a Self-Hosted Monero Node Worth It? (2026 Data)
A public node sees your IP and your wallet's requests; your own node sees neither. We measured what a full Monero node costs today and where it actually helps.
Most privacy advice about swapping coins is about the swap service. In practice the bigger collector of metadata is the node your wallet talks to. Open Cake Wallet or Feather on default settings and your wallet asks a server you do not own, do not pay for and cannot audit which blocks have arrived and whether particular outputs belong to you. That server sees your IP address (or your Tor exit), the rhythm of your requests, and the exact moment a transaction you signed first appeared on the network. It cannot read your view key — scanning happens locally — but correlation does not need keys. It needs notes, and it can take plenty. (Monero wallet guide)
What a node costs, measured today (18 October 2026). We queried a public Monero node's restricted RPC and the network's own statistics. Height: 3,786,546. Node database size: 295,279,001,600 bytes, or 274.98 GiB. Transactions processed to date: 64,774,161. Network difficulty 750,312,212,910, hash rate around 6.25 GH/s, 238 alternative blocks on record, peers at 31 in and 32 out. Block weight ceiling 600,000 bytes against a median of 300,000, target block time 120 seconds, and a minimum relay fee of 0.00002 XMR per kB — so a roughly 1.5 kB transaction costs some 0.00003062 XMR, about $0.017 at today's quote of 1 XMR = 566.468303 USDT. Nobody is asking you to download a snapshot: a full node is a 275 GiB, random-read-heavy database that must stay online and keep up. (XMR to USDT exit)
Three layers of exposure, and only one of them is fixed by running a node. Network layer: which IP talks to the blockchain, and when. Wallet layer: whose server answers your queries, and therefore what can be inferred about which outputs are yours. Ledger layer: what the chain publishes about the transaction itself, permanently and to anyone. Your own node fixes the wallet layer completely and part of the network layer — your queries never leave the machine, and your broadcasts leave from your own peer instead of a service's — and does nothing whatsoever for the ledger layer. Swapping into XMR with a self-hosted node is still a visible on-chain transaction. The node just stops a third party from being the one who ties it to you.
Three tiers, priced honestly. (1) A remote clearnet node: free, zero maintenance, and every query described above belongs to the operator — fine for a wallet holding pocket change, wrong for savings. (2) A remote node over Tor, ideally an .onion endpoint: still free, and the operator logs a circuit instead of your home IP; it can still profile request patterns, and onion nodes are slower and occasionally unavailable. (3) Your own node: you pay roughly 275 GiB of disk, electricity, and the duty to keep a service alive; you get a wallet layer that is entirely local, a node other people sync from, and no third party able to hand your wallet stale or partial chain views on a bad day. A middle path worth knowing: read the chain from your own node, broadcast through something that does not carry your home IP. (Is Tor safe for swaps?)
Six steps to a node that actually protects something. 1. Check the disk before anything else: plan 500 GB or more on an SSD; a 275 GiB database plus growth plus logs does not sit comfortably in a 300 GB partition. 2. Start it with monerod --data-dir=/srv/monero --restricted-rpc, adding --prune-blockchain if space is the binding constraint — knowing that pruning trades disk for a full re-sync if you later change your mind. 3. Expect the initial download to be on the order of the database itself, with peer overhead on top, and measure the wait in days on a home connection, not hours. 4. Keep port 18089 private: firewall it to localhost or your LAN. That RPC has no authentication, and --restricted-rpc limits which methods are exposed, not who can call them. 5. Point the wallet at 127.0.0.1:18089 — a manual setting in most wallets, Cake Wallet and Feather included. A new node with a wallet still on defaults protects nothing. 6. If Tor is part of your setup, run monerod with --tx-proxy tor,127.0.0.1:9050 so your own broadcasts do not leave from your ISP's address either. (Monero wallet guide)
Six traps that quietly make a node useless. (1) Exposing 18089 to the internet: you become an open, unauthenticated wallet server for strangers. (2) Syncing onto a spinning disk: the database is random-read heavy, and a wallet polling a thrashing node shows timeouts and stale heights. (3) Leaving the wallet pointed at a remote node after building one — the single most common version of this mistake. (4) Assuming a node equals anonymity: your ISP still sees the connection and peers still see your IP unless you route through Tor, so pairing a self-hosted node with a VPN or Tor is the real privacy configuration. (5) Ignoring the disk until it fills: a node that silently stops on a full volume looks exactly like a chain with no new blocks until you check /get_info. (6) Treating the node as part of the swap: a swap needs an address and a refund address, not a wallet connection, so no node changes what a swap provider learns. (Is Tor safe for swaps?)
When a node is not worth it. The honest answer: for occasional swaps from a wallet funded elsewhere, a node is a lot of maintenance for a small privacy delta. The payoff scales with how much of your balance lives in a self-custodial wallet, how often that wallet is online, and how much you care that no third party holds a request log tying your IP to your outputs. Touch a self-custody Monero wallet a few times a month? An .onion remote node plus Tor is a defensible stopping point, and you can revisit later. Is Monero where your savings sit, with the wallet open daily? Then 275 GiB of disk is the cheapest part of the whole setup. (Is Tor safe for swaps?)
Where a node changes nothing: the swap itself. An instant swap hands the provider a payout address and a refund address, nothing more — no wallet connect, no signature, no node. Numbers from our own quote endpoint today: 100 USDT-TRC20 yields 0.15036374 XMR; 0.05 BTC yields 6.88830672 XMR, i.e. 137.76613 XMR per BTC and an implied Bitcoin price near $78,040; 0.001 BTC yields 0.12842185 XMR; 1 XMR pays 566.468303 USDT-TRC20. Our catalogue currently lists 540 assets across 72 networks, 7 of which need a memo or tag, and the site runs a Tor mirror at 4jyoxqdyx7dh3xfjctihpld7fgliowhimajfszcgypxash5rjqhas3yd.onion for anyone who would rather not have swap traffic leave from the same IP as their wallet requests. All quotes are as of writing time, 18 October 2026 — the live rate on the page is the only one that counts when you send. (Is Tor safe for swaps?)
The three-question test. Ask three things in order. Does your wallet currently talk to a server you do not control? Most likely yes — that is the wallet layer, and it is fixable for the price of a disk. Do you broadcast from an IP that identifies you elsewhere? If yes, a node alone will not help; add Tor or a VPN, because the peer you broadcast to is the one taking notes. Is your Monero balance a running balance or a parking spot? Running balances justify a node, parking spots justify an onion node and a browser tab. Answer all three honestly and the decision makes itself. (Is Tor safe for swaps?)