Skip to main content

Running a node

This document explains the main steps to configure a node to join an existing network, and make it validator.


The steps detailed here are to be adjusted depending on the network you're joining.

⚙️ Init

Joining a network require at least 3 elements:

  • The network's chain-id.
  • The network's Genesis.
  • Some network's peers.

As a prerequisite, the okp4d binary shall be installed, please find the instructions here.

Chain ID

A network is identified by its chain id, when initializing a node's configuration it is recommended to provide it so the client.toml configuration will be properly set, this will ease CLI commands.


The chain-id values for each networks are detailed in the corresponding sections (i.e. Join Testnet & Join Mainnet).

Choose a moniker

The moniker helps identifying your node on the explorer interfaces, this is more human readable than a node ID.


Initialize the node

At this point, the node can be initialized:

okp4d init $MONIKER --chain-id $CHAIN_ID

This will generate, in the $HOME/.okp4d folder, the following files:

  • config/app.toml: Application-related configuration file.
  • config/client.toml: Client-oriented configuration file (not used when running a node).
  • config/config.toml: Tendermint-related configuration file.
  • config/genesis.json: The network's genesis file.
  • config/node_key.json: Private key to use for node authentication in the p2p protocol.
  • config/priv_validator_key: Private key to use as a validator in the consensus protocol.
  • data: The node's database.

The generated config/priv_validator_key and config/node_key.json are very sensible, if stolen the entire stake delegated to the validator is at risk. ➡️ See the Security section.

Set Genesis

Inside the network all the nodes share the same chain configuration and state, the genesis file providing the configuration and the base state all the nodes shall share it.

The config/genesis.json file shall be replaced with the one corresponding to the targeted network (i.e. Join Testnet & Join Mainnet).

Add peers

Joining a network is first of all being part of the P2P protocol. To do so your node must connect with others by specifying persistent peers, either in the config/config.toml, or through the p2p.persistent_peers argument of the start command. Depending on the chosen network, refer to its section to find peers (i.e. Join Testnet & Join Mainnet).

🚀 Run

Let's invoke the start command:

okp4d start

Running a validator node being critical, consider automate upgrades and secure your node.

Syncing the node

Your node will start beginning by syncing to the network, this step can take a long time depending on the blockchain size, you can query the sync status with the following command:

# Query via the RPC (default port: 26657)
curl http://localhost:26657/status | jq .result.sync_info.catching_up

During the sync process the node will apply each block on its state, you'll need to install binary upgrades at the correct heights (i.e. only on breaking upgrade cases) in order to sync your node. Please refer to your targeted network upgrades history (i.e. Join Testnet & Join Mainnet).

👨‍⚖️ Becoming validator


Your node shall be fully synced before upgrading it to a validator. It can't take part in the validation consensus without sharing the same state than the others, and risk thus to be slashed and jailed.

To make your node validator you need to submit a create-validator transaction referencing it by its public key:

PUB_KEY=$(okp4d tendermint show-validator)
okp4d tx staking create-validator \
--amount 1000000uknow \
--commission-max-change-rate "0.1" \
--commission-max-rate "0.20" \
--commission-rate "0.1" \
--min-self-delegation "1" \
--details "Don't stop me KNOW" \
--pubkey=$PUB_KEY \
--moniker "$MONIKER_NAME" \
--chain-id $CHAIN_ID \
--gas-prices 0.025uknow \
--from <key-name>

This is an example transaction, to customize your validator explore the available flags:

okp4d tx staking create-validator --help