# Cronos Testnet: Running Nodes

The latest Crypto.org Chain Testnet has been named as Cronos.

This is a detailed documentation for setting up a Validator or a full node on Crypto.org Cronos testnet cronostestnet_338-3.

# 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

  • To run Cronos testnet nodes, you will need a machine with the following minimum requirements:

    • 4-core, x86_64 architecture processor;
    • 16 GB RAM;
    • 1 TB of storage space.

# Step 1. Get the Cronos testnet binary


The following is the minimal setup for a validator node / full node.

To simplify the following step, we will be using Linux (Intel x86) for illustration. Binary for Mac (Intel x86 (opens new window) / M1 (opens new window))and Windows (opens new window) are also available.

  • To install released Cronos testnet binaries from github:

    $ curl -LOJ https://github.com/crypto-org-chain/cronos/releases/download/v0.6.0-testnet/cronos_0.6.0-testnet_Linux_x86_64.tar.gz
    $ tar -zxvf cronos_0.6.0-testnet_Linux_x86_64.tar.gz

    Afterward, you can check the version of cronosd by

    $ ./cronosd version

# Step 2. Configure cronosd

# Step 2-0 (Optional) Clean up the old blockchain data

  • If you have joined cronostestnet_338-2 before, you would have to clean up the old blockchain data and start over again, it can be done by running:

    $ ./cronosd unsafe-reset-all

    and remove the old genesis file by

    $ rm ~/.cronos/config/genesis.json

Before kick-starting your node, we will have to configure your node so that it connects to the Cronos testnet:

# Step 2-1 Initialize cronosd

  • First of all, you can initialize cronosd by:

      $ ./cronosd init [moniker] --chain-id cronostestnet_338-3

    This moniker will be the displayed id of your node when connected to Crypto.org Chain network. When providing the moniker value, make sure you drop the square brackets since they are not needed. The example below shows how to initialize a node named pegasus-node :

      $ ./cronosd init pegasus-node --chain-id cronostestnet_338-3


    • Depending on your cronosd home setting, the cronosd configuration will be initialized to that home directory. To simply the following steps, we will use the default cronosd home directory ~/.cronos/ for illustration.
    • You can also put the cronosd to your binary path and run it by cronosd

# Step 2-2 Configure cronosd

  • Download and replace the Cronos Testnet genesis.json by:

    $ curl https://raw.githubusercontent.com/crypto-org-chain/cronos-testnets/main/cronostestnet_338-3/genesis.json > ~/.cronos/config/genesis.json
  • Verify sha256sum checksum of the downloaded genesis.json. You should see OK! if the sha256sum checksum matches.

    $ if [[ $(sha256sum ~/.cronos/config/genesis.json | awk '{print $1}') = "7d898ad75b3e2e1fa182d928ca10a284c1dd252e12d17ad6dab76551b29d1a59" ]]; then echo "OK"; else echo "MISMATCHED"; fi;


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

      function sha256sum() { shasum -a 256 "[email protected]" ; } && export -f sha256sum
  • In ~/.cronos/config/app.toml, update minimum gas price to avoid transaction spamming (opens new window)

    $ sed -i.bak -E 's#^(minimum-gas-prices[[:space:]]+=[[:space:]]+).*$#\1"5000000000000basetcro"#' ~/.cronos/config/app.toml
  • For network configuration, in ~/.cronos/config/config.toml, please modify the configurations of persistent_peers, create_empty_blocks_interval and timeout_commit by:

    $ sed -i.bak -E 's#^(persistent_peers[[:space:]]+=[[:space:]]+).*$#\1"[email protected]:26656,[email protected]:26656"#' ~/.cronos/config/config.toml
    $ sed -i.bak -E 's#^(create_empty_blocks_interval[[:space:]]+=[[:space:]]+).*$#\1"5s"#' ~/.cronos/config/config.toml
    $ sed -i.bak -E 's#^(timeout_commit[[:space:]]+=[[:space:]]+).*$#\1"5s"#' ~/.cronos/config/config.toml


  • For Mac environment, if jq is missing, you may install it by: brew install jq

# Step 3. Run everything


This page only shows the minimal setup for validator / full node.

Furthermore, you may want to run full nodes as sentries (see Tendermint (opens new window)), restrict your validator connections to only connect to your full nodes, test secure storage of validator keys etc.

# Step 3-1. Create a new key and address

Run the followings to create a new key. For example, you can create a key with the name Default by:

  $ ./cronosd keys add Default

You should obtain an address with tcrc prefix, e.g. tcrc10u5mgfflasrfj9s94mt8l9yucrt2gzhcyt5tsg. This will be the address for performing transactions.

# Step 3-2. Obtain test token

Users can use the faucet (opens new window) to obtain test tokens, please note that you would need a Ethereum type address 0x... that can be obtained by

In case you have reached the daily limit on faucet , you can simply send a message on Discord (opens new window) #request-tcro channel , stating who you are and your 0x... address.

# Step 3-3. Run everything

Once the cronosd has been configured, we are ready to start the node and sync the blockchain data:

  • Start cronosd, e.g.:
  $ ./cronosd start


If you see errors saying too many files opened..., then you need to set a higher number for maximum open file descriptors in your OS.

If you are on OSX or Linux, then the following could be useful:

