Remote Node vs Your Own Node: What Each Reveals About You
Monero remote node vs own node privacy explained: what a remote node can and cannot see, the real risks, and how to pick the right setup for your threat model.
On this page
- What a node actually does for your wallet
- What a remote node cannot see
- What a remote node can see or do
- Remote node vs own node at a glance
- How much hardware does your own node need?
- Your own node isn’t automatically invisible
- Choosing the right setup: a decision guide
- Practical checklist if you use a remote node
- The bottom line
Key takeaways
- A remote node never sees your keys, balance, recipients or amounts, and it cannot spend your coins.
- What it can see is your IP address, when you sync, and which transactions you broadcast through it.
- A malicious node can also tamper with fees or decoy data to make your transactions easier to single out.
- Running your own node removes the third party; a pruned node needs roughly a third of the full disk space.
- If you must use a remote node, connect to it over Tor or I2P and avoid DNS names that rotate between random nodes.
Almost every Monero wallet will happily connect you to someone else’s node so you can start transacting in seconds. That convenience is real, but so is the trade-off, and it is one of the most misunderstood parts of Monero privacy. This guide sets out what a remote node can and cannot learn about you, and how to decide whether you need your own.
What a node actually does for your wallet
A Monero wallet doesn’t store the blockchain. It needs a node (the monerod daemon) to do three things:
- Serve blocks so the wallet can scan them for outputs that belong to you.
- Supply decoy outputs when you build a transaction. Each input today is hidden in a ring of 16 members: your real output plus 15 decoys pulled from the chain.
- Broadcast your signed transaction to the rest of the network.
When the node runs on your own machine or a server you control, all three steps stay with you. With a remote node, a stranger handles all three.
The Moneropedia entry on remote nodes splits them into two kinds. A private remote node runs on hardware you control, such as a home server or a VPS. An open remote node is run by someone else and shared with the public, either through an aggregator like monero.fail or by advertising itself with the --public-node flag. In this article, “remote node” means an open node run by a stranger.
What a remote node cannot see
A lot of the online panic about remote nodes is overstated, so let’s start with the limits. As Feather Wallet’s documentation explains, a remote node:
- Does not learn your addresses or balance. Your wallet downloads blocks and checks them locally with your private view key, which never leaves your device.
- Cannot see who you pay or how much. Amounts are hidden by RingCT and recipients by one-time stealth addresses. Both stay encrypted on-chain no matter which node relays the transaction.
- Cannot spend your money. Signing needs your private spend key, and the wallet never sends it anywhere.
Key point: A remote node is a metadata risk, not a custody risk. Switching nodes never puts your coins at risk of theft. The worst a node can do is collect information about you.
What a remote node can see or do
Here is what a node operator can collect or manipulate.
Your IP address and timing
On clearnet, the node sees your IP address every time your wallet connects. It knows when you open your wallet, how often you sync, and roughly where you are. That is the same metadata any website collects, but here it sits next to financial activity.
Which transactions you broadcast
This is the big one. When you send XMR through a remote node, that node receives your signed transaction before anyone else. It can’t read the amount or the recipient, but it can record “this transaction hash came from this IP at this time.” If the same operator also gets data from an exchange, a merchant, or a subpoena, that link becomes useful to them.
Leaked Chainalysis training material from 2024 showed exactly this kind of data. An investigation by Digilol found RPC logs of sendrawtransaction requests reaching nodes behind node.moneroworld.com, a round-robin DNS name that several wallets had in their default node lists. In Decrypt’s coverage, a former Monero community member summed up the point: without your IP, an observer like that has very little to work with.
Manipulating the data you receive
A dishonest node can also lie to your wallet. According to Feather’s docs, it can:
- Tamper with fee information so you pay an unusual fee, which makes your transaction stand out from everyone else’s.
- Attempt to bias decoy selection by feeding your wallet crafted output data, which could help reveal the true input. Feather describes the odds of success as low, notes that this never exposes amounts or recipients, and warns you if it detects the attack.
The bootstrap node caveat
If you run a local node in the Monero GUI before it has finished syncing, the GUI can forward requests to a bootstrap remote node in the meantime. The Moneropedia bootstrap-node page warns that replies from that node may be untrustworthy. Until your own node is fully synced, you are effectively still on a remote node.
Remote node vs own node at a glance
| Factor | Open remote node (clearnet) | Remote node over Tor/I2P | Your own node |
|---|---|---|---|
| Sees your IP | Yes | No (sees a Tor/I2P circuit) | No third party |
| Sees which transactions you broadcast | Yes | Yes, but can’t link them to your IP | No |
| Can tamper with fees or decoy data | Yes | Yes | No |
| Sees your balance or recipients | No | No | No |
| Setup time | Seconds | Minutes | Hours to days (initial sync) |
| Disk space | None | None | Full chain, or about a third of it pruned |
| Helps decentralize the network | No | No | Yes |
How much hardware does your own node need?
Less than most people think.
- Storage: The full chain is well over 200 GB and growing, so use an SSD. With
--prune-blockchain, the monerod reference says you save about two thirds of the disk space without losing functionality for your own wallet. A pruned node still validates every block and relays transactions. - Drive type: SSDs make a huge difference. Syncing on a spinning hard drive can take days and is a common reason people give up.
- Always-on vs on-demand: You don’t need to run the node 24/7. Starting it before you use your wallet and letting it catch up for a few minutes works fine.
- Location: A home server, an old laptop, a mini PC or a VPS all work. A VPS paid anonymously keeps your home IP out of the picture, but the hosting company can still see what the machine does.
Tip: Start with a pruned node on your everyday computer. If you find yourself using Monero a lot, move to a dedicated always-on box later. Pruning is easiest to enable on the first sync. Adding it later prunes the data without shrinking the file right away.
Your own node isn’t automatically invisible
Running monerod at home fixes the remote-node problem but introduces a smaller one: your node itself talks to the public P2P network from your home IP. Two things follow from that.
- Your ISP and network observers can see that you run a Monero node. The traffic patterns and default port 18080 make it fairly obvious. In most places this is legal and unremarkable, but if you live somewhere it isn’t, keep it in mind.
- Transactions first leave the network from your IP. Monero uses Dandelion++ to blur where a transaction started, but a well-positioned observer running many peers can still make educated guesses. This is why the Monero Research Lab has recommended since late 2024 that node operators load a ban list of suspected spy nodes.
The fix is to broadcast your own transactions over an anonymity network with monerod’s --tx-proxy option. Blocks still sync over clearnet for speed, but your own transactions leave only through Tor or I2P. Our full walkthrough is in the Privacy & OpSec category.
Choosing the right setup: a decision guide
Match the setup to what you’re protecting against rather than aiming for maximum effort every time.
Casual use, small amounts
A reputable remote node over Tor is fine. Feather Wallet ships with Tor and by default switches node traffic to Tor after the initial sync. Cake Wallet has an experimental built-in Tor option. Avoid round-robin hostnames that send you to a different unknown node each time.
Regular use, meaningful amounts
Run your own node, even pruned, on a machine you control, and point your wallet at 127.0.0.1:18081. Add --tx-proxy so your broadcasts leave over Tor.
High-risk threat model
Run your own node with both inbound and outbound anonymity-network support, use a wallet inside Whonix or Tails, and keep separate wallets for separate identities. At this level, operational habits matter more than any single setting.
Warning: Don’t put your own node on the open internet with full RPC access. If you expose it to other devices, use
--restricted-rpc(or a separate restricted RPC port) so outsiders can’t call admin or wallet-sensitive methods.
Practical checklist if you use a remote node
- Pick nodes from a list that shows uptime and version, such as monero.fail, and stick with one or two rather than hopping around.
- Route the wallet through Tor or I2P. In the Monero GUI, set the SOCKS5 proxy under Settings, then enter a
.onionor.b32.i2pnode address. - Keep your wallet’s default fee setting so your transactions look like everyone else’s.
- Update your wallet. Recent Monero releases include hardening against malicious remote nodes, and the 0.18.5.3 release (October 2026) lists several wallet fixes in this area.
- Treat any node that asks for a “trusted daemon” flag with suspicion. Only mark nodes you operate as trusted.
The bottom line
A remote node can’t take your coins or read your balance, and much of the fear about it comes from misunderstanding that. What it can do is tie your IP address to the moment you send a transaction, and that link is exactly what blockchain-surveillance firms want. Running a pruned node on a cheap SSD closes that gap. If you can’t, routing your wallet through Tor gets you most of the way. Either option beats connecting over clearnet to whatever default node your wallet picked.
Frequently asked questions
Can a Monero remote node steal my funds?
No. Your private spend key never leaves your wallet, so a node cannot sign transactions for you. Its risks are about metadata, not theft.
Does a remote node see my balance?
No. Your wallet downloads blocks and scans them locally with your view key. The node just serves data and never learns which outputs belong to you.
Is a pruned node as private as a full node?
Yes, for your own wallet's privacy there is no difference. Pruning drops old signature data you don't need, and the node still validates everything and relays transactions normally.
Is a public node over Tor good enough?
For most people it is a reasonable middle ground. Tor hides your IP from the node operator, but the node can still see your broadcasts and could still feed you bad data, so your own node remains the stronger option.