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 nexus command group provides transaction subcommands for the Nexus module, which serves as the cross-chain routing hub of the Axelar network. Validators use these commands to register or deregister themselves as chain maintainers, governance can activate or deactivate supported chains, operators can configure per-asset fee structures, and any participant can retry a failed general message routing attempt.

​
Subcommands

Registers the sender (a validator’s proxy address) as a chain maintainer for one or more chains. Chain maintainers are responsible for observing and voting on events from the chains they maintain.Syntax
axelard tx nexus register-chain-maintainer [chain]... [flags]
Arguments
​
chain
string
required
One or more chain names to maintain (space-separated, e.g. ethereum avalanche).
Key Flags
​
--from
string
required
Proxy address of the validator registering as maintainer. Must be the registered proxy for the validator.
​
--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 nexus register-chain-maintainer ethereum \
  --from myproxy \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl \
  --broadcast-mode sync
The --from address must be the validator’s proxy address, not the validator’s operator address. Register a proxy first using axelard tx snapshot register-proxy.
Deregisters the sender as a chain maintainer for one or more chains. After deregistration the validator will no longer be expected to vote on events from those chains.Syntax
axelard tx nexus deregister-chain-maintainer [chain]... [flags]
Arguments
​
chain
string
required
One or more chain names to stop maintaining (space-separated).
Key Flags
​
--from
string
required
Proxy address of the validator deregistering.
​
--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 nexus deregister-chain-maintainer ethereum \
  --from myproxy \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
Deregistering reduces the validator set for the affected chains. Ensure that the remaining maintainers meet the minimum threshold before deregistering.
Activates one or more chains, enabling cross-chain transfers and message routing through Axelar for those chains. This is typically a governance-gated operation.Syntax
axelard tx nexus activate-chain [chain]... [flags]
Arguments
​
chain
string
required
One or more chain names to activate (space-separated, 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 nexus activate-chain ethereum \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
Deactivates one or more chains, halting cross-chain transfers and message routing for those chains. This may be used as an emergency circuit breaker or during scheduled maintenance.Syntax
axelard tx nexus deactivate-chain [chain]... [flags]
Arguments
​
chain
string
required
One or more chain names to deactivate (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 nexus deactivate-chain ethereum \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
Deactivating a chain immediately stops all pending transfers and message routing to that chain. In-flight messages may be lost or need manual recovery.
Registers the fee rate, minimum fee, and maximum fee for a specific asset on a given chain. These parameters govern how much users are charged when transferring that asset through Axelar.Syntax
axelard tx nexus register-asset-fee [chain] [asset] [fee-rate] [min-fee] [max-fee] [flags]
Arguments
​
chain
string
required
Name of the chain for which the fee applies (e.g. ethereum).
​
asset
string
required
Asset denomination for which the fee is being set (e.g. uaxl, uusdc).
​
fee-rate
string
required
Proportional fee expressed as a decimal fraction (e.g. "0.001" for 0.1%).
​
min-fee
string
required
Minimum fee amount in the asset’s base denomination (e.g. "1000" for 1000 uaxl).
​
max-fee
string
required
Maximum fee amount in the asset’s base denomination (e.g. "1000000" for 1 AXL).
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 nexus register-asset-fee \
  ethereum uaxl "0.001" "1000" "1000000" \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
Fee parameters take effect immediately once the transaction is confirmed. Existing in-flight transfers use the fee schedule that was active when they were initiated.
Re-attempts routing of a general message that previously failed to reach its destination. This is useful when a transient error (such as a contract revert on the destination chain) caused the routing to fail.Syntax
axelard tx nexus retry-failed-message [message-id] [flags]
Arguments
​
message-id
string
required
Unique identifier of the failed general message to retry (e.g. ethereum-2|0xTxHash-1).
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 nexus retry-failed-message \
  "ethereum-2|0xfailedTxHash-1" \
  --from mykey \
  --chain-id axelar \
  --gas auto \
  --gas-prices 0.007uaxl
Query the message status with axelard q nexus message [message-id] before retrying to confirm it is in a failed state and to understand the root cause.

​
Common Flags

All axelard tx nexus subcommands accept the following standard transaction flags:
FlagDefaultDescription
--from—Key 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

Get started for freeTalk to us