Testnet upgrade: v1.1
Instructions for the 2024-Dec-12
testnet upgrade to axelar-core v1.1.2
.
Release can be found here
Upgrade height 16665600
countdown
About the v1.1 upgrade
The v1.1.2
upgrade is a consensus breaking release for Axelar testnet. Once live, it will enable the deployment of ITS Hub on testnet.
- If you’re a validator or have delegated to one, please vote for the upgrade proposal via
axelard tx gov vote 164 yes --from validator
⚠️
⚠️
axelard
must be built with go-1.23
for this release.
- Wait for the proposed upgrade block,
16665600
. Your node will panic at that block height with a log:{"level":"error","module":"consensus","err":"UPGRADE \"v1.1.2\" NEEDED at height: 16665600",
. Stop your node after chain halt.
pkill -f 'axelard start'# Validators need to also stop vald/tofndpkill -f 'vald-start'pkill -f tofnd
- Backup the state:
cp -r ~/.axelar_testnet/.core/data ~/.axelar-lisbon-3-upgrade-1.1.2/.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.
- Restart your
axelard
node with the newv1.1.2
build. - If you’re a validator also restart
vald
withv1.1.2
andtofnd
withv1.0.1
.
Example using join scripts in axelarate-community git repo:
# in axelarate-community repogit checkout maingit pullKEYRING_PASSWORD="pw-1" ./scripts/node.sh -n testnet -a v1.1.2# For validators, restart vald/tofndKEYRING_PASSWORD="pw-1" TOFND_PASSWORD="pw-2" ./scripts/validator-tools-host.sh -n testnet -a v1.1.2 -q v1.0.1