Skip to content

Latest commit

 

History

History
65 lines (46 loc) · 2.51 KB

UPGRADE_V3.md

File metadata and controls

65 lines (46 loc) · 2.51 KB

kichain-t-4 V3 Upgrade

The V3 upgrade kichain-t-4 is set to happen at height 4351400 which at current block time should be reached on 31st of May 2022 around 13H00 UTC.

How to upgrade your node

Use the provided builds or build the new client yourself. A full how-to guide can be found in this dedicated tutorial.

We provide static binary releases with verifiable checksums. We encourage validators to build these binaries themselves using our dedicated tutorial and check the resulting checksum.

The client version should be:

kid version --long

# name: kitools
# server_name: kid
# version: Testnet-3.0.0-beta
# commit: 2a87d4df01e7da5f6c4e59f38148affd49fb35c3
# build_tags: netgo ledger muslc,
# go: go version go1.17.10 linux/amd64

With Cosmovisor

To upgrade your node using Cosmovisor you need to follow these steps:

# Check that your $DAEMON_HOME is correctly set
echo $DAEMON_HOME

# Download new binary (amd64 version, please adapt if you use an arm arch)
wget https://github.com/KiFoundation/ki-tools/releases/download/3.0.0-beta/kid-testnet-3.0.0-beta-linux-amd64
mv kid-testnet-3.0.0-beta-linux-amd64 kid
chmod +x kid

# check shasum - should be 3ec617c3050a1c9d27f8a8a4d171308fe94b6a89d55d6ab28b48dfb3a1a87871
sha256sum ./kid

# check version - should be Testnet-3.0.0-beta (commit 2a87d4df01e7da5f6c4e59f38148affd49fb35c3)
./kid version --long

# make a directory if you haven't already
mkdir -p $DAEMON_HOME/cosmovisor/upgrades/v3/bin

# copy this new binary
cp kid $DAEMON_HOME/cosmovisor/upgrades/v3/bin/

# this should return Testnet-3.0.0-beta
$DAEMON_HOME/cosmovisor/upgrades/v3/bin/kid version

When the upgrade height is reached, Cosmovisor will automatically restart using the new binary.

Without Cosmovisor

To upgrade your node without using Cosmovisor, you need to follow these steps:

  1. Wait for the chain upgrade height. When it is reached, the node will stop. If the kid process is not automatically killed, kill it with the kill command.
  2. Download the provided client or build it as shown earlier.
  3. Start the node with the new client : kid start --home <NODE_HOME>

Security

If you discover a security vulnerability in this project, please report it to [email protected]. We will promptly address all security vulnerabilities.