# Check current max fd
$ ulimit -n
# Set a new max fd
# Example
$ ulimit -Sn 4096
  • (Optional for Linux) Start cronosd with systemd service, e.g.:
  $ curl -s https://raw.githubusercontent.com/crypto-org-chain/cronos-docs/master/systemd/create-service.sh -o create-service.sh && curl -s https://raw.githubusercontent.com/crypto-org-chain/cronos-docs/master/systemd/cronosd.service.template -o cronosd.service.template
  $ chmod +x ./create-service.sh && ./create-service.sh
  $ sudo systemctl start cronosd
  # view log
  $ journalctl -u cronosd -f
Example: /etc/systemd/system/cronosd.service created by script
# /etc/systemd/system/cronosd.service

ExecStart=/usr/local/bin/cronosd start --home /home/ubuntu/.cronos


It should begin fetching blocks from the other peers. Please wait until it is fully synced before moving onto the next step.

  • You can query the node syncing status by

    $ ./cronosd status 2>&1 | jq '.SyncInfo.catching_up'

    If the above command returns false, It means that your node is fully synced; otherwise, it returns true and implies your node is still catching up.

  • One can check the current block height by querying the public full node by:

    curl -s https://cronos-testnet-3.crypto.org:26657/commit | jq "{height: .result.signed_header.header.height}"

    and you can check your node's progress (in terms of block height) by

    $ ./cronosd status 2>&1 | jq '.SyncInfo.latest_block_height'

The next step only applied to the validators, in which, validator hosting is by invitation only at the early stage of the Cronos testnet.

# Step 3-4. Obtain the validator public key

You can obtain your validator public key by:

  $ ./cronosd tendermint show-validator

The public key should in a json format, for example:

  "@type": "/cosmos.crypto.ed25519.PubKey",
  "key": "gvPPVShkWjuUn7cuqS3ci9fHnC+nLFxzsNWkwGJ6iMI="

# Step 3-5. Send a create-validator transaction

Once the node is fully synced, we are now ready to send a create-validator transaction and join the network, for example:

$ ./cronosd tx staking create-validator \
--from=[name_of_your_key] \
--amount=10000000stake \
--pubkey='{"@type":"/cosmos.crypto.ed25519.PubKey","key":"PUBLIC_KEY"}'  \
--moniker="[The_id_of_your_node]" \
--security-contact="[security contact email/contact method]" \
--chain-id="cronostestnet_338-3" \
--commission-rate="0.10" \
--commission-max-rate="0.20" \
--commission-max-change-rate="0.01" \
--min-self-delegation="1" \

confirm transaction before signing and broadcasting [y/N]: y

You will be required to insert the following:

  • --from: The tcrc... address that holds your stake token;
  • --pubkey: The validator public key( See Step 3-4 above )
  • --moniker: A moniker (name) for your validator node;
  • --security-contact: Security contact email/contact method.

# Step 3-6. Check your validator status

Once the create-validator transaction completes, you can check if your validator has been added to the validator set:

$ ./cronosd tendermint show-validator
## [{"@type":"/cosmos.crypto.ed25519.PubKey","key":"VALIDATOR_KEY"}] ##
$ ./cronosd query tendermint-validator-set | grep -c [VALIDATOR_KEY]

## 1 = Yes; 0 = Not yet added ##

To further check if the validator is signing blocks, kindly run this script (opens new window), for example:

$ curl -sSL https://raw.githubusercontent.com/crypto-com/chain-docs/master/docs/getting-started/assets/signature_checking/check-validator-up.sh | bash -s -- \
--tendermint-url https://cronos-testnet-3.crypto.org:26657 \
--pubkey $(cat ~/.cronos/config/priv_validator_key.json | jq -r '.pub_key.value')

The validator is in the active validator set under the address  <YOUR_VALIDATOR_ADDRESS>
The validator is signing @ Block#<BLOCK_HEIGHT> 👍

# Step 4. Perform Transactions

# Step 4-1. query bank balances - Check your transferable balance

You can check your transferable balance with the balances command under the bank module.

Example: Check your address balance
$ ./cronosd query bank balances tcrc1qsklxwt77qrxur494uvw07zjynu03dq9alwh37

- amount: "10005471622381693"
  denom: basetcro
  next_key: null
  total: "0"

# tx slashing unjail - Unjail a validator

Validator could be punished and jailed due to network misbehaviour, we can check the jailing status of a validator, for example:

$ ./cronosd query staking validators -o json | jq
      "operator_address": "tcrcvaloper1hhskvvt87ngxjgl4fkcrn3ts09u63pnh47t06u",
      "consensus_pubkey": {
        "@type": "/cosmos.crypto.ed25519.PubKey",
        "key": "rXphE0lECaU4MfBL70l6tGrfaply4dp79g7ql4ijfco="
      "jailed": false,

Where "jailed": true implies that the validator has been jailed. After the jailing period has passed, one can broadcast a unjail transaction to unjail the validator and resume its normal operations by

$ ./cronosd tx slashing unjail --from [key_name] --chain-id "cronostestnet_338-3" --fees=1000000000000000000basetcro

  confirm transaction before signing and broadcasting [y/N]: y


Congratulations! You've successfully set up a Testnet node and performed some basic transactions! You may refer to Wallet Management (opens new window) for more advanced operations and transactions.

# Cronos testnet faucet and explorer