# Cronos POS Chain Mainnet: Running a Full Node 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 [FAQs](https://github.com/crypto-org-chain/chain-main/discussions/442) for more info. ## Step 0: Notes on network upgrades 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: | Block height | Binary Version | Instruction | | ------------------------- | -------------------- | ------------------------------------------------------------------------------------------------ | | `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 - 22,649,500` | `chain-main_4.2.2` | When it reaches the target block height `10,073,800` (V4 upgrade), update the binary and restart | | `22,649,500 - 24,836,000` | `chain-main_v5.0.1` | When it reaches the target block height `22,649,500` (V5 upgrade), update the binary and restart | | `>24,836,000` | `chain-main_6.0.0-2` | When it reaches the target block height `24,836,000` (V6 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 for the detailed upgrade steps. * "[Canis Major](https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide/upgrade_guide)" (`v1.*` to `v2.0.1`); * ["DRACO II"](https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide/upgrade_guide_draco_2) (`v2.*` to `v3.3.9`); * ["V4 upgrade"](https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide/upgrade_guide_v4) (`v3.3.9` to `v4.2.2`); * [V5 upgrade](https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide/upgrade_guide_v4-1) (`v4.*` to `v5`); * [V6 upgrade](https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide/upgrade_guide_v4) (`v5.0.1` to `v6.0.0-2` ) ## Pre-requisites ### Supported OS 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. ### Prepare your machine 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: 5.9TB * CPU: 4 cores Default Full Node (setting pruning = default) * RAM: 64GB (Rocksdb) or 16GB (goleveldb) * Disk: 1.5TB (From Quicksync) * CPU: 4 cores Pruned Node (setting pruning = everything) * RAM: 64GB (Rocksdb) or 16GB (goleveldb) * Disk: 15GB (From Publicnode) * CPU: 4 cores *Please note that the size of snapshots from Quicksync will keep growing.* ## Step 1. Get the Cronos POS Chain Mainnet binary {% hint style="info" %} **Remarks**: The following is the minimal setup to join Cronos POS Chain Mainnet. Furthermore, you may want to run full nodes as sentries (see [Tendermint](https://docs.tendermint.com/v0.34/)), restrict your validator connections to only connect to your full nodes, use secure storage and [key management](https://docs.cronos-pos.org/for-users/wallets/cli#keys-management-chain-maind-keys) service for your validator keys etc. {% endhint %} To simplify the following step, we will be using **Linux** for illustration. Binaries for [Mac](https://github.com/crypto-org-chain/chain-main/releases/download/v1.2.1/chain-main_1.2.1_Darwin_x86_64.tar.gz) and [Windows](https://github.com/crypto-org-chain/chain-main/releases/download/v1.2.1/chain-main_1.2.1_Windows_x86_64.zip) are also available. There are two options to install `chain-maind`: * [Directly from Github](#option-1-install-chain-maind-released-binaries-from-github); or * [Homebrew](#option-2-install-chain-maind-by-homebrew) 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`: ### Option 1 - Install `chain-maind` released binaries from GitHub * To install Cronos POS Chain binaries from Github: ```bash $ curl -LOJ https://github.com/crypto-org-chain/chain-main/releases/download/v1.2.1/chain-main_1.2.1_Linux_x86_64.tar.gz $ tar -zxvf chain-main_1.2.1_Linux_x86_64.tar.gz ``` * You can verify the installation by checking the version of the chain-maind, the current version is `1.2.1`. ```bash # check the version of chain-maind $ ./chain-maind version 1.2.1 ``` **OR** ### Option 2 - Install `chain-maind` by homebrew {% hint style="info" %} **Reminder**: \ \- If you plan to play around with different networks (mainnet and testnet), we suggest you follow Option 1 to download the binary directly. \ \- The binary downloaded from homebrew is **only for interacting with the mainnet**. You cannot use it to interact with testnet. {% endhint %} To install binaries in Homebrew for macOS X or Linux [Homebrew](https://brew.sh/) is a free and open-source package management system for macOS X. Install the official Chain-maind formula from the terminal. * First, install the `crypto-org-chain` tap, a repository of our Homebrew `chain-maind` package: ```bash # tap the repo $ brew tap crypto-org-chain/chain-maind ``` * Now, install the `chain-maind` version `1.2.1` with crypto-org-chain/chain-maind ```bash # install the chain-maind CLI tool $ brew install chain-maind@1.2.1 ``` * You can verify the installation by checking the version of the `chain-maind` ```bash # check the version of chain-maind $ chain-maind version 1.2.1 ``` ## Step 2. Configure `chain-maind` Before kick-starting your node, we will have to configure the node so that it connects to the Cronos POS mainnet {% hint style="info" %} **Note**:\ \- Depending on your `chain-maind` home setting, the `chain-maind` configuration will be initialized to that home directory. To simplify the following steps, we will use the default chain-maind home directory `~/.chain-maind/` for illustration.\ \- You can also put the `chain-maind` to your binary path and run it directly by `chain-maind` {% endhint %} ### Step 2-1. Initialize `chain-maind` * First of all, you can initialize chain-maind by: ```bash $ ./chain-maind init [moniker] --chain-id crypto-org-chain-mainnet-1 ``` * 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. ### Step 2-2. Configure chain-maind * Download and replace the Cronos POS Chain mainnet `genesis.json` by: ```bash $ curl https://raw.githubusercontent.com/crypto-org-chain/mainnet/main/crypto-org-chain-mainnet-1/genesis.json > ~/.chain-maind/config/genesis.json ``` * Verify sha256sum checksum of the downloaded `genesis.json`. You should see `OK!` if the sha256sum checksum matches. ```bash $ if [[ $(sha256sum ~/.chain-maind/config/genesis.json | awk '{print $1}') = "d299dcfee6ae29ca280006eaa065799552b88b978e423f9ec3d8ab531873d882" ]]; then echo "OK"; else echo "MISMATCHED"; fi; OK! ```

