Archive Node
Pronunciation: AR-kive NOHD
Also known as: Archival Node
Definition
An archive node is a blockchain node that retains historical blockchain data and, on many smart-contract networks, past state needed to answer queries at earlier blocks. It differs from a standard full node that validates the chain but may prune historical state. Archive nodes support explorers, analytics, contract debugging, audits, and historical balance queries.
Overview
Meaning and scope
An archive node is a blockchain node that retains historical blockchain data and, on many smart-contract networks, past state needed to answer queries at earlier blocks. It differs from a standard full node that validates the chain but may prune historical state. Archive nodes support explorers, analytics, contract debugging, audits, and historical balance queries.
Mechanism and operation
A full node can validate new blocks using current state and canonical history without storing every intermediate state snapshot. An archive node keeps additional database versions so a request such as “read this contract at block X” can be answered directly. The storage burden can be very large and grows with network activity. Fast disks, substantial capacity, memory, database tuning, and long synchronization periods are often required. Backups can be impractical if operators attempt to copy the complete database frequently. Address histories, token transfers, decoded events, and traces may still require an indexer or tracing API.
Practical payment example
An auditor investigating a contract balance at a past block may query an archive node for historical state, while a pruned node might be unable to answer that precise request.
Operational checks
The node supplies authoritative protocol data, while higher-level services transform it into searchable records. Historical queries should specify block hash or canonical height and account for reorganizations. Contract proxy upgrades also require using the code and ABI active at the requested block. Operators should distinguish archive nodes from snapshots, block explorers, and data warehouses.
Distinctions and limits
Documentation should focus on retained state and supported queries rather than the wording alone. If an old state query is critical for accounting or dispute resolution, the organization should preserve its own evidence rather than depend indefinitely on one commercial endpoint.
Related reading
Example
An auditor investigating a contract balance at a past block may query an archive node for historical state, while a pruned node might be unable to answer that precise request.
Comparison
Documentation should focus on retained state and supported queries rather than the wording alone. If an old state query is critical for accounting or dispute resolution, the organization should preserve its own evidence rather than depend indefinitely on one commercial endpoint.
Key Takeaway
An archive node preserves historical protocol state for past-block queries, while indexes, traces, search, and application metadata may still require additional services.
Sources
- Ethereum Documentation: Networking Layer — Ethereum Foundation (2026-07-30)
- Bitcoin Developer Guide: P2P Network — Bitcoin.org (2026-07-30)