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.
add-cosmos-based-chain — Register a new Cosmos chain
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
This command is typically submitted via a governance proposal. Ensure the IBC path is verified and active before registration.
register-asset — Register an asset on a Cosmos chain
Registers a new asset denomination on an already-registered Cosmos-based chain. This makes the asset recognisable within the Axelar routing system.Syntax
register-fee-collector — Set the fee collector account
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
execute-pending-transfers — Execute all pending Axelarnet transfers
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
Schedule this command to run periodically in your relayer setup to avoid a backlog of pending transfers building up on the Axelar chain.
route-ibc-transfers — Route pending IBC transfers to Cosmos chains
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
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
The message must have been approved through the Axelar voting process before routing. Use axelard q axelarnet message to check the approval status.
retry-ibc-transfer — Retry a failed IBC transfer
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