Core node components
A full node maintains peer connections, validates incoming data, stores blocks and chainstate, manages a mempool and may build optional indexes. These roles have different storage and performance characteristics.
Pruning can reduce retained block storage while preserving full validation, but pruned nodes cannot serve all historical blocks to applications or peers.
RPC and application boundaries
Applications commonly use authenticated RPC to query a node or submit transactions. RPC should not be exposed directly to the public internet, and wallets should separate signing authority from read-only services where practical.
Resilient operation
Monitor disk space, peer count, sync status, chain tip, clock health and software releases. Back up wallet material and configuration—not chain data that can be independently reconstructed—and test recovery procedures.
Visual recap
A layered node deployment
Consensus validation stays at the center while interfaces expose only what applications need.
Diverse peers
Validation and mempool
Chainstate and blocks
Indexes and RPC
Wallets and apps
Key takeaways
- Validation, storage, relay and indexing are distinct responsibilities.
- Pruning saves disk but limits historical serving.
- RPC requires authentication and network protection.
- Monitoring and tested backups are part of node security.
Lesson recap
Check what you learned
Reveal each model answer, then honestly mark whether you understood it or need another review.
1 of 3
Recall
Does a pruned full node still validate the entire blockchain from genesis during initial sync?
References
