This page covers every command involved in the lifecycle of an Axelar node — from first-time initialization through day-to-day operation, maintenance, and the validator daemon. All commands inherit the global flags (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.
--home, --log_level, --log_format, --trace, --output).
axelard init
Generates the initial configuration files for a new node: the private validator key (priv_validator_key.json), node key (node_key.json), genesis file (genesis.json), and application configuration (app.toml, config.toml).
axelar. Must match the network you intend to join.$HOME/.axelar.genesis.json if present. Short form: -o.1.stake.init, replace the generated genesis.json with the official network genesis file before starting the node for the first time.axelard start
Runs the full Axelar node application with CometBFT embedded in-process. This is the primary command for operating a live node.
Networking Flags
tcp://0.0.0.0:26656.ID@host:port seed nodes for peer discovery.ID@host:port peers to maintain persistent connections with.ip:port address advertised to peers for inbound connections.tcp://127.0.0.1:26657.localhost:9090.true.tcp://localhost:1317.Pruning Flags
default (last 362,880 states), nothing (archive), everything (2 latest states), or custom. Defaults to default.custom pruning.custom only).Operational Flags
$HOME/.axelar.0.007uaxl). Transactions with lower fees are rejected.0 disables checks.0 disables snapshots.2.axelard status
Queries the CometBFT RPC endpoint and returns the node’s current status, including block height, sync state, and validator public key.
-n. Defaults to tcp://localhost:26657.text or json. Short form: -o. Defaults to json.axelard health-check
Checks whether the node and its supporting services (broadcaster account and TSS daemon) are ready. Useful in readiness probe scripts for validator operations.
axelarvaloper1…) to check registration status.tcp://localhost:26657.localhost.50051.axelard rollback
Rolls back Cosmos SDK and CometBFT state by exactly one block height. Used to recover from an incorrect application state transition where CometBFT has persisted an incorrect app hash. After rollback, restarting the node will re-execute the transactions in the rolled-back block.
$HOME/.axelar.axelard prune
Prunes historical application state from disk, keeping only recent heights. Run this on a stopped node to reclaim disk space without starting a full archive resync.
| Method | Behaviour |
|---|---|
default | Keep the last 362,880 states |
nothing | Retain all historical state (archive node) |
everything | Keep only the 2 most recent states |
custom | Manually specify --pruning-keep-recent |
custom pruning.goleveldb, rocksdb, or pebbledb. Defaults to goleveldb.$HOME/.axelar.axelard comet
CometBFT utility subcommands for inspecting and managing the consensus layer.
show-node-id — Print the node's P2P ID
show-node-id — Print the node's P2P ID
node_key.json file. Share this ID with peers to allow them to connect directly.show-validator — Print validator consensus public key
show-validator — Print validator consensus public key
show-address — Print consensus address
show-address — Print consensus address
axelarvalcons1… address).version — Print CometBFT version
version — Print CometBFT version
unsafe-reset-all — Wipe all CometBFT data
unsafe-reset-all — Wipe all CometBFT data
--keep-addr-book flag preserves the peer address book.bootstrap-state — Bootstrap state via light client
bootstrap-state — Bootstrap state via light client
reset-state — Remove all data and WAL
reset-state — Remove all data and WAL
axelard snapshots
Manages local application state snapshots. Snapshots enable state-sync, allowing other nodes to quickly bootstrap by downloading a verified state snapshot instead of replaying all blocks from genesis.
list — List available local snapshots
list — List available local snapshots
export — Export current app state as a snapshot
export — Export current app state as a snapshot
dump — Dump snapshot to a portable archive
dump — Dump snapshot to a portable archive
.tar.gz archive file for transfer or backup.-o.load — Load a snapshot archive into the store
load — Load a snapshot archive into the store
.tar.gz snapshot archive into the local snapshot store.restore — Restore app state from a local snapshot
restore — Restore app state from a local snapshot
delete — Delete a local snapshot
delete — Delete a local snapshot
axelard vald-start
Starts the Axelar validator daemon (vald). Vald watches external chains for cross-chain events and participates in threshold signing rounds via the tofnd TSS sidecar. It must be run alongside a fully synced axelard start process.
axelarvaloper1…) that vald will act on behalf of.tofnd TSS daemon. Defaults to localhost.tofnd TSS daemon. Defaults to 50051.tofnd. Defaults to 15s.axelar.tcp://localhost:26657.file.0.007uaxl.4.sync or async. Defaults to sync.systemd or supervisord) that starts vald only after the node RPC endpoint becomes available.