Snapshot Node Configuration
Snapshots are important for a network to ensure nodes are able to sync up to the latest state of the network as quickly as possible. Before nodes can be used, they must sync up to the current state of the network, by starting from a recent snapshot these nodes can fast-track a majority of the syncing.
System Requirementsโ
There are several system requirements, both software and hardware, for setting up a snapshot node on the Core network.
Softwareโ
- Currently, a Core Snapshot Node can only run on Mac OS X or on the Linux operating systems.
Hardwareโ
On the Core network, Snapshot nodes act also as the archive nodes, storing the enitre blockchain data.
Testnet Snapshot Node Hardware Specificationsโ
For Snapshot 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 | 4 CPU cores |
RAM | 16 Gigabytes |
Internet Speed | A broadband Internet connection with upload/download speeds of 5Mbps |
Mainnet Snapshot Node Hardware Specificationsโ
For Sanpshot 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 | 4 CPU cores |
RAM | 16 Gigabytes |
Internet Speed | A broadband Internet connection with upload/download speeds of 5Mbps |
Core Chain Snapshotsโ
You can get the latest snapshots from here.
Syncing Nodes Using Snapshots on Core Chain Networkโ
On Core Chain network, you can sync your node to the latest state by several ways. In this document, we guide you through the syncing process of nodes on the Core network using the snapshots.
Download Pre-Build Binariesโ
Download the pre-build binaries from the release page or follow the instructions below
Linuxโ
wget $(curl -s https://github.com/coredao-org/core-chain/releases/latest |grep browser_ |grep geth_linux |cut -d\" -f4)
mv geth_linux geth
chmod -v u+x geth
MacOSโ
wget $(curl -s https://github.com/coredao-org/core-chain/releases/latest |grep browser_ |grep geth_mac |cut -d\" -f4)
mv geth_mac geth
chmod -v u+x geth
Download the config filesโ
Download genesis.json and config.toml by:
wget $(curl -s https://github.com/coredao-org/core-chain/releases/latest |grep browser_ |grep mainnet |cut -d\" -f4)
unzip mainnet.zip
Peers Configurationโ
- Mainnet: the config.toml file from the latest release ships configured with the information about the
Bootstrap Nodes
andStatic Nodes
as shown below:
BootstrapNodes =
["enode://6334cdde2728b17486e4930c29e85128694faf118c23f559c7502e1cb42dd90a54f785c80c6a493d7d6f5ed23f3c9cf75e0392b024e45f7eadc81a84544a45ff@seed4.coredao.org:0?discport=35022",
"enode://20b605d5ee978c22bfb9ed208a40f2876d3dfafb1c60a6427c4db28e516520ee610cbc2a1c0ee05dd08578a041dc9070d92cf888422ed0869d0666b5103292b4@seed2.coredao.org:0?discport=35022",
"enode://04ffc724b82e2c52df47e2439a30ca4c0f7aca5ce270f6c6bcdf539581ce2ae4965afd5c5fe19106cd528ed6f379c68687a41310054ee751a73880b2c73e85d8@seed3.coredao.org:0?discport=35022",
"enode://e9a218f70debcb6a423d68f287c972c717606a70bfed278c2f7a876493d37bc535b05127abddeeca21941fc61497a6ca13387466c75a070050862ca6da11b0ca@seed1.coredao.org:0?discport=35022"]
StaticNodes =
["enode://8c60a7445dfff047051aa686d621e8ff3fad4623ebd60aea3b8a9b5285945ff0bb05540cc215bcb0ae3fb07b6c368605ddeebeb23b282ffb2ae777d8a73155ec@18.230.84.232:35021",
"enode://af5bb3eb4278885d98dfdb994a283cd1eafec7f3cf53b13325a484a71e02613a2d724314a2d5bf2ea3b33adb0d1ad7d1c5b9e23c8d2959453a55bde5f02c762f@35.72.191.164:35021",
"enode://40811f3281241c68555179e40654971ec01b1849899e296c0852e5dfed70f3d17f776e90dced50e94cc71699e2b010eec58047ce91d07fa7a3520220cf3ce22b@13.39.140.139:35021",
"enode://ee253be3c7c2ccdd4611d16975733ceb2f41f61a04672756fa4850a0b85419ca5e07ceb5a6f1ac43318b136c8995b9160e6de0c6b4bc2c9325797c11275888e6@18.221.135.3:35021",
"enode://71f4b875a8cec01fe9f01974a682ef846ab8cbe0c23518b2a94e38eef0db829488502122b19c94d595521364bc4550639b58c0332d3942447dfd65707fc80bc0@13.214.98.126:35021"]
Download snapshotโ
Download latest chaindata snapshot from here.
Start the Nodeโ
./geth --config ./config.toml --datadir ./node --cache 8000 --rpc.allow-unprotected-txs --txlookuplimit 0
Make sure you use the version of geth you downloaded with wget above, and not your local installation of geth, which might be the wrong version.
It is recommended to run a fast node, which is a full node with the flag --tries-verify-mode none set if you want high performance and care little about state consistency.
./geth --config ./config.toml --datadir ./node --cache 8000 --rpc.allow-unprotected-txs --txlookuplimit 0 --tries-verify-mode none
Monitor node statusโ
You can monitor the logs for node status. By default the logs are stored at ./node/logs/core.log
.
Sync Modeโ
There are two sync modes for running a full node: snap and full which can be specified by flag --syncmode.
-
The snap sync mode is used for initial sync, which will download the latest states rather than execute the blocks from the genesis. When the initial sync is done, it will switch to full sync automatically.
-
The full sync mode can also be used to do initial sync, which will execute all the blocks since genesis. But it is not recommended, since the amount of historical data is too large. Instead, you can download a snapshot from the official repo and start full sync from the snapshot.
-
If the flag --syncmode is not provided, the default sync mode will depend on the state of the data folder. It will be snap mode if you sync from genesis or full mode if you start from a snapshot. 2