Note:
For Mac environment, sha256sum was not installed by default. In this case, you may setup sha256sum with this command:

function sha256sum() { shasum -a 256 "$@" ; } && export -f sha256sum
* In `~/.chain-maind/config/app.toml`, update minimum gas price to avoid [transaction spamming](https://github.com/cosmos/cosmos-sdk/issues/4527) ```bash $ sed -i.bak -E 's#^(minimum-gas-prices[[:space:]]+=[[:space:]]+)""$#\1"0.025basecro"#' ~/.chain-maind/config/app.toml ``` {% hint style="info" %} **Reminder**: \ The list of the`seed`is subject to change, you can also find the latest seed to connect [here](https://github.com/crypto-org-chain/mainnet#seed-nodes). {% endhint %} {% hint style="warning" %} **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 [staking tombstone](https://docs.cosmos.network/master/modules/slashing/07_tombstone.html) {% endhint %} ## Step 3. Run everything ### Step 3-1. Run everything Once the `chain-maind` has been configured, we are ready to start the node and sync the blockchain data: * Start `chain-maind`, e.g.: ```bash $ ./chain-maind start ``` **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.: ```bash $ git clone https://github.com/crypto-org-chain/chain-main.git && cd chain-main $ ./networks/create-service.sh $ sudo systemctl start chain-maind # view log $ journalctl -u chain-maind -f ``` {% hint style="info" %} **Example**: /etc/systemd/system/chain-maind.service created by script ```bash # /etc/systemd/system/chain-maind.service [Unit] Description=Chain-maind ConditionPathExists=/usr/local/bin/chain-maind After=network.target [Service] Type=simple User=ubuntu WorkingDirectory=/usr/local/bin ExecStart=/usr/local/bin/chain-maind start --home /home/ubuntu/.chain-maind Restart=on-failure RestartSec=10 LimitNOFILE=50000 [Install] WantedBy=multi-user.target ``` {% endhint %} 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. {% hint style="info" %} **Remarks:** \ Option 2 - Install `chain-maind` by homebrew
To install binaries in Homebrew for macOS X or Linux * You can query the node syncing status by ```bash $ ./chain-maind status 2>&1 | jq '.SyncInfo.catching_up' ``` * 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. {% endhint %} ### Step 3-2. Upgrade the `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`: ```bash `ERR UPGRADE "v2.0.0" NEEDED at time: 2021-06-01T23:59:00Z:...` ``` #### Step 3-2-1 - Get the `v2.1.2` binary To simplify the following step, we will be using **Linux** for illustration. Binary for [Mac](https://github.com/crypto-org-chain/chain-main/releases/download/v2.1.2/chain-main_2.1.2_Darwin_x86_64.tar.gz) and [Windows](https://github.com/crypto-org-chain/chain-main/releases/download/v2.1.2/chain-main_2.1.2_Windows_x86_64.zip) are also available. * Terminate the `chain-maind`; afterwards, download the `v2.1.2` released binaries from github: ```bash $ curl -LOJ https://github.com/crypto-org-chain/chain-main/releases/download/v2.1.2/chain-main_2.1.2_Linux_x86_64.tar.gz $ tar -zxvf chain-main_2.1.2_Linux_x86_64.tar.gz ``` {% hint style="info" %} **Remarks:** \ If you have stated `chain-maind` with *systemd* service, kindly stop it by ```bash $ sudo systemctl stop chain-maind ``` And replace the binary in the location where the `ExecStart` states in Systemd Unit file. {% endhint %} * For [homebrew](https://github.com/crypto-org-chain/homebrew-chain-maind#chain-maind-homebrew-tap) users, simply run ```bash $ brew upgrade chain-maind ``` #### Step 3-2-2 - Verify the version You can verify the installation by checking the version of `chain-maind`, the latest version is `2.0.1`. ```bash # check the version of chain-maind $ ./chain-maind version 2.1.2 ``` #### Step 3-2-3 - Restart `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.: ```bash $ ./chain-maind start ``` You've successfully performed the new binary upgrade! Sit back and wait for the syncing process. * You can query the node syncing status by ```bash $ ./chain-maind status 2>&1 | jq '.SyncInfo.catching_up' ``` 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: ```bash curl -s https://rpc.mainnet.cronos-pos.org:443/commit | jq "{height: .result.signed_header.header.height}" ``` and you can check your node's progress (in terms of block height) by: ```` ```bash $ ./chain-maind status 2>&1 | jq '.SyncInfo.latest_block_height' ``` ```` ## "DRACO II" and "V4" Network upgrades 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 [guide](https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide/upgrade_guide_draco_2), and **"V4 Upgrade"** (from `v3.3.*` to `v4.2.2` at block height `10,073,800`) by following this [guide](https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide/upgrade_guide_v4-2) at a later stage. You can find the key details for all the upgrades under ["Notes on network upgrades"](https://docs.cronos-pos.org/for-node-hosts/getting-started/mainnet/upgrade-guide) ***