A validating node that discards selected old transaction proof data after checking it. Monero retains the information needed to track the chain and keeps portions of the prunable data to serve peers.
Also called: pruning.
Chain data and retained proof stripes
A pruned Monero node keeps the chain information needed for ongoing operation while discarding selected old prunable transaction data. It retains portions of that data that it can serve to peers.
Different pruned nodes retain different stripes of older prunable data. This lets them contribute data to network synchronization without each keeping a complete archival copy. Pruning does not mean accepting every block without checking it.
References: Moneropedia: pruning · Monero source: cryptonote_core/blockchain.cpp
Internal free space and database file size
Pruning an existing LMDB database can mark internal pages as reusable without reducing the filesystem size of its data file. New database writes can consume that free internal space before the file needs to grow again.
An operator may enable pruning, complete the operation and then see little change in the file size reported by the operating system. That observation alone does not prove pruning failed. Internal allocation and the file's external size are different measurements.
References: Moneropedia: pruning
Starting pruned or creating a pruned copy
Official documentation distinguishes synchronizing a pruned database from the start, pruning an existing database in place, and creating a new pruned copy of a full database. These workflows have different temporary storage requirements.
Before replacing a database, check the documented workflow for the installed release and the space available for any copy. A pruning flag is not an instruction to remove arbitrary database files. Keep wallet backups separate from node-storage maintenance.
References: Moneropedia: pruning · Daemon options and console commands
Historical records and wallet access
Pruning is a node-storage policy. It does not remove your historical payments from the network or hide information already recorded by another party. Other nodes can retain full historical data.
A wallet can use a pruned node. The node still supplies chain data needed by normal wallet scanning. Disk savings depend on chain growth and database state, so a fixed size estimate should not be treated as a permanent requirement.
References: Moneropedia: pruning · Monero source: cryptonote_core/blockchain.cpp
Related glossary terms
Practical guides
Technical baseline: v0.18.5.4. Reviewed 2026-11-08 UTC.