Testnet upgrade: v0.24

Instructions for 2022-Aug-24 testnet upgrade to axelar-core v0.24.0, vald v0.24.0, and tofnd v0.10.1.

Upgrade height 3620300 countdown

  1. If you’re a validator or have delegated to one, please vote for the upgrade proposal via
axelard tx gov vote 20 yes --from validator
  1. Wait for the proposed upgrade block, 3620300. Your node will panic at that block height with a log: {"level":"error","module":"consensus","err":"UPGRADE \"v0.24\" NEEDED at height: ",. Stop your node after chain halt.
pkill -f 'axelard start'
# Validators need to also stop vald/tofnd
pkill -f 'vald-start'
pkill -f tofnd
  1. Backup the state:
cp -r ~/.axelar_testnet/.core/data ~/.axelar-lisbon-3-upgrade-0.24/.core/data

Caution: If you backup the entire folder, ~/.axelar_testnet/.core, that’ll also include your private keys (inside config and keyring-file subfolders). That can be dangerous if anyone gets access to your backups. We recommend backing up keys separately when you first create your node, and then excluding them from any data backups.

  1. Restart your axelard node with the new v0.24.0 build.
  2. If you’re a validator also restart vald with v0.24.0 and tofnd with v0.10.1.

Example using join scripts in axelarate-community git repo:

# in axelarate-community repo
git checkout main
git pull
KEYRING_PASSWORD="pw-1" ./scripts/node.sh -n testnet -a v0.24.0
# For validators, restart vald/tofnd
KEYRING_PASSWORD="pw-1" TOFND_PASSWORD="pw-2" ./scripts/validator-tools-host.sh -n testnet -a v0.24.0 -q v0.10.1
Edit this page