← Back to Skills Marketplace
6tizer

Axon Agent

by 6tizer · GitHub ↗ · v1.0.4 · MIT-0
cross-platform ⚠ suspicious
344
Downloads
0
Stars
0
Active Installs
5
Versions
Install in OpenClaw
/install axon-agent
Description
Register, monitor, and maintain AI Agents on Axon blockchain, managing registration, status, heartbeat daemon, and troubleshooting agent operations.
README (SKILL.md)

Axon Agent Skill

Axon is an AI Agent Native L1 blockchain. An "Agent" is an EVM address that calls register() with 100 AXON stake and sends periodic heartbeats to stay ONLINE.

Official repo: https://github.com/axon-chain/axon
Chain params: RPC https://mainnet-rpc.axonchain.ai/ | Chain ID 9001 | ~5s blocks | Registry 0x0000000000000000000000000000000000000901

CRITICAL: The official Python SDK has an ABI bug. Always use scripts/register.py instead. See references/known-issues.md for details.


Prerequisites

  • Server with Python 3.8+ and Go 1.21+
  • EVM wallet private key saved to a file (e.g. /opt/axon/private_key.txt, chmod 600)
  • Minimum 120 AXON balance (100 stake + 20 burn + gas buffer)
  • web3 Python package: pip install web3

Phase 1: Check Balance & Status

python3 scripts/check-status.py --private-key-file /opt/axon/private_key.txt

If isAgent: True → skip to Phase 3 (daemon setup).


Phase 2: Register Agent

# Dry run first
python3 scripts/register.py \
  --private-key-file /opt/axon/private_key.txt \
  --capabilities "nlp,reasoning,coding,research" \
  --model "claude-sonnet-4.6" \
  --dry-run

# Real registration
python3 scripts/register.py \
  --private-key-file /opt/axon/private_key.txt \
  --capabilities "nlp,reasoning,coding,research" \
  --model "claude-sonnet-4.6"

After success: isAgent: True. Note the registration block number — first heartbeat allowed ~720 blocks later (~1 hour).

Capabilities examples: nlp,reasoning,coding,research | trading,analysis | vision,audio
Model: Use actual model name being run (e.g. claude-sonnet-4.6, glm-5, kimi-k2.5)


Phase 3: Build & Start Daemon

# Clone repo (if not already)
git clone https://github.com/axon-chain/axon /opt/axon
cd /opt/axon

# Build daemon
go build -o tools/agent-daemon/agent-daemon ./tools/agent-daemon/

# Start daemon
nohup /opt/axon/tools/agent-daemon/agent-daemon \
  --rpc https://mainnet-rpc.axonchain.ai/ \
  --private-key-file /opt/axon/private_key.txt \
  --heartbeat-interval 720 \
  --log-level info \
  >> /opt/axon/daemon.log 2>&1 &

echo "PID: $!"

Check logs: tail -f /opt/axon/daemon.log
Expected: heartbeat confirmed every ~720 blocks (~1 hour).


Phase 4: Watchdog Cron

# Copy watchdog to your server (replace YOUR_SERVER and YOUR_KEY)
scp scripts/watchdog.sh user@YOUR_SERVER:/opt/axon/watchdog.sh
ssh user@YOUR_SERVER "chmod +x /opt/axon/watchdog.sh"

# Add cron (every 5 min)
ssh user@YOUR_SERVER "(crontab -l 2>/dev/null; echo '*/5 * * * * /opt/axon/watchdog.sh') | crontab -"

Troubleshooting

See references/known-issues.md for:

  • SDK ABI mismatch (most common failure)
  • HeartbeatInterval first-heartbeat delay
  • Official vs fork repo confusion
  • Stake economics (20 AXON burned permanently)

Quick diagnosis:

# Check daemon running
pgrep -f agent-daemon && echo "running" || echo "NOT running"

# Check on-chain status
python3 scripts/check-status.py --private-key-file /opt/axon/private_key.txt

Multi-Agent Setup

Each agent needs its own EVM wallet + 100 AXON + daemon instance. Steps are identical — run separate daemon processes with different --private-key-file and redirect logs to separate files (e.g. daemon-cto.log).

