Skip to content

Latest commit

 

History

History
233 lines (143 loc) · 7.22 KB

README.md

File metadata and controls

233 lines (143 loc) · 7.22 KB
Raw

How to connect Cassini incentivised testnet network

For Metamask users :

Afterwards, kindly use the Cassini Faucet and obtain test cro token

How to build a full node connecting Cassini incentivised testnet network

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 Cassini 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 Cassini testnet binary

::: tip Remarks: 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 / M1)and Windows are also available.

  • To install released Cassini testnet binaries from github:

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

    Afterward, you can check the version of cronosd by

    $ ./cronosd version
0.5.5-testnet

Step 2. Configure cronosd

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

  • If you have joined other testnet 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 cassini_339-1

    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 cassini_339-1

NOTE

  • 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/cassini/main/cassini-network-info/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}') = "c84684ee99e7c47f68e1bc17b332d32d7d7b72dd4b747d82898905c4b887d3d8" ]]; 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 ~/.cronos/config/app.toml, update minimum gas price to avoid transaction spamming

    $ 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,[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

Step 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

::: tip Remarks: 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
$ ulimit -Sn [NEW_MAX_FILE_DESCRIPTOR]
# 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

:::details Example: /etc/systemd/system/cronosd.service created by script

# /etc/systemd/system/cronosd.service
[Unit]
Description=cronosd
ConditionPathExists=/usr/local/bin/cronosd
After=network.target

[Service]
Type=simple
User=ubuntu
WorkingDirectory=/usr/local/bin
ExecStart=/usr/local/bin/cronosd start --home /home/ubuntu/.cronos
Restart=on-failure
RestartSec=10
LimitNOFILE=4096

[Install]
WantedBy=multi-user.target

:::

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://cassini.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'