---
name: axon-validator-node
description: Axon is a general-purpose blockchain for AI agents with an independent L1 and full EVM compatibility. Use this skill when an AI agent needs to handle Axon mainnet validator and sync-node operations with the official script-first workflow, including bootstrap, funding checks, sync verification, create-validator, agent-validator steps after validator creation, key handling, recovery, and node troubleshooting. Do not use it for ordinary wallet-only tasks or non-validator Agent workflows.
metadata: {"openclaw":{"skillKey":"axon-validator-node","emoji":"⛓️"}}
---

# Axon Validator Node

This skill is the operator playbook for the agent.

## What Axon Is

- Axon is a general-purpose blockchain for AI agents.
- It runs an independent L1 while also exposing an EVM-compatible mainnet for wallets and contracts.
- Validator and Agent participation are first-class protocol workflows on Axon mainnet.
- Mainnet node operations use Cosmos chain ID `axon_8210-1`; wallet-facing EVM tools use chain ID `8210`.
- `AXON` is the native token used for stake, burns, and gas-denominated user-facing operations.

This skill covers the operator side of Axon. It is for validators, sync nodes, validator economics, agent-validator steps, and node recovery.

Use this skill when the request is about running, recovering, verifying, registering, or troubleshooting an Axon mainnet validator or sync node.

Do not use this skill for ordinary wallet usage. If the user only needs MetaMask, balances, transfers, or public RPC reads, switch to `axon-mainnet-user`.

## Agent job

- Recognize that this is an operator workflow, not a wallet walkthrough.
- Keep node chain ID and wallet chain ID clearly separated.
- Follow the official script-first path unless low-level debugging is explicitly required.
- Load the relevant reference file before giving step-by-step operational commands.
- If the user asks what Axon is, give a short project overview before moving into validator instructions.

## What You Can Do With This Skill

- Explain Axon at a high level in the context of validators, Agents, and node operations.
- Guide bootstrap and recovery using the official public scripts and published mainnet files.
- Check readiness for funding, sync completion, `create-validator`, and agent-validator registration after validator creation.
- Explain validator rights, validator obligations, and validator-side mining mechanics.
- Help troubleshoot RPC, peer, fee, key, and heartbeat issues.
- Redirect wallet-only usage and non-validator Agent usage back to `axon-mainnet-user`.

## Official GitHub References

When you need more project detail beyond this skill, use the official Axon repository:

- Project overview and mainnet facts: [github.com/axon-chain/axon/blob/main/README.md](https://github.com/axon-chain/axon/blob/main/README.md)
- Latest releases: [github.com/axon-chain/axon/releases/latest](https://github.com/axon-chain/axon/releases/latest)
- Mainnet genesis: [github.com/axon-chain/axon/blob/main/docs/mainnet/genesis.json](https://github.com/axon-chain/axon/blob/main/docs/mainnet/genesis.json)
- Mainnet bootstrap peers: [github.com/axon-chain/axon/blob/main/docs/mainnet/bootstrap_peers.txt](https://github.com/axon-chain/axon/blob/main/docs/mainnet/bootstrap_peers.txt)
- Validator startup script: [github.com/axon-chain/axon/blob/main/scripts/start_validator_node.sh](https://github.com/axon-chain/axon/blob/main/scripts/start_validator_node.sh)
- Sync-node startup script: [github.com/axon-chain/axon/blob/main/scripts/start_sync_node.sh](https://github.com/axon-chain/axon/blob/main/scripts/start_sync_node.sh)
- Agent heartbeat daemon: [github.com/axon-chain/axon/blob/main/tools/agent-daemon/README_EN.md](https://github.com/axon-chain/axon/blob/main/tools/agent-daemon/README_EN.md)

## Non-negotiable rules

- Mainnet node identity uses Cosmos chain ID `axon_8210-1`.
- Wallet-facing EVM tooling uses chain ID `8210`.
- Prefer the official script workflow from the `axon-chain/axon` repository.
- Do not suggest a manual `axond init` plus manual genesis-fetch flow unless the user explicitly needs low-level debugging.
- Do not tell the user to submit `create-validator` until the validator account is funded, local RPC is up, and `catching_up` is `false`.
- Do not tell the user to register as an Agent until the validator is already created on chain and the signing account still has enough liquid balance for the extra Agent stake plus gas.
- Treat the mnemonic, `KEYRING_PASSWORD_FILE`, validator key files, and any signing key material as sensitive.
- Current practical transaction default: use `GAS_PRICES=1000000000aaxon` unless the local helper already sets a non-zero gas price.
- Current chain-verified Agent parameters are: minimum Agent stake `100 AXON`, registration burn `20 AXON`, heartbeat interval `100` blocks, reward split `20% proposer / 55% validator pool / 25% reputation pool`.

## Workflow routing

- For first-time setup, rebuilds, or exact shell commands, read `references/mainnet-validator.md`.
- For validator duties, validator rights, and validator-side mining mechanics, read `references/validator-mechanics.md`.
- For backups, exposed ports, double-sign prevention, and key hygiene, read `references/validator-security.md`.
- For fee failures, peer failures, sync lag, or missing validator status, read `references/validator-troubleshooting.md`.

## Response policy

- Give exact commands when operating the node.
- Keep `axon_8210-1` and `8210` clearly separated in the response.
- Prefer `start_validator_node.sh` and `start_sync_node.sh` over lower-level alternatives.
- If the user asks to proceed with `create-validator`, explicitly check sync state, funding state, and local RPC readiness first.
- If the user asks about validator rewards or validator mining, explain the current chain logic in terms of proposer rewards, validator-pool eligibility, stake, reputation, and online status rather than using vague marketing language.
- If the user asks to become an Agent validator, first verify the validator is bonded, then register the same account with `axond tx agent register`, then set up a heartbeat loop.