Regen Ledger Documentation

Upgrade Guide v4.0

This document provides guidelines for node operators upgrading from Regen Ledger v3.0 to v4.0. For a general overview of the upgrade process, please refer to Upgrade Overview.

Upgrade Info

Regen Ledger v4.0

Regen Mainnet

  • Upgrade Height: 6589400

Redwood Testnet

  • Upgrade Height: 4828000

Upgrade Guidelines

Update Go

Go 1.18 or later is required.

For available downloads, see Go Downloadsopen in new window.

Option 1: Using Cosmovisor

Cosmovisor v1.0 or later is required.

The following instructions assume the cosmovisor binary is already installed and cosmovisor is set up as a systemd service. If this is not the case, please refer to Using Cosmovisor for instructions on how to install and set up cosmovisor.

Auto-Download Not Recommended

Cosmovisor provides an auto-download option that prevents the need for the following steps in preparing for the upgrade. Although available to validators, this feature should only be used for non-validator nodes and validators should build the binary from source.

Build the upgrade binary (v4.0.1) from source:

cd regen-ledger
git fetch --tags
git checkout v4.0.1
make build

Ensure the regen binary has been built:

./build/regen version

You should see the following:

v4.0.1

Create a v4.0.0 directory and copy the upgrade binary (v4.0.1) to the directory:

mkdir -p $HOME/.regen/cosmovisor/upgrades/v4.0.0/bin
cp ./build/regen $HOME/.regen/cosmovisor/upgrades/v4.0.0/bin

Ensure the right regen binary has been placed in the directory:

$HOME/.regen/cosmovisor/upgrades/v4.0.0/bin/regen version

You should see the following:

v4.0.1

At the proposed block height, cosmovisor will automatically stop the current binary (v3.0.0), set the upgrade binary as the current binary (v4.0.1), and then (depending on the cosmovisor settings) perform a backup and restart the node.

Option 2: Without Cosmovisor

Using cosmovisor to perform the upgrade is not required. Node operators also have the option to manually update the regen binary at the time of the upgrade.

When the chain halts at the proposed upgrade height, stop the current process running regen.

Build the upgrade binary (v4.0.1) from source:

cd regen-ledger
git fetch --tags
git checkout v4.0.1
make install

Ensure the regen binary has been updated:

regen version

You should see the following:

v4.0.1

Restart the process running regen.