3.1 KiB

Raw Blame History

Upgrade Your Node

This document describes the upgrade procedure of a gaiad full-node from a version <current_version> to a version <new_version>.

Software Upgrade

First, stop your instance of gaiad. Next, upgrade the software:

cd $GOPATH/src/github.com/cosmos/cosmos-sdk
git fetch --all && git checkout <new_version>
make tools install

::: tip NOTE: If you have issues at this step, please check that you have the latest stable version of GO installed. :::

See the testnet repo for details on which version is needed for which public testnet, and the SDK release page for details on each release.

Your full node has been cleanly upgraded!

Fetch new genesis

:::warning If the version <new_version> you are upgrading to is breaking from the previous one, you will have to restart your chain. If it is not breaking, you can skip to Restart :::

The procedure varies depending on the network you want to connect to.

Mainnet

Follow the official upgrade guide.

Public Testnet

If you are joining a new public testnet, fetch the genesis from the appropriate testnet in the testnet repo. Save the new genesis as new_genesis.json. Then replace the old genesis.json with new_genesis.json

cd $HOME/.gaiad/config
cp -f genesis.json new-_enesis.json
mv new_genesis.json genesis.json

Local Testnet

If you are running your own local testnet, you can either start with a brand new genesis using gaiad init, or export the state from you previous network as a new genesis. To do so, use the following command

cd $HOME/.gaiad/config
gaiad export --for-zero-height --height=<export-height> > new_genesis.json

Then, replace the old genesis.json with new_genesis.json.

cp -f genesis.json new-_enesis.json
mv new_genesis.json genesis.json

Reset Data

:::warning If the version <new_version> you are upgrading to is not breaking from the previous one, you should not reset the data. If it is not breaking, you can skip to Restart :::

::: warning If you are running a validator node on the mainnet, always be careful when doing gaiad unsafe-reset-all. You should never use this command if you are not switching chain-id. :::

::: danger Warning Make sure that every node has a unique priv_validator.json. Do not copy the priv_validator.json from an old node to multiple new nodes. Running two nodes with the same priv_validator.json will cause you to double sign. :::

First, remove the outdated files and reset the data. If you are running a validator node, make sure you understand what you are doing before resetting.

gaiad unsafe-reset-all

Your node is now in a pristine state while keeping the original priv_validator.json and config.toml. If you had any sentry nodes or full nodes setup before, your node will still try to connect to them, but may fail if they haven't also been upgraded.

Restart

To restart your node, just type:

gaiad start

3.1 KiB Raw Blame History