Node Pruning Explained

Node Pruning Explained

Advanced Running & Operating a Node · 2 views

How blockchain pruning works, what it keeps and drops, when to prune, and how to run a pruned node that still fully validates.

The Monero blockchain grows forever, and a full copy takes a lot of disk space. Pruning lets you run a node that keeps only about a third of that data while still fully validating the chain. For most node operators — especially on a home server, laptop or small VPS — a pruned node is the practical sweet spot. This lesson explains what pruning keeps and drops, the trade-offs, and exactly how to do it.

What Pruning Actually Does

Most of the Monero blockchain's size is old transaction data — specifically the ring-signature data of historical transactions. A node needs that data to serve the full history to others, but it does not need all of it to verify that the chain is valid going forward. Pruning takes advantage of this:

  • It keeps all block headers, the full transaction graph, key images and output data needed to validate new blocks and let your wallet find and spend funds.
  • It discards roughly 7/8 of the bulky ring data for old transactions, keeping only the slice your node is responsible for.
  • The net effect: a pruned node is about a third of the size of a full node, and it still fully validates every block. It is not a "light" or trust-the-server mode — your pruned node verifies the rules itself.

Pruned vs Full — Which Do You Need?

A pruned node is the right default if you want to:

  • Run a personal node on limited disk and still get full validation and privacy.
  • Back a wallet (including over Tor) — wallets work perfectly against a pruned node.
  • Relay and help the network on a smaller machine.

Choose a full (archival) node instead if you need to:

  • Serve the complete blockchain to other nodes doing initial sync, or run a block explorer that displays full historical transaction detail.
  • Provide a public node that some tools expect to have all data. (You can still run a pruned public node; just know it serves pruned data.)

How to Prune

New node, from scratch (easiest): just add the flag and sync once — you'll never download the data you don't need.

./monerod --prune-blockchain

In the Monero GUI, the same option appears as a checkbox ("Prune blockchain") on the screen where you choose to run a local node.

Already have a full node? Prune it in place with the bundled tool — no re-sync required:

./monero-blockchain-prune

This rewrites your existing database down to pruned size. Make sure monerod is stopped first, and that you have a little free space for the operation. Once pruned, keep starting monerod with --prune-blockchain so it stays pruned as it grows.

Things to Know

  • Validation is unchanged. A pruned node enforces every consensus rule — you are not trusting anyone.
  • Your money is unaffected. Your wallet scans and spends normally; pruning is about old, unrelated data, never your keys or outputs (which live in your wallet, not the node).
  • You can't un-prune without re-syncing. Going back to a full node means downloading the dropped data again, so decide based on your role.
  • Initial sync is faster too, since there's less to download and write.

Pruning is how you keep a sovereign, fully-validating node on modest hardware — the foundation for everything else, from private wallet use to running a public node for the community.

Comments

Log in or create a free account to comment.

No comments yet — be the first.