# Network Upgrade: 3-keyleth
TestNet was successfully upgraded to
3-keyleth in block 7,841,840
3-keyleth upgrade planned for block 6,943,000
This guide is for operators already running a node. For new nodes, please see the Install und with Cosmovisor documentation.
There are two possible methods for upgrading:
- Automatically, using Cosmovisor (recommended)
# Automatically upgrade from und v1.7.x to v1.8.x using Cosmovisor
IMPORTANT: This guide assumes the reader has implemented the required changes outlined in Using Cosmovisor with und: Quick Start and migrated their services before using this guide.
# Configuring Cosmovisor
The following can be implemented well in advance of the actual upgrade occurring, which will allow for a completely automated upgrade.
IMPORTANT During the upgrade,
cosmovisor will automatically do a full backup of the
directory. Ensure your host has adequate disk space to accommodate the backup. This may add significant time
to the upgrade process, and as such, the process may take up to 30 minutes before the node comes back online.
# 1. Create the Cosmovisor upgrade plan directory
This will be dependent on how you configured
cosmovisor, and your actual
mkdir -p $HOME/.und_mainchain/cosmovisor/upgrades/3-keyleth/bin
# 2. Download the latest
und v1.8.x and add to Cosmovisor's
mkdir -p $HOME/tmp && cd $HOME/tmp wget https://github.com/unification-com/mainchain/releases/download/v1.8.2/und_v1.8.2_linux_x86_64.tar.gz tar -zxvf und_v1.8.2_linux_x86_64.tar.gz mkdir -p $HOME/.und_mainchain/cosmovisor/upgrades/3-keyleth/bin mv und $HOME/.und_mainchain/cosmovisor/upgrades/3-keyleth/bin $HOME/.und_mainchain/cosmovisor/upgrades/3-keyleth/bin/und version --log_level=""
Check the version output is
The directory structure for
$HOME/.und_mainchain/cosmovisor should now look as follows:
That's it! When the upgrade height specified in the governance proposal is reached, Cosmovisor and the
module will handle the rest automatically.
# Cosmovisor Upgrade process overview
Briefly, at the upgrade height, Cosmovisor will automatically:
- Stop the
- Reconfigure itself to use
undusing the new version
*Ensure the host has enough space to back up
# Manual upgrade (not recommended)
The alternative to implementing Cosmovisor is to manually upgrade the binary. Once the upgrade height specified in the
governance proposal is reached, the
upgrade module will automatically halt the node via a
panic. The node operator
will then need to:
- Stop the
undv1.7.x binary, via
systemdor their chosen method
- Backup the
- Download and install the latest
undv1.8.x, replacing the old v1.7.x binary (for example in
- Restart the
systemdor their chosen method.
Since the process involves manual intervention, monitoring and execution, the process may take longer.