Testnet upgrade: v1.3.1

Instructions for the testnet upgrade axelar-core v1.3.1.

The release for the upgrade can be found here.

Upgrade height 22091980 countdown

The v1.3.1 release provides two Linux binaries:

  • Static binary (axelard-linux-amd64-v1.3.1-static)

    • Contains a statically linked libwasmvm
    • Does not require installing or configuring libwasmvm

  • Dynamically linked binary (axelard-linux-amd64-v1.3.1)

    • Requires upgrading libwasmvm to v2.2.4
    • Must add the library directory to LD_LIBRARY_PATH

⚠️

axelard must be built with go-1.25 for this release.

If using the dynamically linked binary, update wasmvm from v1.5.8 to v2.2.4
(libwasmvm.x86_64.so)
and ensure the directory containing the library is added to LD_LIBRARY_PATH.

If using the static binary (*-static), no wasmvm installation is required.

If using the community node setup scripts, please update to the latest commit on main first.
The dynamic wasmvm library will be auto-downloaded to $AXELARD_HOME/lib,
but you’ll still need to add it to LD_LIBRARY_PATH before running the script.

For verifiers, prepare to update ampd.

The v1.3.1 upgrade is required to support the Axelar Network’s migration to Cosmos SDK v0.50. This upgrade reduces block times from 5s → 1s and brings the latest SDK security features.

  1. If you’re a validator or have delegated to one, please vote for the upgrade proposal via:
Terminal window
axelard tx gov vote 404 yes --from validator
  1. Wait for the proposed upgrade block, 22091980. Your node will panic at that block height with a log: {"level":"error","module":"consensus","err":"UPGRADE \"v1.3.1\" NEEDED at height: 22091980",.

Stop your node after chain halt:

Terminal window
pkill -f 'axelard start'
# Validators also need to stop vald/tofnd
pkill -f 'vald-start'
pkill -f tofnd
  1. Backup the state:
Terminal window
cp -r ~/.axelar_testnet/.core/data ~/.axelar-lisbon-3-upgrade-1.3.1/.core/data

⚠️

⚠️ Important: 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. Lower the timeout_commit config in .axelar/config/config.toml from 5s to 1s.

  2. Restart your axelard node with the new v1.3.1 build as well as ampd with the new v1.13.2 binaries.

  3. If you’re a validator also restart vald with v1.3.1 and tofnd with v1.0.1.

Terminal window
# in axelarate-community repo
git checkout main
git pull
KEYRING_PASSWORD="pw-1" ./scripts/node.sh -n testnet -a v1.3.1
# For validators, restart vald/tofnd
KEYRING_PASSWORD="pw-1" TOFND_PASSWORD="pw-2" ./scripts/validator-tools-host.sh -n testnet -a v1.3.1 -q v1.0.1

For verifiers, a new ampd upgrade is required to support axelard v1.3.1. The ampd upgrade must be done after the axelard upgrade.

Restart ampd with the new binary after deploying axelard v1.3.1. The relevant ampd release is available here.

If you encounter a hash error, ensure you have libwasmvm v2.2.4:

https://github.com/CosmWasm/wasmvm/releases/download/v2.2.4/libwasmvm.x86_64.so

Before restarting your node:

  1. Make sure LD_LIBRARY_PATH includes the directory of libwasmvm (dynamic binary only).
  2. Docker users do not need to modify anything.

Edit on GitHub