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 multisig command group provides read-only access to Axelar’s Multisig module state. The Multisig module manages the threshold key pairs used by Axelar validators to collectively sign EVM command batches and other cross-chain operations. Use these subcommands to inspect key assignments, active keygen sessions, and pending key rotations.
All Multisig query subcommands accept --node, --grpc-addr, --height, and --output flags. Historical queries using --height may fail if the node has pruned that block’s state.

​
Global Flags

The following flags are inherited by every axelard query multisig 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 details of the multisig key corresponding to the given key ID. Key details include the participating validators, their public key shares, and the signing threshold required to produce a valid signature.Syntax
axelard query multisig key [key-id] [flags]
Arguments
​
key-id
string
required
The unique identifier of the multisig key to look up (e.g., Ethereum-key-2024).
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 multisig key Ethereum-key-2024
axelard query multisig key Avalanche-key-2023 --output json
Example output
key:
  id: "Ethereum-key-2024"
  multisig_key:
    threshold: 2
    pubkeys:
    - key_id: "Ethereum-key-2024"
      participant: "axelarvaloper1abc..."
      pub_key: "0x04abc..."
    - key_id: "Ethereum-key-2024"
      participant: "axelarvaloper1def..."
      pub_key: "0x04def..."
  state: KEY_STATE_ACTIVE
Keys with state KEY_STATE_ACTIVE are currently in use for signing. Keys with KEY_STATE_INACTIVE have been rotated out and are no longer used for new batches.
Returns the key ID currently assigned to the given chain. This is the active multisig key used to sign command batches for that chain.Syntax
axelard query multisig key-id [chain] [flags]
Arguments
​
chain
string
required
The name of the chain to look up the active key ID for (e.g., Ethereum, Avalanche).
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 multisig key-id Ethereum
axelard query multisig key-id Avalanche --output json
Example output
key_id: "Ethereum-key-2024"
Use the returned key_id with axelard query multisig key to fetch the full key details, or with axelard query evm address to find the corresponding EVM address.
Returns the key ID assigned for the next key rotation on the specified chain. This key is being prepared (via a keygen session) and will replace the current active key once the rotation is confirmed.Syntax
axelard query multisig next-key-id [chain] [flags]
Arguments
​
chain
string
required
The name of the chain to query the next key ID for (e.g., Ethereum, Polygon).
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 multisig next-key-id Ethereum
axelard query multisig next-key-id Avalanche --output json
Example output
key_id: "Ethereum-key-2025"
If no key rotation is in progress, this query will return an error or an empty response indicating that no next key is scheduled.
Returns detailed information about the keygen session associated with the given key ID. A keygen session is the distributed key generation protocol that validators participate in to create a new multisig key.Syntax
axelard query multisig keygen-session [key-id] [flags]
Arguments
​
key-id
string
required
The key ID whose keygen session you want to inspect (e.g., Ethereum-key-2025).
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 multisig keygen-session Ethereum-key-2025
axelard query multisig keygen-session Avalanche-key-2024 --output json
Example output
session:
  key_id: "Ethereum-key-2025"
  state: KEYGEN_STATE_COMPLETED
  key_share_distribution_policy: KEY_SHARE_DISTRIBUTION_POLICY_WEIGHTED_BY_STAKE
  expires_at: 7850000
  completed_at: 7849500
  is_grace_period: false
  count: 3
  threshold: 2
  participants:
  - address: "axelarvaloper1abc..."
    pub_key: "0x04abc..."
  - address: "axelarvaloper1def..."
    pub_key: "0x04def..."
  - address: "axelarvaloper1ghi..."
    pub_key: "0x04ghi..."
A keygen session in KEYGEN_STATE_PENDING is awaiting participant submissions. KEYGEN_STATE_COMPLETED means the key is ready. KEYGEN_STATE_FAILED means the session did not complete in time and must be restarted.
Returns the on-chain governance parameters for the Multisig module. These parameters govern keygen session timeouts, signing timeouts, and other protocol-level settings.Syntax
axelard query multisig 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 multisig params
axelard query multisig params --output json
Example output
params:
  keygen_threshold: "51/100"
  signing_threshold: "51/100"
  keygen_timeout: 100
  sign_timeout: 100

Build docs developers (and LLMs) love

Get started for freeTalk to us