Mainnet Upgrades

Details of mainnet upgrades, installation block height and links to instructions.

Release procedures for validators and node operators are explained here. The RELEASES.md file in UnUniFi's GitHub repo is the canonical source of truth for release processes.

The UnUniFi Network mainnet is regularly upgraded to provide the latest security patches, Cosmos SDK module integrations and performance improvements.

Some upgrades are able to be undertaken automatically with Cosmovisor while other upgrades need to be manually installed at specified block heights. Others can be installed at any time after their predecessor.

Upgrade types

There are two types of upgrades that happen on UnUniFi Network. They are:

1. Planned feature upgrades or planned patches

2. Unplanned security upgrades.

Planned upgrade (via governance)

Planned upgrades, as the name suggests, are upgrades that are developed and proposed via governance. If approved by the community, these upgrades are undertaken by the chain automatically halting at the planned upgrade height.

Node operators are then required to swap the binary for the planned upgrade binary. After all node operators have upgraded and started their nodes the network will continue in the upgraded state.

Unplanned upgrade

Where emergency security patches are required, node operators are notified via the official discord validator channels. Node operators will be required to halt their nodes manually at the required upgrade height, swap the patched binary and restart their nodes. After all node operators have upgraded and started their nodes the network will continue in the upgraded state.

Upgrade Path

In order to sync a node with the current UnUniFi mainnet, you will need to follow these steps:

Genesis binary

The genesis binary is v1.0.0-beta.1. This binary should be used with genesis file. Refer to instructions details in Joining Mainnet

First Software upgrade

Binary version is v1.0.0-v3.1.0.

Update Daemon for upgrade

If you want ununifid to upgrade automatically, do the following steps prior to the upgrade height:

export UPGRADE_NAME= # upgrade name
export NEW_VERSION= # release version for upgrade

mkdir -p $DAEMON_HOME/cosmovisor/upgrades/$UPGRADE_NAME/bin
cd $HOME/$CHAIN_REPO
git pull
git checkout $NEW_VERSION
make build
cp build/ununifid $DAEMON_HOME/cosmovisor/upgrades/$UPGRADE_NAME/bin

If you are setting true for automatic download in cosmosvisor, you don't need to do this. But, it's not recommended for validators.