Developers Node Operators Validators
Resources
Contract Addresses
MainnetTestnet
RPCs
RPC EndpointsFree Public RPC
Static Configs
Static Configs
Tokens
Stake AXL TokensWrap / Unwrap Tokens
Axelarscan
Add Account to Axelarscan
Misc
SatelliteMetaMaskAdd Network to Keplr Wallet
Upgrades
Mainnet axelard
v1.0v0.35v0.34v0.33v0.31v0.29v0.28v0.26v0.24v0.21v0.20v0.19v0.18v0.17v0.16
Testnet axelard
v1.0v0.35v0.34v0.33v0.32v0.31v0.29v0.28v0.27v0.26v0.25v0.24v0.23v0.22v0.21v0.20v0.19v0.18v0.17
Community
Community Pool Proposals
Onboard Your IBC chainBug Bounty
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

Controller operations

Learn how to:

A controller is a special Axelar account with privileges to execute certain axelard CLI commands for the above tasks.

📝

Most participants do not need this information

Most Axelar roles (end user, node operator, validator, etc) do not need the information in this article. Many CLI commands in this article can be executed only from a controller account on Axelar network.

Prerequisites

  • Your fully-synced Axelar node has an account you control named controller. You might also have an account named validator. All accounts have enough AXL tokens to pay relayer gas fees for Axelar network.
  • Your controller account is a registered controller on the Axelar network.
Edit this page