Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/axelarnetwork/axelar-core/llms.txt

Use this file to discover all available pages before exploring further.

The axelard tx evm command group provides all transaction subcommands needed to manage EVM-compatible chains on the Axelar network. These commands allow operators and validators to register new chains, configure gateway contracts, deploy cross-chain tokens, confirm on-chain events, and sign batched gateway commands. All subcommands require a funded signing account and an active connection to an Axelar node.

Subcommands

Registers a new EVM chain with the Axelar network. The chain configuration must be supplied as a path to a JSON file containing the key requirements and EVM module parameters.Syntax
axelard tx evm add-chain [name] [chain config] [flags]
Arguments
name
string
required
Human-readable name for the new EVM chain (e.g. ethereum, avalanche).
chain config
string
required
Path to a JSON file containing the chain’s key requirements and EVM module parameters.
Key Flags
--from
string
required
Name or address of the key that signs and pays for the transaction.
--chain-id
string
Axelar network chain ID (default "axelar").
--gas
string
Gas limit per transaction. Use "auto" for automatic estimation (default 200000).
--gas-prices
string
Gas price in decimal format (default "0.007uaxl").
--broadcast-mode
string
Broadcasting mode: sync or async (default "sync").
--keyring-backend
string
Keyring backend to use: os, file, kwallet, pass, test, or memory (default "file").
Example
axelard tx evm add-chain ethereum /path/to/ethereum-config.json \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl \
  --broadcast-mode sync
The JSON config file must conform to the EVM module parameter schema. Refer to the Axelar network documentation for the required fields and format.
Sets (or updates) the AxelarGateway contract address for a registered EVM chain.Syntax
axelard tx evm set-gateway [chain] [address] [flags]
Arguments
chain
string
required
Name of the EVM chain (e.g. ethereum).
address
string
required
EVM address of the AxelarGateway contract (hex, 0x-prefixed).
Key Flags
--from
string
required
Signing key name or address.
--chain-id
string
Network chain ID (default "axelar").
--gas
string
Gas limit (default 200000).
--gas-prices
string
Gas price (default "0.007uaxl").
--broadcast-mode
string
sync or async (default "sync").
--keyring-backend
string
Keyring backend (default "file").
Example
axelard tx evm set-gateway ethereum 0xABCDEF1234567890ABCDEF1234567890ABCDEF12 \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
Creates a deploy-token command targeting the AxelarGateway contract so that a wrapped ERC-20 token for the given origin asset can be deployed on the specified EVM chain.Syntax
axelard tx evm create-deploy-token [evm chain] [origin chain] [origin asset] [token name] [symbol] [decimals] [capacity] [mintLimit] [flags]
Arguments
evm chain
string
required
Target EVM chain where the token will be deployed (e.g. ethereum).
origin chain
string
required
Chain where the asset originates (e.g. axelarnet, cosmos).
origin asset
string
required
Denom or identifier of the asset on the origin chain (e.g. uaxl).
token name
string
required
Full display name of the token (e.g. "Axelar").
symbol
string
required
Token ticker symbol (e.g. AXL).
decimals
uint8
required
Number of decimal places for the token (e.g. 6).
capacity
string
required
Maximum token supply allowed on the EVM chain (use 0 for unlimited).
mintLimit
string
required
Per-mint cap for the token (use 0 for unlimited).
Key Flags
--from
string
required
Signing key name or address.
--address
string
Address of an existing ERC-20 token contract to wrap instead of deploying a new one (default 0x0000000000000000000000000000000000000000).
--chain-id
string
Network chain ID (default "axelar").
--gas
string
Gas limit (default 200000).
--gas-prices
string
Gas price (default "0.007uaxl").
--broadcast-mode
string
sync or async (default "sync").
--keyring-backend
string
Keyring backend (default "file").
Example
axelard tx evm create-deploy-token \
  ethereum axelarnet uaxl "Axelar" AXL 6 0 0 \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
Submits a vote to confirm one or more gateway transactions on an EVM chain. Validators use this command after observing a transaction on the external chain.Syntax
axelard tx evm confirm-gateway-txs [chain] [txID]... [flags]
Arguments
chain
string
required
Name of the EVM chain (e.g. ethereum).
txID
string
required
One or more EVM transaction hashes to confirm (space-separated).
Key Flags
--from
string
required
Signing key name or address.
--chain-id
string
Network chain ID (default "axelar").
--gas
string
Gas limit (default 200000).
--gas-prices
string
Gas price (default "0.007uaxl").
--broadcast-mode
string
sync or async (default "sync").
--keyring-backend
string
Keyring backend (default "file").
Example
axelard tx evm confirm-gateway-txs ethereum \
  0xabc123...def456 \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
