Most blockchain node software offers a choice between running a "full" node (retaining complete historical data) and a "pruned" node (keeping only recent data) — understanding this trade-off is essential for planning storage and choosing the right setup for your needs.
What a Full Node Retains
A full, unpruned node keeps the entire blockchain history from genesis to the current tip — every block and transaction ever recorded, letting it independently verify the entire chain's history and serve that complete data to other nodes.
What a Pruned Node Retains
A pruned node validates the entire chain during initial sync (fully verifying every rule was followed) but then discards older block data, keeping only enough recent data to continue validating new blocks and process current wallet operations.
What You Give Up with Pruning
- Ability to serve full historical blockchain data to other nodes on the network
- Ability to re-scan or re-verify very old transaction history locally
- Some advanced use cases requiring historical data access (certain block explorers, some indexing services)
What You Keep with Pruning
- Full validation security — your node still independently verifies every rule during sync, exactly like a full node
- Ability to run your own wallet trustlessly against your own node
- Dramatically reduced storage requirements — often a small fraction of full node size
When to Choose Full (Unpruned)
- You want to contribute full historical data availability to network decentralization
- You're running services (like a block explorer) that need historical data access
- Storage cost isn't a significant constraint for your setup
When to Choose Pruned
- You mainly want trustless wallet verification and current-state validation
- Storage cost or availability is a meaningful constraint
- You don't need to serve historical data to other nodes
Example: Bitcoin Pruning Configuration
# In bitcoin.conf
prune=550550 specifies the target size in MB to retain — adjust based on your specific storage constraints and needs; consult current Bitcoin Core documentation for recommended values.
Can You Switch Between Pruned and Full Later?
Switching from full to pruned is generally straightforward (just enable pruning and the node discards old data). Switching from pruned back to full generally requires re-downloading and re-verifying the discarded historical data from scratch, since it was deleted — plan your choice with this asymmetry in mind.
Impact on Lightning Network Nodes
A pruned Bitcoin node is generally sufficient as the base layer for a Lightning Network node (see How to Set Up a Lightning Network Node (LND) on a VPS), since Lightning doesn't require historical blockchain data beyond what's needed for standard wallet operations.
Common Errors
"Cannot rescan beyond pruned data" when trying to import an old wallet — expected behavior for a pruned node; older transaction history needed for the rescan was already discarded.
Continue Reading
- How to Run a Bitcoin Full Node on a VPS
- VPS Requirements for Running a Blockchain Node
- Blockchain Node Storage Requirements and Growth Planning
Browse more articles in Cryptocurrency & Blockchain Node Hosting.
