Setup a node (mainnet / public testnet)


1 core machine with 2 GB RAM, running Linux or Mac, with Docker and Docker Compose (version >= 1.28) installed.
At least 100 GB storage for chain data. (Estimated storage requirement: 40 GB per year)
Please make sure that your TCP port 26656 is connectable from external network.

Setup steps

  1. 4.
    Start up the node and wait for synchronization catch up

Clone the project

Run git clone --branch fotan-1.1 --single-branch, then cd likecoin-chain.

Build the Docker image

Run ./

Initialize the node and account keys

cp docker-compose.yml.template docker-compose.yml cp .env.template .env
for setting up the docker-compose.yml and .env.
Modify .env file for the network config.
For mainnet:
LIKECOIN_MONIKER="<change this for your node's name>" LIKECOIN_DOCKER_IMAGE="likecoin/likecoin-chain:fotan-1.1" LIKECOIN_CHAIN_ID="likecoin-mainnet-2" LIKECOIN_GENESIS_URL="" LIKECOIN_SEED_NODES="[email protected]:26656,[email protected]:26656"
For testnet:
LIKECOIN_MONIKER="<change this for your node's name>" LIKECOIN_DOCKER_IMAGE="likecoin/likecoin-chain:fotan-1.1" LIKECOIN_CHAIN_ID="likecoin-public-testnet-3" LIKECOIN_GENESIS_URL="" LIKECOIN_SEED_NODES="[email protected]:31801"
Note that LIKECOIN_MONIKER is a custom name you decide for your node's name.
Run docker-compose run --rm init to create .liked directories, with node config and keys initialized.
Run docker-compose run --rm liked-command keys add validator to add an operator key. The command will output your operator address, and also a 12-24 words mnemonic phrase. Please backup the mnemonic phrase properly as it represents your validator's private key.
When asked, enter and repeat a passphrase for protecting your account key.

Start up the node

Run docker-compose up -d. This will create and run the Docker containers in background.
To see if the node is running well, you can input docker-compose logs to see if there is any error.
The node will connect to the network and start to synchronize blocks, which may take some time depends on how long the network is started. Using state sync described below to quickly catch up with latest blocks.
You can check the synchronization progress at http://{YOUR_NODES_IP}:26657/status. result.sync_info.catching_up will be false if the node has already caught up the network's blocks.

State Sync

For state sync to work, we would need to configure a trusted block height and hash in config.toml.
To enable state sync, modify the [statesync] session of config.yaml as below, using example height 225500 . You should modify the config according to latest block height. The RPC servers, are used here, but any two trusted RPC servers can also be used.
enable = true
rpc_servers = ","
trust_height = 225500
trust_hash = "10737475ED545C9BE1A48E1F99BD8D2941E7E286EDB71FC1B9E15E27032144DB"
trust_period = "168h0m0s"

Becoming a validator

For a validator node, you will need a node synchronized, which you may setup following the steps above.
You also need some LikeCoin in your operator address.
Then you can use the following command to create a validator, turning your node into a validator node:
docker-compose run --rm create-validator \ --amount <AMOUNT> \ --details <DETAILS> \ --commission-rate <COMMISSION_RATE>
Modify the parameters:
  • <AMOUNT>: the amount to self-delegate on the validator at the beginning (e.g. 90000000000000nanoekil).
  • <DETAILS>: the detailed description of the validator. Remember to quote it using ".:
  • <COMMISSION_RATE>: the validator's commission rate, which could be seen as the "tax" received by the validator from delegators, e.g. 0.5 (50%).
Optionally, you may add the following additional parameters:
  • --identity <IDENTITY>: a string representing the identity of the validator, usually the GPG fingerprint. Some block explorers (e.g. Big Dipper) will query this field and search Keybase for the user profile.
  • --website <WEBSITE>: the website of the validator.
After signing and sending the transaction, your node should turn into a validator node. You may check by viewing .liked/data/priv_validator_state.json, the height value will change to non-zero if the node is validating blocks.
Last modified 2mo ago