Confirms that an ERC-20 token has been deployed on a target EVM chain for an asset originating from another chain. The confirmation is tied to a specific EVM transaction ID.Syntax
axelard tx evm confirm-erc20-token [chain] [origin chain] [origin asset] [txID] [flags]
Arguments
chain
string
required
EVM chain where the token was deployed (e.g. ethereum).
origin chain
string
required
Chain from which the asset originates (e.g. axelarnet).
origin asset
string
required
Asset denom on the origin chain (e.g. uaxl).
txID
string
required
EVM transaction hash of the deployment transaction.
Key Flags
--from
string
required
Signing key name or address.
--chain-id
string
Network chain ID (default "axelar").
--gas
string
Gas limit (default 200000).
--gas-prices
string
Gas price (default "0.007uaxl").
--broadcast-mode
string
sync or async (default "sync").
--keyring-backend
string
Keyring backend (default "file").
Example
axelard tx evm confirm-erc20-token \
  ethereum axelarnet uaxl 0xdeploymentTxHash \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
Confirms that a transfer-operatorship transaction has been executed on an EVM chain gateway. Validators vote on this to finalise the new operator set.Syntax
axelard tx evm confirm-transfer-operatorship [chain] [txID] [flags]
Arguments
chain
string
required
Name of the EVM chain (e.g. ethereum).
txID
string
required
EVM transaction hash of the transfer-operatorship transaction.
Key Flags
--from
string
required
Signing key name or address.
--chain-id
string
Network chain ID (default "axelar").
--gas
string
Gas limit (default 200000).
--gas-prices
string
Gas price (default "0.007uaxl").
--broadcast-mode
string
sync or async (default "sync").
--keyring-backend
string
Keyring backend (default "file").
Example
axelard tx evm confirm-transfer-operatorship \
  ethereum 0xoperatorshipTxHash \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
Requests validators to sign the batch of pending commands for the specified EVM chain’s gateway contract. Once enough signatures are collected the batch can be submitted to the gateway on the external chain.Syntax
axelard tx evm sign-commands [chain] [flags]
Arguments
chain
string
required
Name of the EVM chain whose pending commands should be signed (e.g. ethereum).
Key Flags
--from
string
required
Signing key name or address.
--chain-id
string
Network chain ID (default "axelar").
--gas
string
Gas limit (default 200000).
--gas-prices
string
Gas price (default "0.007uaxl").
--broadcast-mode
string
sync or async (default "sync").
--keyring-backend
string
Keyring backend (default "file").
Example
axelard tx evm sign-commands ethereum \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl \
  --broadcast-mode sync
Run sign-commands after pending transfers have accumulated to batch multiple gateway commands into a single signed payload, reducing the number of external transactions required.
Creates a transfer-operatorship command for an EVM chain’s gateway contract, reassigning control to the key identified by keyID.Syntax
axelard tx evm transfer-operatorship [chain] [keyID] [flags]
Arguments
chain
string
required
Name of the EVM chain (e.g. ethereum).
keyID
string
required
Identifier of the multisig key that will become the new gateway operator.
Key Flags
--from
string
required
Signing key name or address.
--chain-id
string
Network chain ID (default "axelar").
--gas
string
Gas limit (default 200000).
--gas-prices
string
Gas price (default "0.007uaxl").
--broadcast-mode
string
sync or async (default "sync").
--keyring-backend
string
Keyring backend (default "file").
Example
axelard tx evm transfer-operatorship ethereum my-new-key-id \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
After issuing this command, call sign-commands so that validators produce the signed payload and then submit it to the gateway on the EVM chain. Operatorship does not change until the gateway transaction is executed.
Retries processing of a previously failed event for a given EVM chain. Use this when an event was confirmed but could not be processed due to a transient error.Syntax
axelard tx evm retry-event [chain] [event ID] [flags]
Arguments
chain
string
required
Name of the EVM chain that emitted the event (e.g. ethereum).
event ID
string
required
Unique identifier of the failed event to retry.
Key Flags
--from
string
required
Signing key name or address.
--chain-id
string
Network chain ID (default "axelar").
--gas
string
Gas limit (default 200000).
--gas-prices
string
Gas price (default "0.007uaxl").
--broadcast-mode
string
sync or async (default "sync").
--keyring-backend
string
Keyring backend (default "file").
Example
axelard tx evm retry-event ethereum 0xfailedEventId \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl

Common Flags

All axelard tx evm subcommands accept the following standard transaction flags:
FlagDefaultDescription
--fromKey name or address used to sign
--chain-idaxelarNetwork chain ID
--gas200000Gas limit; use auto for estimation
--gas-adjustment1Multiplier applied to simulated gas estimate
--gas-prices0.007uaxlGas price in decimal format
--broadcast-modesyncBroadcasting mode (sync | async)
--keyring-backendfileKeyring backend (os | file | test | memory)
--nodetcp://localhost:26657CometBFT RPC endpoint
--yestrueSkip interactive confirmation prompt

Build docs developers (and LLMs) love