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 binary is the all-in-one command-line interface for running and interacting with an Axelar Network node. Built on the Cosmos SDK, it handles everything from node initialization and key management to submitting cross-chain transactions and operating the external validator daemon (vald). Whether you are spinning up a new validator, querying chain state, or bootstrapping genesis, axelard is the single entry-point for every operation.

​
Getting the Binary

Download the pre-built release from the Axelar Core GitHub releases page and place the binary somewhere on your $PATH: 
# Verify installation
axelard version
The default home directory is $HOME/.axelar. Every command that reads or writes local state accepts a --home flag to override this location.

​
Global Flags

These flags are inherited by every axelard subcommand.
​
--home
string
Directory for config and data. Defaults to $HOME/.axelar.
​
--log_level
string
Logging verbosity: trace, debug, info, warn, error, fatal, or panic. Defaults to info.
​
--log_format
string
Log output format: json or plain. Defaults to plain.
​
--trace
boolean
Print a full stack trace on errors. Useful for debugging.
​
--output
string
Output format for commands that return structured data: text or json. Defaults to text.

​
Quick Status Checks

Use these commands to verify your binary and node are working correctly before diving into deeper operations.

​
axelard version

Prints the application binary version information. 
axelard version
axelard version --long          # Full build info
axelard version --output json   # Machine-readable output

​
axelard status

Queries the remote node for its current status, including sync state, latest block height, and validator info. Output defaults to JSON. 
axelard status
axelard status --node tcp://my-node:26657
axelard status --output json
Use axelard status | jq '.SyncInfo.catching_up' to quickly check whether your node has caught up with the network.

​
axelard health-check

Performs a readiness check against the node and the TSS daemon (tofnd). Reports whether the broadcaster account is funded, the operator is registered, and the TSS sidecar is reachable. 
axelard health-check \
  --operator-addr axelarvaloper1... \
  --node tcp://localhost:26657 \
  --tofnd-host localhost \
  --tofnd-port 50051
FlagDefaultPurpose
--operator-addr—Operator address to check
--nodetcp://localhost:26657CometBFT RPC endpoint
--tofnd-hostlocalhostHostname of the TSS daemon
--tofnd-port50051Port of the TSS daemon
--grpc-addr—gRPC endpoint for this chain
--grpc-insecurefalseAllow gRPC over insecure channels
--height—Query state at a specific block height
--skip-broadcasterfalseSkip broadcaster balance check
--skip-operatorfalseSkip operator registration check
--skip-tofndfalseSkip TSS daemon reachability check

​
Validator Daemon (vald) Commands

Axelar validators run a second process — the vald (validator daemon) — alongside the core node. Vald is responsible for observing external chains and signing threshold signatures via the TSS sidecar (tofnd).

​
axelard vald-start

Starts the vald process. Must be run after the node is synced and the tofnd daemon is running. 
axelard vald-start \
  --validator-addr axelarvaloper1... \
  --from broadcaster \
  --tofnd-host localhost \
  --tofnd-port 50051 \
  --node tcp://localhost:26657 \
  --chain-id axelar-dojo-1
vald-start will broadcast transactions to the chain on behalf of the broadcaster account. Ensure the account has sufficient AXL to pay gas fees before starting.
Key flags:
FlagDefaultPurpose
--validator-addr—Operator address (axelarvaloper1…)
--from—Broadcaster key name or address
--tofnd-hostlocalhostTSS daemon host
--tofnd-port50051TSS daemon port
--tofnd-dial-timeout15sDial timeout for TSS daemon
--gas-prices0.007uaxlGas price for broadcast transactions
--gas-adjustment4Gas adjustment multiplier

​
axelard vald-sign

Signs a hash with the key corresponding to a given key ID for a specific validator. If --pubkey is omitted, the public key is retrieved from the node automatically. 
axelard vald-sign [key-id] [validator-addr] [hash-to-sign] \
  --node tcp://localhost:26657
FlagDefaultPurpose
--pubkey—Validator public key (hex); looked up from node if not set
--nodetcp://localhost:26657RPC endpoint

​
Command Groups

Node Setup & Operations

Initialize, start, and manage a running node — including init, start, status, rollback, prune, comet, and snapshots.

Key Management

Create, import, export, and inspect cryptographic keys used for signing transactions and validator operations.

Genesis Configuration

Bootstrap a new chain: add genesis accounts, create validator gentxs, configure Axelar-specific parameters, and validate the genesis file.

Transactions

Submit on-chain transactions via axelard tx — delegate, vote on governance proposals, interact with cross-chain modules, and more.

​
Full Command Tree

CommandDescription
axelard initInitialize node configuration and genesis file
axelard startRun the full node with CometBFT
axelard statusQuery node status
axelard versionPrint binary version
axelard health-checkCheck node and TSS daemon health
axelard rollbackRoll back chain state by one height
axelard prunePrune historical app state
axelard keysManage cryptographic keys
axelard genesisGenesis-related subcommands
axelard cometCometBFT utility subcommands
axelard snapshotsManage local state snapshots
axelard vald-startStart the validator daemon
axelard vald-signSign a hash with a TSS key
axelard queryQuery chain state
axelard txBroadcast transactions
axelard configManage application configuration
axelard debugDebugging utilities
axelard exportExport chain state to JSON
Run axelard [command] --help at any level of the command tree to see all available subcommands and flags for that command.

Build docs developers (and LLMs) love

Get started for freeTalk to us