Testnet upgrade: v0.35
About the v0.35 upgrade
This release adds the Axelar Virtual Machine to the network and adds support for CosmWasm contract creation.
This release enables CosmWasm. Contracts created with CosmWasm will require governance proposals to be deployed for the indefinite future.
Instructions for 2024-February-13
testnet upgrade to axelar-core v0.35.3
, vald v0.35.3
, and tofnd v0.10.1
.
Release can be found here.
Upgrade height 12017025
countdown
Go v1.21 will be needed to build axelard
.
Node operators using binaries need to download wasmvm v1.3.1
libwasmvm.x86_64.so and add the parent folder to LD_LIBRARY_PATH
.
Node operators will need to use the updated cosmsprund
to prune their nodes.
If using the community node setup scripts, please update to the latest commit on main
first.
wasmvm
lib will be auto-downloaded to $AXELARD_HOME/lib
but you’ll need to add it to LD_LIBRARY_PATH
before running the script.
- If you’re a validator or have delegated to one, please vote for the upgrade proposal via
- Wait for the proposed upgrade block,
12017025
. Your node will panic at that block height with a log:{"level":"error","module":"consensus","err":"UPGRADE \"v0.35\" NEEDED at height: 12017025", ...}
. Stop your node after chain halt.
- Backup the state:
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 newv0.35.3
build. - If you’re a validator also restart
vald
withv0.35.3
andtofnd
withv0.10.1
.
Example using join scripts in axelarate-community git repo: