Use axelard tx evm to add EVM chains, set gateway contracts, deploy cross-chain tokens, confirm events, sign pending commands, and transfer operatorship.
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.
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
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
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
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
confirm-transfer-operatorship — Confirm operatorship transfer
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
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
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.
transfer-operatorship — Transfer gateway operatorship
Creates a transfer-operatorship command for an EVM chain’s gateway contract, reassigning control to the key identified by keyID.Syntax
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.
retry-event — Retry a failed EVM event
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