Archive Node Configuration
Archive nodes in the Core network play a crucial role in maintaining the complete historical state of the network. These nodes are specialized versions of full nodes with enhanced capabilities tailored to storing and providing access to the entire history of all transactions and states since the inception of the Core Chain.
System Requirements​
There are several system requirements, both software and hardware, for setting up a Archive node on the Core network.
Software​
- Currently, a Core archive node can only run on Mac OS X or on the Linux operating systems.
Hardware​
Core nodes perform several resource-intensive tasks, which can include storing blockchain data, verifying blocks or transactions, communicating with peer nodes, and answering network requests, depending on their configuration. Each type of Core node has specific hardware requirements based on their expected needs.
Testnet Archive Node Hardware Specifications​
For Archive Nodes on Core Blockchain Testnet, we recommend the following minimal hardware specs:
| Requirements | Details |
|---|---|
| Storage | Solid State Drive (SSD) with a minimum capacity of 4TB |
| CPU | 8 Core CPU |
| RAM | 32 Gigabytes |
| Internet Speed | A broadband Internet connection with upload/download speeds of 5Mbps |
Mainnet Archive Node Hardware Specifications​
For Archive Nodes on Core Blockchain Mainnet, we recommend the following minimal hardware specs:
| Requirements | Details |
|---|---|
| Storage | Solid State Drive (SSD) with a minimum capacity of 4TB |
| CPU | 8 Core CPU |
| RAM | 32 Gigabytes |
| Internet Speed | A broadband Internet connection with upload/download speeds of 5Mbps |
Running Core Archive Node​
1. We recommend using the core-chain GitHub repository to directly build and run your full node, running your full node directly from our blockchain codebase. Instructions for building the source code can be found in the repository's README.
2. Download the latest node binary for from Core Chain GitHub releases repo and the latest snapshot for archive node from Core's Snapshot Repository. The node binary includes the relevant mainnet and testnet configuration files.
3. Write the genesis state locally by executing the following command from your project directory:
geth --datadir node init genesis.json
4. Our full/archive node is ready, let's start running it! You can just run the following geth command directly:
## start an archive node
geth --config ./config.toml --datadir ./node --cache 8000 --gcmode=archive --syncmode=full
5. As our archive node runs, we can monitor its logs to make sure that everything is operating correctly. The log file is located at ./node/logs/core.log by default, but can be changed to another location if desired.