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 axelarnet command group contains all transaction subcommands for managing the Axelarnet module. These commands let operators register new Cosmos-based chains and their assets, configure fee collection, route pending IBC transfers, relay approved general messages, and recover from failed IBC transfers. Most operations require governance approval or validator-level privileges.

Subcommands

Adds a new Cosmos-SDK-based chain to the Axelar network. You must supply the chain’s human-readable name, its bech32 address prefix, the IBC path used to connect it, and one or more native asset denoms.Syntax
axelard tx axelarnet add-cosmos-based-chain [name] [address prefix] [ibc path] [native asset]... [flags]
Arguments
name
string
required
Human-readable name for the Cosmos chain (e.g. osmosis).
address prefix
string
required
Bech32 address prefix used by the chain (e.g. osmo).
ibc path
string
required
IBC connection path that links Axelar to the chain (e.g. channel-3).
native asset
string
required
One or more native asset denoms supported by the chain (space-separated, e.g. uosmo).
Key Flags
--from
string
required
Name or address of the signing key.
--chain-id
string
Axelar network chain ID (default "axelar").
--gas
string
Gas limit (default 200000). Use "auto" for automatic estimation.
--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: os, file, kwallet, pass, test, or memory (default "file").
Example
axelard tx axelarnet add-cosmos-based-chain \
  osmosis osmo channel-3 uosmo \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl \
  --broadcast-mode sync
This command is typically submitted via a governance proposal. Ensure the IBC path is verified and active before registration.
Registers a new asset denomination on an already-registered Cosmos-based chain. This makes the asset recognisable within the Axelar routing system.Syntax
axelard tx axelarnet register-asset [chain] [denom] [flags]
Arguments
chain
string
required
Name of the registered Cosmos chain (e.g. osmosis).
denom
string
required
Asset denomination to register (e.g. uosmo or an IBC denom hash).
Key Flags
--from
string
required
Signing key name or address.
--is-native-asset
bool
Pass this flag if the asset is a native token of the Cosmos chain rather than an IBC-transferred asset.
--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 axelarnet register-asset osmosis uosmo \
  --is-native-asset \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
Designates the Axelarnet account that will collect cross-chain transfer fees. Only one fee collector can be active at a time; calling this command again replaces the existing address.Syntax
axelard tx axelarnet register-fee-collector [fee collector] [flags]
Arguments
fee collector
string
required
Bech32 Axelar address that will receive collected fees (e.g. axelar1...).
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 axelarnet register-fee-collector axelar1feeCollectorAddress \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
Triggers execution of all pending cross-chain transfers that are queued for the Axelar chain. This command is typically called by relayers or automated scripts to process accumulated transfer events.Syntax
axelard tx axelarnet execute-pending-transfers [flags]
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 axelarnet execute-pending-transfers \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl \
  --broadcast-mode sync
Schedule this command to run periodically in your relayer setup to avoid a backlog of pending transfers building up on the Axelar chain.
Dispatches all pending outbound IBC transfers from Axelar to their respective destination Cosmos chains. Relayers call this as part of the normal cross-chain transfer flow.Syntax
axelard tx axelarnet route-ibc-transfers [flags]
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 axelarnet route-ibc-transfers \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl \
  --broadcast-mode sync
Routes a previously approved general message to its destination chain. The caller supplies the message ID (assigned at approval time) and the ABI-encoded payload to forward.Syntax
axelard tx axelarnet route-message [message ID] [payload] [flags]
Arguments
message ID
string
required
Unique identifier of the approved general message (assigned by the Axelar network upon approval).
payload
string
required
ABI-encoded or hex-encoded payload bytes to forward to the destination contract.
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 axelarnet route-message \
  "ethereum-2|0xTxHash-1" \
  0xEncodedPayload \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
The message must have been approved through the Axelar voting process before routing. Use axelard q axelarnet message to check the approval status.
Re-attempts an IBC transfer that previously failed (for example, due to a closed channel or a timeout). Provide the numeric transfer ID that was assigned when the transfer was originally queued.Syntax
axelard tx axelarnet retry-ibc-transfer [transfer ID] [flags]
Arguments
transfer ID
uint64
required
Numeric identifier of the failed IBC transfer 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 axelarnet retry-ibc-transfer 42 \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
Before retrying, verify that the IBC channel is open and operational on both ends. Retrying against a permanently closed channel will fail again.

Common Flags

All axelard tx axelarnet 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