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 query axelarnet command group provides read-only access to Axelar’s Axelarnet module state. The Axelarnet module manages Axelar’s native IBC integrations with Cosmos chains — tracking the IBC channel paths used to route cross-chain transfers and monitoring pending outbound IBC transfers. Use these subcommands to look up IBC path registrations and inspect module parameters without submitting any transaction.
Most Axelarnet query subcommands accept --node, --grpc-addr, --height, and --output flags. The ibc-transfer-count subcommand does not expose gRPC or node connection options — it only inherits the global --output, --home, --log_level, and --trace flags.

​
Global Flags

The following flags are inherited by every axelard query axelarnet subcommand.
​
--home
string
Directory for config and data. Defaults to $HOME/.axelar.
​
--log_format
string
Logging format: json or plain. Defaults to plain.
​
--log_level
string
Logging level: trace, debug, info, warn, error, fatal, or panic. Defaults to info.
​
--output
string
Output format: text or json. Defaults to text.
​
--trace
boolean
Print full stack trace on errors.

​
Subcommands

Returns the registered IBC path for the given Cosmos chain. The IBC path identifies the channel through which cross-chain transfers are routed between Axelar and that chain. This is used by Axelar to correctly forward IBC packets.Syntax
axelard query axelarnet ibc-path [chain] [flags]
Arguments
​
chain
string
required
The name of the Cosmos chain to look up the IBC path for (e.g., osmosis, cosmoshub, juno).
Flags
​
--grpc-addr
string
The gRPC endpoint to use for this chain.
​
--grpc-insecure
boolean
Allow gRPC over insecure channels. If not set, the server must use TLS.
​
--height
integer
Query state at a specific block height. May error if the node is pruning state.
​
--node
string
<host>:<port> to CometBFT RPC interface. Defaults to tcp://localhost:26657.
​
-o / --output
string
Output format: text or json. Defaults to text.
Example
axelard query axelarnet ibc-path osmosis
axelard query axelarnet ibc-path cosmoshub --output json
axelard query axelarnet ibc-path juno --node tcp://my-node:26657
Example output
ibcPath: "transfer/channel-3"
The IBC path format is transfer/channel-N where N is the channel number on the Axelar side of the IBC connection. Use chain-by-ibc-path to perform the reverse lookup from path to chain name.
Returns the Cosmos chain name registered for the given IBC path. This is the reverse of ibc-path — given a channel path such as transfer/channel-3, it tells you which Cosmos chain that channel corresponds to.Syntax
axelard query axelarnet chain-by-ibc-path [ibc-path] [flags]
Arguments
​
ibc-path
string
required
The IBC path to look up, in the format transfer/channel-N (e.g., transfer/channel-3).
Flags
​
--grpc-addr
string
The gRPC endpoint to use for this chain.
​
--grpc-insecure
boolean
Allow gRPC over insecure channels.
​
--height
integer
Query state at a specific block height.
​
--node
string
<host>:<port> to CometBFT RPC interface. Defaults to tcp://localhost:26657.
​
-o / --output
string
Output format: text or json. Defaults to text.
Example
axelard query axelarnet chain-by-ibc-path transfer/channel-3
axelard query axelarnet chain-by-ibc-path transfer/channel-0 --output json
Example output
chain:
  name: "osmosis"
  supports_foreign_assets: true
  key_type: KEY_TYPE_NONE
  module: axelarnet
If no chain is registered for the given IBC path, the command returns an error. Ensure the path is in the exact format transfer/channel-N with no trailing characters.
Returns the number of pending (in-flight) outbound IBC transfers per Cosmos chain. This is useful for monitoring Axelar’s IBC transfer queue and diagnosing delays in cross-chain deliveries.Syntax
axelard query axelarnet ibc-transfer-count [flags]
Flags
​
-h / --help
boolean
Display help for this command.
​
--output
string
Output format: text or json. Defaults to text. Inherited from the parent command group.
Example
axelard query axelarnet ibc-transfer-count
axelard query axelarnet ibc-transfer-count --output json
Example output
counts:
- chain: "osmosis"
  count: 5
- chain: "cosmoshub"
  count: 2
- chain: "juno"
  count: 0
A consistently high pending transfer count for a specific chain may indicate an IBC channel is congested, the relayer is down, or the channel has been closed. Cross-reference with the relevant chain’s IBC monitoring tools for diagnosis.
Returns the on-chain governance parameters for the Axelarnet module. These parameters control IBC transfer behaviour, fee collection, and other module-level policies.Syntax
axelard query axelarnet params [flags]
Flags
​
--grpc-addr
string
The gRPC endpoint to use for this chain.
​
--grpc-insecure
boolean
Allow gRPC over insecure channels.
​
--height
integer
Query state at a specific block height.
​
--node
string
<host>:<port> to CometBFT RPC interface. Defaults to tcp://localhost:26657.
​
-o / --output
string
Output format: text or json. Defaults to text.
Example
axelard query axelarnet params
axelard query axelarnet params --output json
Example output
params:
  route_timeout_window: 100
  transfer_limit: 50
  end_blocker_limit: 50
  call_contracts_proposal_min_deposits:
  - denom: "uaxl"
    amount: "100000000"
The route_timeout_window parameter (in blocks) determines how long Axelar waits before timing out a pending IBC packet. If transfers are frequently timing out, governance can increase this value via a parameter change proposal.

Build docs developers (and LLMs) love

Get started for freeTalk to us