An archival node (also known as a full archival node) is a critical component of blockchain infrastructure that stores the entire history of the ledger. Unlike a standard full node, which may prune older data to save disk space, an archival node retains every single block, transaction, and the complete state (the collective snapshot of all account balances and smart contract data) at every point in the chain's history. This makes it the most resource-intensive type of node to run, requiring significant storage capacity and bandwidth.
LABS
Glossary
Archival Node
A blockchain node that maintains the entire historical record of the network, from the genesis block to the present, including all transactions and state changes.
Chainscore © 2026
definition
BLOCKCHAIN INFRASTRUCTURE
What is an Archival Node?
An archival node is a type of blockchain node that maintains a complete, unpruned historical record of the entire blockchain, including all transactions and state data from the genesis block.
The primary function of an archival node is to serve as a definitive source of historical data for the network. It enables complex queries that require deep historical context, such as auditing the complete transaction history of an address, analyzing historical network metrics, or reconstructing the state of a smart contract at a specific block height. Services like block explorers, on-chain analytics platforms, and certain indexers rely heavily on archival nodes to access and serve this comprehensive data to end-users and applications.
Running an archival node involves synchronizing and validating the entire blockchain from its inception, a process that can take days or weeks for established networks like Ethereum or Bitcoin. Due to the immense storage requirements—often multiple terabytes—these nodes are typically operated by dedicated entities, including research institutions, exchanges, and infrastructure providers. The existence of a robust network of archival nodes is essential for decentralization, as it ensures historical data remains verifiable and accessible without relying on a single centralized source.
how-it-works
BLOCKCHAIN INFRASTRUCTURE
How an Archival Node Works
An archival node is a type of blockchain node that maintains a complete, unpruned copy of the entire ledger, storing every transaction and state change from the genesis block to the present.
An archival node operates by downloading, validating, and permanently storing the entire historical data of a blockchain. This includes every single block header, transaction, and the full state—the complete record of all account balances, smart contract code, and storage—at every point in the chain's history. Unlike pruned or light nodes, it does not discard any data, making it the definitive source for historical queries and deep chain analysis. Its primary function is to serve as a trustless data archive for the network.
The operational mechanics involve running client software like Geth for Ethereum or Bitcoin Core, which synchronizes with the network by downloading and verifying the entire chain. This process, known as an archive sync, is the most resource-intensive synchronization mode. It requires significant storage (often multiple terabytes), substantial RAM for state management, and considerable bandwidth. Once synchronized, the node continuously validates new blocks and broadcasts them to peers, while also serving historical data to other nodes, explorers, and applications via its RPC (Remote Procedure Call) interface.
Archival nodes are critical infrastructure for services requiring comprehensive historical access, such as blockchain explorers (Etherscan), analytics platforms (Dune Analytics, Nansen), and indexing protocols (The Graph). They enable complex queries about historical token flows, smart contract interactions, and on-chain governance events. For developers, they are essential for debugging, auditing smart contract histories, and running services that depend on complete state data, such as certain oracles or bridges.
The distinction between an archival node and a full node is important. While all archival nodes are full nodes, not all full nodes are archival. A standard full node typically prunes old state data, keeping only recent states and block headers to conserve disk space. An archival node, by retaining everything, provides a public good for the ecosystem but at a high operational cost, which is why they are often run by dedicated infrastructure providers, research institutions, and foundations rather than individual users.
key-features
BLOCKCHAIN INFRASTRUCTURE
Key Features of Archival Nodes
Archival nodes are specialized blockchain nodes that store the complete historical state of a network, enabling deep data analysis, auditing, and services that require access to any past transaction or state.
01
Complete Historical State
Unlike standard full nodes, which prune old data to save space, archival nodes store the entire historical state of the blockchain. This includes every transaction, smart contract interaction, and the state of every account at every block height. This is essential for services like block explorers, advanced analytics platforms, and forensic auditing.
02
Data Availability for Indexers
Archival nodes are the primary data source for blockchain indexers (e.g., The Graph) and other middleware services. These services query the node's historical data to build searchable, structured databases (subgraphs) that power decentralized applications (dApps), providing fast access to complex historical queries that would be impossible to run directly on-chain.
03
Auditing and Compliance
They provide an immutable, verifiable record for regulatory compliance, tax reporting, and security audits. Auditors can trace the complete flow of funds, verify the provenance of assets (e.g., for NFTs), and investigate suspicious activity by reconstructing events from the genesis block.
04
High Resource Requirements
Maintaining an archival node demands significant resources:
- Storage: Terabytes to petabytes of fast SSD storage, growing continuously.
- Memory (RAM): High RAM is required to efficiently manage the state trie.
- Bandwidth: Constant high-throughput syncing and serving data to queries. This makes them expensive to run, leading to fewer archival nodes compared to full nodes.
05
RPC Endpoint for Advanced Queries
Archival nodes expose JSON-RPC endpoints that support historical queries, such as eth_getBalance or eth_call for a specific past block number. This allows developers to query historical token balances, simulate old transactions, or check the state of a smart contract at any point in time, which is not possible on a pruned full node.
06
Network Bootstrapping and Recovery
Archival nodes act as a trustless source of truth for bootstrapping new nodes and recovering from network partitions. A new node can sync from an archival node to obtain a guaranteed complete and verified copy of the blockchain history, ensuring the integrity and consistency of the network's shared state.
COMPARISON
Archival Node vs. Other Node Types
A functional comparison of core blockchain node types based on data storage, resource requirements, and network role.
| Feature / Metric | Archival Node | Full Node | Light Node (SPV Client) |
|---|---|---|---|
Data Storage | Complete historical blockchain state (all blocks, transactions, state) | Recent blockchain state (pruned blocks, current state) | Block headers only |
Storage Requirement |
| ~100-500 GB (pruned) | < 1 GB |
Network Role | Serves historical data queries, supports explorers & indexers | Validates & relays transactions/blocks, enforces consensus | Verifies transactions via Merkle proofs, depends on full nodes |
Resource Intensity | Very High (CPU, RAM, Storage, Bandwidth) | High (CPU, RAM, Bandwidth) | Low (minimal resources) |
Bootstrapping Time | Days to weeks (sync from genesis) | Hours to days (sync recent state) | Minutes (sync headers) |
Historical Query Capability | |||
Independent Validation | |||
Typical Operator | Data providers, analytics firms, block explorers | Developers, validators, exchanges, dedicated users | Mobile wallets, IoT devices, end-users |
primary-use-cases
ARCHIVAL NODE
Primary Use Cases and Ecosystem Usage
Archival nodes serve as the definitive historical record for a blockchain, enabling advanced data queries and ecosystem services that require access to the complete state history.
technical-requirements
ARCHIVAL NODE
Technical Requirements and Costs
Running an archival node demands significant hardware resources and operational overhead to store and serve the complete, unpruned history of a blockchain.
01
Storage Requirements
Archival nodes require terabytes (TB) of fast storage to hold the entire blockchain history, including all historical states. For example, an Ethereum archival node requires over 12 TB of SSD storage, growing by hundreds of gigabytes per month. This is in stark contrast to a full node, which may only need 1-2 TB after pruning old state data.
02
Memory (RAM) & CPU
Processing historical data queries demands high-performance hardware. Key requirements include:
- RAM: 32 GB or more is standard to handle in-memory state caches and serve queries efficiently.
- CPU: Multi-core processors (e.g., 8+ cores) are needed for parallel transaction and block processing, especially when replaying the chain or serving complex queries.
03
Bandwidth & Uptime
Archival nodes must maintain a constant, high-bandwidth connection to the peer-to-peer network.
- Bandwidth: Unmetered or high-data-cap connections are essential, as initial sync can download terabytes of data, followed by continuous block propagation.
- Uptime: Near 100% uptime is critical to avoid falling behind the chain tip and to be reliably available for data services.
04
Operational & Financial Costs
The total cost of ownership is substantial, encompassing:
- Hardware: Enterprise-grade SSDs, servers, and networking equipment represent a large capital expenditure.
- Hosting: Cloud instances with the required specs (e.g., AWS i3en.metal) can cost over $1,000 per month.
- Maintenance: Requires dedicated DevOps or sysadmin expertise for software updates, monitoring, and troubleshooting.
05
Comparison to Other Node Types
Archival nodes are the most resource-intensive. A full node validates all rules but can prune old state data. A light client or light node only downloads block headers, requiring minimal resources. An archive node is specifically configured to retain everything a full node does, plus all historical state, making it essential for block explorers, analytics platforms, and historical data APIs.
06
Use Cases Justifying the Cost
The high cost is justified for specific applications that require deep historical access:
- Block Explorers (e.g., Etherscan): To query any transaction or account state from any block.
- Analytics & Research: For on-chain data analysis, trend reporting, and academic research.
- Infrastructure Services: Providing historical data via RPC endpoints for dApps, wallets, and developers.
- Auditing & Forensics: Investigating historical events, security incidents, or compliance matters.
security-considerations
ARCHIVAL NODE
Security and Decentralization Role
An archival node is a type of blockchain node that stores the complete history of the network, including every transaction and state change since the genesis block. It is the most resource-intensive node type and serves as the ultimate source of historical data for the network's integrity.
01
Complete Historical Record
Unlike full nodes, which typically only store recent blocks to validate new transactions, an archival node maintains the entire blockchain history. This includes every block, transaction, and the full state (account balances, smart contract code, and storage) for every block height. It is the definitive archive for auditing and deep historical analysis.
02
Resource Requirements
Running an archival node demands significant and growing resources:
- Storage: Requires terabytes of disk space (e.g., Ethereum's archive data exceeds 12TB).
- Memory & CPU: Needs high-spec hardware to serve complex historical queries.
- Bandwidth: Must handle sustained data synchronization and serving requests. This high cost is why few participants run them, creating a trade-off between accessibility and decentralization of historical data.
03
Primary Use Cases
Archival nodes are not for everyday transaction validation. They are critical infrastructure for:
- Block Explorers & Analytics: Services like Etherscan query archival nodes to display historical transactions and states.
- Developer Tooling: Needed for tasks like replaying old transactions or debugging historical contract states.
- Auditors & Researchers: Enable forensic analysis of the chain's complete history for compliance or study.
04
Decentralization & Trust
While full nodes decentralize transaction validation, archival nodes decentralize historical truth. If only a few entities (like centralized infrastructure providers) run archival nodes, they become single points of failure for accessing the chain's history. A healthy network requires a distributed set of archival operators to prevent historical data censorship or manipulation.
05
Comparison: Full vs. Archival
Full Node:
- Stores recent blocks (e.g., last 128).
- Validates new transactions/blocks.
- Prunes old state data.
- Lower resource requirement.
Archival Node:
- Stores all blocks from genesis.
- Maintains all historical states.
- Does not prune data.
- Serves complex historical queries.
- Essential for services, not required for network consensus.
06
The Pruning Process
Most full nodes use state pruning to delete old state data not needed for validating new blocks, drastically reducing storage needs. An archival node disables this pruning. Some networks offer archive mode as a configuration flag when syncing a node. Services like Erigon and Nethermind for Ethereum implement advanced storage models to make running archival nodes more efficient.
DEBUNKED
Common Misconceptions About Archival Nodes
Archival nodes are critical infrastructure for blockchain data integrity, yet they are often misunderstood. This section clarifies their true purpose, capabilities, and limitations by addressing the most frequent points of confusion.
An archival node is a full node that retains the complete historical state of the blockchain, while a standard full node typically prunes old state data to save disk space. All archival nodes are full nodes, but not all full nodes are archival. A full node validates all transactions and blocks, storing only the current state and recent block headers. An archival node goes further by preserving every single historical state, transaction, and receipt from the genesis block. This makes it essential for services like block explorers, analytics platforms, and certain developer tools that require querying arbitrary historical data, which a pruned full node cannot provide.
examples-in-practice
ARCHIVAL NODE
Examples in Practice
Archival nodes are deployed for specific use cases requiring deep historical data access, often by specialized services and institutions.
02
Regulatory Compliance & Auditing
Financial institutions, auditors, and regulatory bodies use archival nodes for forensic analysis and compliance. Key applications include:
- Transaction tracing for anti-money laundering (AML) investigations.
- Providing immutable audit trails for asset provenance and corporate actions.
- Reconstructing complete historical states to verify financial reports or smart contract execution.
03
Decentralized Application (dApp) Backends
Certain dApps, particularly in DeFi and gaming, require access to extensive historical data for their core logic. Examples include:
- On-chain reputation systems that calculate scores based on a user's entire transaction history.
- Historical price oracles that need to query precise asset prices from specific past blocks.
- Advanced analytics dashboards that provide users with personalized historical insights.
05
Research & Academic Study
Researchers and academics utilize archival nodes to conduct longitudinal studies on blockchain ecosystems. This enables analysis of:
- Network growth, adoption patterns, and economic activity over time.
- The long-term effects of protocol upgrades and governance decisions.
- Historical security incidents, their causes, and the network's resilience.
ARCHIVAL NODE
Frequently Asked Questions (FAQ)
Essential questions and answers about the role, operation, and importance of archival nodes in blockchain networks.
An archival node is a type of blockchain node that maintains a complete, unpruned copy of the entire blockchain history, including all historical states and transaction data. Unlike lighter nodes, it does not discard old data to save space. It works by synchronizing with the network from the genesis block, validating and storing every block, transaction, and the resulting state (e.g., account balances, smart contract storage) at every point in history. This requires significant storage (often multiple terabytes) and robust hardware. Archival nodes serve as the definitive source for querying any past on-chain event and are critical for services like block explorers, advanced analytics, and certain developer tools that require historical state access.
ENQUIRY
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.
NDA Protected
Confidentiality24h Response
Time to ValueDirectly to Engineering Team
No Sales Fluff10+
Protocols Shipped
$20M+
TVL Overall