Cronos POS Chain Mainnet: Running a Full Node
Last updated
Last updated
This is detailed documentation for setting up a Full Node on the Cronos POS Chain mainnet. Note that while anyone can set up a full node, only the top 100 validators are considered "active" and eligible to receive rewards. See for more info.
For the host who would like to build a Run a Full Node with complete blockchain data from scratch, note that there were several breaking network upgrades, requiring upgrading at designated block heights below:
1 - 922,363
chain-main_1.2.1
Start the node with the older binary version
922,363 - 3,526,800
chain-main_2.0.1
When it reaches the target block height 922,363
(Canis Major), update the binary and restart
3,526,800 - 10,073,800
chain-main_3.3.9
When it reaches the target block height 3,526,800
(Draco II ), update the binary and restart*
>10,073,800
chain-main_4.2.2
When it reaches the target block height 10,073,800
(V4 upgrade ), update the binary and restart
*Note that as of v3.3.5
and higher, you need to modify your .chain-maind/config/app.toml
and set the following params:
index_events = []
iavl-cache-size = 781250
iavl-disable-fastnode = false
(set to true
to skip IAVL migration, but keep as false
when starting from a migrated snapshot. When you are on INF starting ABCI with Tendermint
for a while, migration is going on and you should NOT terminate this. It might take a couple of hours, so plan well ahead for this migration, as it may incur downtime.)
Users can refer to the upgrade guides of
"" (v1.*
to v2.0.1
);
(v2.*
to v3.3.9
);
(v3.3.9
to v4.2.2
); for the detailed upgrade steps.
We officially support macOS, Windows and Linux only. Other platforms may work, but there is no guarantee. We will extend our support to other platforms after we have stabilized our current architecture.
For Cronos POS Chain mainnet, you will need a machine with the following minimum requirements to run different types of nodes:
Archive Node (setting pruning = nothing)
RAM: 64GB (Rocksdb)
Disk: 3.4TB
CPU: 4 cores
Default Full Node (setting pruning = default)
RAM: 64GB (Rocksdb) or 16GB (goleveldb)
Disk: 1.2TB (From quick sync)
CPU: 4 cores
Pruned Node (setting pruning = everything)
RAM: 64GB (Rocksdb) or 16GB (goleveldb)
Disk: 40GB (From quick sync)
CPU: 4 cores
Please note that the size of snapshots from Quicksync will keep growing.
As mentioned before, in order to run a full node with complete blockchain data, we would need to begin with the older binary version 1.2.1
:
chain-maind
released binaries from GitHubTo install Cronos POS Chain binaries from Github:
You can verify the installation by checking the version of the chain-maind, the current version is 1.2.1
.
OR
chain-maind
by homebrewTo install binaries in Homebrew for macOS X or Linux
First, install the crypto-org-chain
tap, a repository of our Homebrew chain-maind
package:
Now, install the chain-maind
version 1.2.1
with crypto-org-chain/chain-maind
You can verify the installation by checking the version of the chain-maind
chain-maind
Before kick-starting your node, we will have to configure the node so that it connects to the Cronos POS mainnet
chain-maind
First of all, you can initialize chain-maind by:
This moniker
will be the displayed ID of your node when connected to the Cronos POS Chain network. When providing the moniker value, make sure you drop the square brackets since they are not needed.
Download and replace the Cronos POS Chain mainnet genesis.json
by:
Verify sha256sum checksum of the downloaded genesis.json
. You should see OK!
if the sha256sum checksum matches.
Once the chain-maind
has been configured, we are ready to start the node and sync the blockchain data:
Start chain-maind
, e.g.:
OR
(Optional for Linux) If you would like to have it running in the background, you can start chain-maind
with systemd
service, e.g.:
It should begin fetching blocks from the other peers. Please wait until it is synced to the upgrade height 922,363
before moving onto the next step.
chain-maind
binary to v2.1.2
At the upgrade height of 922,363
, users will see the following error message on the chain-maind
:
v2.1.2
binaryTerminate the chain-maind
; afterwards, download the v2.1.2
released binaries from github:
You can verify the installation by checking the version of chain-maind
, the latest version is 2.0.1
.
chain-maind
with version v2.1.2
We are ready to start the node join the network again with the new binary:
Start chain-maind
, e.g.:
You've successfully performed the new binary upgrade! Sit back and wait for the syncing process.
You can query the node syncing status by
If the above command returns false
, it means that your node is synced; otherwise, it returns true
and implies your node is still catching up.
You can check the current block height by querying the public full node by:
and you can check your node's progress (in terms of block height) by:
Remarks: The following is the minimal setup to join Cronos POS Chain Mainnet. Furthermore, you may want to run full nodes as sentries (see ), restrict your validator connections to only connect to your full nodes, use secure storage and service for your validator keys etc.
To simplify the following step, we will be using Linux for illustration. Binaries for and are also available. There are two options to install chain-maind
:
; or
is a free and open-source package management system for macOS X. Install the official Chain-maind formula from the terminal.
In ~/.chain-maind/config/app.toml
, update minimum gas price to avoid
Reminder:
The list of theseed
is subject to change, you can also find the latest seed to connect .
Important: When a validator is jailed because of a byzantine fault, their validator public key is added to a list of permanently banned validators and cannot re-join the network as a validator with the same public key, see
To simplify the following step, we will be using Linux for illustration. Binary for and are also available.
For users, simply run
You've successfully performed the "Canis Major" binary upgrade! Allow sometime for the node to catch up, meanwhile, you can get ready for "DRACO II," the second network upgrade ( from v2.*
to v3.3.2
at block height 3,526,800
) by following this , and "V4 Upgrade" (from v3.3.*
to v4.2.2
at block height 10,073,800
) by following this at a later stage. You can find the key details for all the upgrades under