Skip to main content

Join the network

After your node is configured it need to sync the latest state and connect to the network. We support two ways of syncing your chain.

Get genesis file

Download the genesis.json file and copy it over to the config directory: ~/.kyve/config/genesis.json. This is a genesis file with the chain-id and genesis account balances.

Download the mainnet genesis file (5.2 MB)


verify the correctness of the genesis configuration via

echo "1dc3ec916f49ef8c221851566aca12a3f914b23afb3ab35067fc8a8d5f59c2ee  genesis.json" | sha256sum -c

and move the genesis file to the config directory

mv genesis.json ~/.kyve/config/

Syncing the network


We strongly recommend setting up Cosmovisor and Systemd as a supervisor.

State-Sync with KSYNC


Using KSYNC for state-syncing KYVE is only available for mainnet, if you wish to join Kaon or Korellia use traditional state-sync here.

Since KYVE has validated and archived all of its own state-sync snapshots on a 3,000 block interval those can be used to bootstrap your KYVE node. For this the node-syncing tool KSYNC can be used. To install KSYNC run the following:

go install

You can verify the installation with ksync version. To state-sync to the latest available snapshot run the following:


Please use the correct kyved binary version, you can find the correct version for each height here.

ksync state-sync --binary /path/to/kyved --chain-id kaon-1 --source kyve

After the state-sync snapshot has been applied you can normally continue syncing blocks over the P2P network.

Use traditional State-Sync

State sync fetches a snapshot of a recent height and then only syncs the missing blocks between the snapshot and the current height. This is the preferred method as it's much faster. Usually minutes versus weeks.

However, one needs to trust the provided state-sync nodes. If you need full trust you should sync from genesis.


Make sure to use the current version of the chain for statesync. All releases can be found here: Go to and look for the latest SoftwareUpgrade Proposal to find the current version.

First, one needs to obtain a trusted height and hash of that height. One can go to a blockexplorer and use the values provided there. For example block 86783 can be viewed at:

To enable state-sync edit config.toml under the section [statesync]

enable = true

# ...

rpc_servers = ","
trust_height = 86783 # Replace with newer block
trust_hash = "DFE6A7EC8D3E3A55A3CA6DA2D9BFB776A5F52604EBED078DAC87775AEA5C3D75" # Replace with newer hash

After that start the node with

./kyved start

Sync from genesis with KSYNC


Using KSYNC for syncing KYVE from genesis is only available for mainnet, if you wish to sync Kaon or Korellia use the normal P2P sync here.

Since KYVE has validated and archived all of its own blocks and block results they can be used to sync the node instead of fetching them from the P2P network. For this the node-syncing tool KSYNC can be used. To install KSYNC run the following:

go install

Since syncing the node from genesis can take weeks we strongly recommend setting up a systemd process which supervises the ksync process. Also since during the sync you will encounter multiple upgrades we also strongly recommend setting up Cosmovisor and preinstall all upgrade binaries. You can find information on setting up Cosmosvisor here and the systemd template below.

Create a file /etc/systemd/system/ksync.service with the following contents:


ExecStart=/<path-to-ksync>/ksync block-sync --binary <path-to-cosmovisor>/cosmovisor --chain-id kaon-1 --source=kyve -y


Make sure to replace <your-user>, <path-to-ksync>, <path-to-kyve> and <path-to-cosmovisor> with your values.

To start the process:

sudo systemctl enable ksync
sudo systemctl start ksync

It can be stopped using

sudo systemctl stop ksync

You can see its logs with

sudo journalctl -u ksync -f

Sync from genesis


For syncing from genesis you need chain binary version v1.0.0

After the genesis file is downloaded the chain binary can be started with

./kyved start