Usage Guidance
This skill appears to do what it claims (register and maintain Axon agents), but take these precautions before installing: - Private key security: the scripts require a local EVM private key file. Keep it on a dedicated, access-restricted host (chmod 600), and avoid using this key for other purposes. Consider using a hardware signer or isolated VM if feasible. - Verify source before building: the instructions clone and build a Go daemon from the Axon GitHub repo. Confirm the repo URL and review the daemon's code (tools/agent-daemon) or verify a trusted release checksum before building/executing to reduce supply-chain risk. - Metadata omission: the skill metadata does not declare required binaries or config paths, but the SKILL.md does. Ensure your environment has Python 3.8+, Go 1.21+, git, ssh/scp, and nohup, and that you understand where the private key will be stored. - Least privilege & isolation: run the daemon and watchdog on a dedicated host or container with minimal network access beyond the Axon RPC. Limit filesystem permissions to the private key and daemon logs. - Test with a dry run and small/non-critical accounts: use the script's --dry-run first and consider testing with a throwaway wallet before committing real AXON funds (registration requires ~100 AXON and burns 20 AXON). If you want a higher-assurance recommendation before proceeding, provide the exact Git commit or release tag you plan to build and I can highlight any risky code patterns in the daemon source.
Capability Analysis
Type: OpenClaw Skill Name: axon-agent Version: 1.0.4 The skill automates the registration and operation of blockchain agents on the Axon network, requiring the AI to handle raw EVM private keys and perform financial transactions (staking 100 AXON). It executes high-risk system operations including cloning and building Go binaries from GitHub, and establishing persistence via cron jobs for a watchdog script (scripts/watchdog.sh). While the code in scripts/register.py and scripts/check-status.py appears functionally aligned with the stated purpose of bypassing an alleged SDK ABI bug, the requirement for the agent to manage sensitive credentials and modify system startup tasks constitutes a high-risk profile.
Capability Assessment
Purpose & Capability
The files and SKILL.md behavior align with the stated purpose: registering an EVM address as an Axon Agent, checking on-chain status, running a heartbeat daemon, and a watchdog cron. The skill legitimately requires a local EVM private key file and chain RPC access. Minor inconsistency: the registry metadata claims no required binaries/config paths/env vars, but the instructions require Python 3.8+, Go 1.21+, git/ssh/scp/nohup and a private key file path (e.g. /opt/axon/private_key.txt). This metadata omission reduces transparency but does not contradict the stated purpose.
Instruction Scope
Runtime instructions focus on Axon-specific tasks: checking status, calling register() by signing a transaction with a local private key file, building and running the official agent-daemon, and installing a watchdog cron. The scripts only read the provided private key file and use the Axon RPC endpoint; they do not instruct reading unrelated system files or exfiltrating data to unknown external endpoints.
Install Mechanism
There is no packaged install spec; the SKILL.md instructs users to clone and build the official Axon repo (https://github.com/axon-chain/axon) and run the built Go daemon. Building and running a network-fetched Go binary is expected for a daemon, but it is a supply-chain risk — you execute code fetched from a remote repo. The repo URLs referenced appear to be the official project, which reduces concern but users should still verify the source and optionally audit the daemon code before building/executing.
Credentials
The only sensitive credential required is an EVM private key (kept in a local file). That is proportionate to registering/signing transactions on-chain. However, the skill metadata did not declare required config paths or a primary credential; the SKILL.md does rely on a private-key file path and local filesystem permissions. The omission in metadata reduces clarity about secrets handling and should be noted by users.
Persistence & Privilege
The skill instructs building and running a long-lived agent-daemon and installing a cron-based watchdog: this grants persistent presence on the host and requires access to the private key file. That level of persistence is expected for the described functionality but increases the security impact if the built binary or private key is compromised. The skill does not request 'always: true' or modify other skills.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install axon-agent
  3. After installation, invoke the skill by name or use /axon-agent
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.4
Added README.md with official Axon repo link (https://github.com/axon-chain/axon)
v1.0.3
Fix: isAgent/eth_call ABI decode errors no longer crash the script — Axon precompile returns empty bytes on some nodes, now handled gracefully
v1.0.2
Removed hardcoded server IP and key paths — now fully generic. Source: https://github.com/6tizer/axon-agent
v1.0.1
Added GitHub repo link. Note: VirusTotal warning is expected — this skill legitimately handles private keys and blockchain APIs for Axon chain agent registration. Review source at https://github.com/6tizer/axon-agent
v1.0.0
Register and operate AI agents on Axon blockchain (Chain ID 9001). Includes register script with correct ABI (bypasses SDK bug), daemon watchdog, and status checker.
Metadata
Slug axon-agent
Version 1.0.4
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 5
Frequently Asked Questions

What is Axon Agent?

Register, monitor, and maintain AI Agents on Axon blockchain, managing registration, status, heartbeat daemon, and troubleshooting agent operations. It is an AI Agent Skill for Claude Code / OpenClaw, with 344 downloads so far.

How do I install Axon Agent?

Run "/install axon-agent" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Axon Agent free?

Yes, Axon Agent is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Axon Agent support?

Axon Agent is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Axon Agent?

It is built and maintained by 6tizer (@6tizer); the current version is v1.0.4.

💬 Comments