SwapSS learn

Remote node or your own node: what each one really costs

Your wallet needs somebody’s copy of the chain. Either you keep one or you ask a stranger for theirs. The usual framing is privacy against convenience, which is close but imprecise: what you actually trade is a specific set of observations, handed to a specific party, against disk space and one long first sync.

What a remote node can observe

It never receives your keys and it cannot spend anything. What it does receive is a stream of metadata that is easy to underrate. Monero’s own glossary is blunt about the core of it: node operators can link transactions to IP addresses.

  • Your IP address, and the hours of the day your wallet is open.
  • The height your wallet starts syncing from, which hints at when the wallet was created.
  • The transaction you hand it to broadcast. It sees that before the rest of the network does.
  • The set of outputs your wallet fetched to build a ring. It does not learn which member is yours, but it knows the set came from you.
  • What it does not see, when your wallet downloads blocks and scans them locally: your view key, your spend key, your balance.

What a dishonest node can do, not just see

The failure mode is lying by omission. A node can serve a stale chain, withhold the block that contains your payment, or misreport fee levels so that you overpay or send something that sits unconfirmed. It cannot fabricate a payment to you, because your wallet checks the chain’s own proofs. This is not a hypothetical class of bug: the 8 July 2026 point release lists hardening against malicious remote nodes among its changes, which is what a maintained defense against it looks like.

What your own node costs in 2026

Three real costs, in the order people usually underestimate them.

  • Disk: the full chain file is about 280 GB as of June 2026. A pruned node keeps about 95 GB by discarding seven eighths of old ring signature data, with no privacy or security downside for you - it simply serves less history to peers.
  • First sync: the cost is verification, not download. The machine checks every block. On a modern desktop with a solid-state disk it is hours; on a small always-on box or a spinning disk it can run for days. Any single number quoted for this is wrong for somebody.
  • Upkeep: one block every two minutes means steady-state traffic is trivial next to the first sync. Serving other peers is what actually consumes bandwidth, and that is configurable.

What a light wallet is actually doing

A light wallet does not scan on your device. It gives your private view key to a scanning service, which watches the chain and returns the outputs that belong to you. The reference implementation describes it in exactly those terms: clients submit their view key, and the server scans for incoming transactions. The operator can therefore see every payment into that wallet and its amount, for as long as it holds the key, and a disclosed view key cannot be taken back. It still cannot spend, because your spend key never leaves you, and a view key alone does not reliably reconstruct your outgoing transactions.

When each answer is the right one

The decision is usually settled by two facts: how much you hold, and whether you have 95 GB to spare.

  • Your own node: meaningful balances, frequent transactions, or a preference that nobody sits between your IP and your transactions.
  • Your own node at home, reached from your phone: most of the benefit, none of the phone storage problem.
  • A remote node reached over Tor: no room for the chain, or a mobile-only setup. The IP link goes away; the timing, and the fact that some Tor user asked, do not.
  • A light wallet: an address you are content for a service to watch, or small day-to-day amounts. Not a savings wallet, because the disclosure is permanent.

Common questions

The questions that settle it for most people.

  • Does pruning hurt privacy? No. It stores less history for other people. Your own verification and scanning are unchanged.
  • Can a remote node steal my coins? No. Spending needs your spend key, which stays in your wallet.
  • Can a remote node tell that a transaction is mine? It sees the transaction arrive from your IP before the network does, which is a strong hint. Over Tor it sees a circuit instead.
  • How long does the first sync take? Hours on fast hardware, days on slow. It is bound by verification, so processor speed matters more than connection speed.
  • Do I need the full 280 GB? Only if you want to serve full history to other nodes. Pruned is the normal choice.