Unlocking the potential of the Ethereum network, a node serves as a robust computer running Ethereum client software, intricately linked to fellow nodes within the network. Collaboratively, these nodes engage in the crucial task of verifying transactions and upholding the shared blockchain database, commonly known as a ledger. Diverse nodes and client software programs exist, each offering unique features and functionalities that we'll explore shortly.
Key insights into Full and Archive nodes on Ethereum:
Full Node: Storing and meticulously managing recent block data (e.g., the last 128 blocks) on disk, a Full Node responds to requests by providing blockchain data. It actively contributes to network support through block validation and comprehensive verification of all blocks and states. A Full node becomes the source from which all states can be derived.
Archive Node: Possessing the capabilities of Full nodes, an Archive Node goes further by compiling an archive of historical states. Valuable for accessing historical blockchain data beyond the reach of Full nodes, Archive nodes, unlike their counterparts, are not obliged to partake in block validation. Moreover, they can be constructed from scratch using a Full node.
What is an Ethereum Full Node? In Ethereum's PoW consensus mechanism, a Full node was characterized by a single client software. In the evolved state of Ethereum (ETH2 with Proof-of-Stake), a Full node comprises two distinct client software components—one for the consensus layer and another for the execution layer. These collaborative clients verify Ethereum's state and relay information to incoming JSON RPC requests and consensus layer validators.
Recommended hardware requirements for a Full node:
- Fast CPU with 4+ cores. High Ghz/Core is important, starting at 3.5 Ghz and more
- 16 GB RAM minimum requirement, 32GB is recommended
- SSD drive with a 1TB+ disk space. As the amount of data capacity varies, a 2TB SSD drive is recommended to avoid disk space upgrades in the future.
- 1Gbps internet speed with 30 - 40TB data transfer included.
What is an Ethereum Archive Node? Mirroring Full node capabilities, an Archive Node goes further by curating an archive of historical states. This node proves indispensable for querying historical blockchain data beyond the last 128 blocks. Archive nodes, distinctively, are not obligated to engage in block validation and can theoretically be constructed from the ground up by replaying blocks from the genesis.
The storage demand for running an Archive node is elevated due to storing historical states. Running an Archive node necessitates around ~12 TB on Geth and ~2 TB on Erigon (subject to growth). It's essential to note that the database size and synchronization speed are client-specific and vary with configurations.
Recommended hardware requirements for a Full Archive node:
- Fast CPU with 4+ cores. High Ghz/Core is important, starting at 3.5 Ghz and more
- 16 GB RAM minimum requirement, 32GB is recommended
- Storage requirements depend on the client software ( Geth consumes ~15+ TB, while Erigon requires more than 2TB disk space). SSD disk space is recommended, as HDD does not provide the required performance.
- 1Gbps internet speed with 30 - 40TB data transfer included.