# Running a Chain-Node
The Chain-Nodes are the backbone of KYVE. The chain layer is a completely sovereign Proof of Stake (opens new window) blockchain build with Ignite (opens new window). This blockchain is run by independent nodes we call Chain-Nodes since they're running on the chain level. The native currency of the KYVE chain is $KYVE, it secures the chain and allows chain nodes to stake and other users to delegate into them.
- 2GB RAM (plus 8GB SWAP during chain-upgrades)
- 150GB DISK
The disk requirements will keep on expanding over time: the 150GB figure was valid on May 7th 2022 but it will not stay that way forever. Consider giving 2 to 3 times that amount in order to avoid having to resize your volumes too quickly.
# Genesis Installation
IMPORTANT: This guide assumes a GNU/Linux amd64 system.
During the time, chain-upgrades occur but the blockchains stays the same. Therefore, it is necessary to process older blocks with the appropriate version. We use Cosmovisor to handle automatic upgrades. The setup is explained after the initial setup.
In the genesis setup the node will be fully configured. After that one needs to configure the Cosmovisor.
# Obtaining the binaries
Obtain the genesis
It is important to start with the oldest version
v0.0.1 (the genesis version).
Start the chain the first time:
The node should now be starting to sync the chain. If it doesn't, you can always look
for other peers here (opens new window) and use it with
p2p.persistent_peers param, for example:
The node can be stopped with
ctrl + c. You do not need to wait for it to sync. Setting up a daemon service is explained later in this chapter.
The seed only needs to be provided for the first startup. It is then automatically saved to the address book.
The chain will start to sync until the first governance upgrade proposal starts to occur. The Chain-Node will halt and probably print a "CONSENSUS FAILURE" error. When this happens the next released binary needs to be started.
To avoid replacing the binaries manually and allow automatic updates we recommend setting up the Cosmovisor.
# Setup Cosmovisor
The Cosmovisor is a tool that listens to on-chain governance proposals and automatically replaces the binary.
Setup the directory
Copy the binary from the first section to the Cosmovisor directory.
Then export the following environment variables:
IMPORTANT: For production grade validator nodes it is highly recommended turning off auto download and downloading binaries manually instead.
Cosmovisor can be stopped with
strg + C. Setting up a daemon service is explained later in this chapter.
# Obtaining binaries manually
This is needed when
DAEMON_ALLOW_DOWNLOAD_BINARIES is set to
When a new chain-upgrade proposal occurs, users have multiple days time to vote on it. The upgrade-proposal specifies an exact block-height on which the upgrade will be performed. When the proposal is up for vote the GitHub repository is already updated with the new tag and version.
Node-runners then have to check out the specific tag and build the binary on their on. After that the binary needs to be copied to the Cosmovisor directory.
$UPGRADE_NAME will be the name of the tag of the commit. And is also specified in the governance proposal.
# Setting up Deamon-service
For the daemon service root-privileges are required during the setup.
Create a service file. $USER is the Linux user which runs the process. Replace it before you copy the command
Start the daemon
It can be stopped using
You can see its logs with
# Becoming a validator
To become a validator you need $KYVE. There are currently 100 validator slots, if all slots are taken you need to stake more than the lowest one in the list to take its place.
Make sure your node is fully synced and configured correctly.
Create a key or import an existing one
Make sure you have enough balance in your wallet.
Become a validator by submitting the
create-validator transaction to the network.
You need to substitute
Learn your valoper address
Delegate additional stake