DevelopersNode OperatorsValidators
Resources
Contract addresses
MainnetTestnet
RPCs
RPC EndpointsFree Public RPC
Tokens
Stake AXL tokensWrap / unwrap tokens
Axelarscan
Add Account to Axelarscan
Misc
SatelliteMetaMaskAdd Network to Keplr Wallet
Upgrades
Mainnet
Axelard
v0.16v0.17v0.18v0.19v0.20v0.21v0.24v0.26v0.28v0.29v0.31v0.33v0.34
Testnet
Axelard
v0.17v0.18v0.19v0.20v0.21v0.22v0.23v0.24v0.25v0.26v0.27v0.28v0.29v0.31v0.32v0.33v0.34
Community
Community Pool ProposalsBug Bounty
Contract and SDK reference
InterchainTokenServiceInterchainTokenFactoryTokenManagerAxelarGateway AxelarGasServiceAxelarExecutableAxelarJS SDK
Learn more about Axelar
Crosschain Message FlowaxlUSDCSecurity OverviewInterchain Transaction DurationEVM Contract Governance
CLI
IntroductionReferenceSend UST to an EVM chainRedeem UST from an EVM chainSend AXL to an EVM chainRedeem AXL from an EVM chain

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

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.

  1. If you’re a validator or have delegated to one, please vote for the upgrade proposal via
axelard tx gov vote 70 yes --from validator
  1. 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.
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.34/.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.35.3 build.
  2. If you’re a validator also restart vald with v0.35.3 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.35.3
# For validators, restart vald/tofnd
KEYRING_PASSWORD="pw-1" TOFND_PASSWORD="pw-2" ./scripts/validator-tools-host.sh -n testnet -a v0.35.3 -q v0.10.1
Edit this page