This source did not publish a separate summary. Review SKILL.md before using the skill.
SKILL.md
AWP Registry
Skill version: 0.24.8
API URL
All API calls in this skill use this base URL:
https://tapi.awp.sh/api
If the environment variable AWP_API_URL is set, use that value instead. The scripts read this automatically.
WebSocket: wss://tapi.awp.sh/ws/live
Explorer: deployment-specific (default: https://basescan.org for Base)
Throughout this document, all curl commands use the full URL directly. Do not invent different URLs.
IMPORTANT: Always show the user what you're doing. Every query result, every transaction, every event — print it clearly. Never run API calls silently.
CRITICAL: Registration is FREE and most subnets require ZERO staking. Do NOT tell users they need AWP tokens or staking to get started. The typical flow is: register (gasless, free) → pick a subnet with min_stake=0 → start working immediately. Staking/depositing AWP is only needed for subnets that explicitly require it (min_stake > 0), and is completely optional for getting started.
Fill in the current session's channel and target. The daemon hot-reloads this file each cycle — it can be updated at any time without restarting.
Step 4 — Check notifications: If ~/.awp/notifications.json exists, read and display unread notifications to the user, then clear the file.
Step 5 — Session recovery: Check if wallet is already unlocked:
awp-wallet receive 2>/dev/null
If wallet unlocked (exit code 0), parse wallet_addr from the JSON output: wallet_addr = json["eoaAddress"]. Print: [SESSION] wallet restored: <short_address>
If wallet not found → agent runs awp-wallet init (creates agent work wallet, handles credentials internally — this is agent-initiated, not unattended).
If wallet locked, do nothing — unlock happens on first write action.
Step 6 — Version check (optional, informational only):
Fetch the remote version:
curl -sf https://raw.githubusercontent.com/awp-core/awp-skill/main/SKILL.md | sed -n 's/.*Skill version: \([0-9.]*\).*/\1/p'
If a newer version exists, notify the user: [UPDATE] AWP Skill X.Y.Z available (current: 0.24.8). Skip this step if the network is unavailable.
Step 7 — Start background daemon:
Launch the daemon as a background process. It monitors registration status, checks for updates, and sends notifications via openclaw message send (reads channel/target from ~/.awp/openclaw.json written in Step 3). Daemon logs are written to ~/.awp/daemon.log.
Not registered → present both options and WAIT for the user to choose. Do NOT auto-select either option. The user must explicitly pick one.
── how do you want to start? ─────
Option A: Quick Start
Register as an independent agent.
Free, gasless. No AWP tokens needed.
Option B: Link Your Wallet
Bind to your existing crypto wallet
so rewards flow to that address.
Free, gasless. No AWP tokens needed.
Which do you prefer? (A or B)
───────────────────────────────────
Option A (Solo Mining) — after user picks A:
python3 scripts/relay-start.py --token $TOKEN --mode principal
Option B (Delegated Mining) — after user picks B:
Ask the user for their wallet address, then:
IMPORTANT: After bind(target), rewards automatically resolve to the target address via the bind chain (resolveRecipient() walks the tree). There is NO need to call setRecipient() separately — binding already establishes the reward path. Do NOT suggest or execute setRecipient() after a successful bind.
Only show subnets with min_stake > 0 if the user explicitly asks, or if no free subnets exist.
Step 4: Install subnet skill and start working
Install the skill directly:
[4/4] installing Benchmark skill...
[4/4] ready ✓
── onboarding complete ───────────
wallet: <short_address>
subnet: #1 "Benchmark"
cost: FREE (no staking required)
──────────────────────────────────
Your agent is now working on subnet #1.
No AWP tokens were needed.
If the user later wants to work on a subnet that requires staking, guide them to S2 (deposit) and S3 (allocate) at that time — not during initial onboarding.
Intent Routing
User wants to...
Action
Reference file to load
Start / onboard / setup
ONBOARD
references/commands-staking.md
Query subnet info
Q1
None
Check balance / positions
Q2
None
View emission / epoch info
Q3 [DRAFT]
None
Look up agent info
Q4
None
Browse subnets
Q5
None
Find / install subnet skill
Q6
None
View epoch history
Q7 [DRAFT]
None
Set recipient / bind / start mining
S1
references/commands-staking.md
Deposit / stake AWP
S2
references/commands-staking.md
Allocate / deallocate / reallocate
S3
references/commands-staking.md
Register a new subnet
M1
references/commands-subnet.md
Activate / pause / resume subnet
M2
references/commands-subnet.md
Update skills URI
M3
references/commands-subnet.md
Set minimum stake
M4
references/commands-subnet.md
Create governance proposal
G1
references/commands-governance.md
Vote on proposal
G2
references/commands-governance.md
Query proposals
G3
None
Check treasury
G4
None
Watch / monitor events
W1
None (presets below)
Emission settlement alerts
W2 [DRAFT]
None (workflow below)
Check notifications
NOTIFICATIONS
None — read ~/.awp/notifications.json
View daemon log
LOG
None — tail -50 ~/.awp/daemon.log
Output Format
All structured output (status panels, query results, transaction confirmations, progress steps) must be wrapped in markdown code blocks so the user sees clean, monospaced, aligned text. Use tagged prefixes so the user can follow along:
This is an agent work wallet — do NOT store personal assets in it. The wallet created by this skill is for executing AWP protocol tasks only. Keep only the minimum ETH needed for gas. Do not transfer personal funds or valuable tokens into this wallet.
When the user requests an on-chain operation, the agent executes it directly — no additional confirmation prompt is needed. The user's instruction IS the confirmation. Show a brief summary of what was executed after the transaction:
[WALLET] This is your agent work wallet — for AWP tasks only.
Do NOT store personal assets here. Keep only minimal ETH for gas.
Address: <address>
Rules
Registration is FREE. Never tell users they need AWP tokens, ETH, or staking to register. Registration uses the gasless relay and costs nothing.
Most subnets are FREE to join. Subnets with min_stake = 0 require no staking at all. Always prefer these during onboarding. Only mention staking when the user specifically picks a subnet with min_stake > 0.
Do NOT block onboarding on staking. The flow is: register → pick free subnet → start working. Staking is a separate, optional, later step.
Use bundled scripts for ALL write operations. Never manually construct calldata, ABI encoding, or EIP-712 JSON.
Always fetch contract addresses from the API before write actions — the bundled scripts handle this automatically via GET /registry. Never hardcode contract addresses.
Show amounts as human-readable AWP (wei / 10^18, 4 decimals). Never show raw wei.
Addresses: show as 0x1234...abcd for display, full for parameters.
Do not use stale V1 names: no "unbind()", no "removeAgent()". Binding changes use bind(newTarget).
Wallet handles credentials internally. Just run awp-wallet init + awp-wallet unlock. No password generation, no password files, no user prompts.
This is an agent work wallet. Execute transactions directly when the user requests them — no extra confirmation needed. Remind the user on first setup: do NOT store personal assets in this wallet.
Subnet skill install (Q6): Always install directly. For third-party sources (not github.com/awp-core/*), add a ⚠ third-party source notice but do not block.
Onboarding requires user choice. Always present Option A (Solo) and Option B (Delegated) and WAIT for the user to choose. Never auto-select an option.
Bind already sets the reward path. After bind(target), rewards resolve to the target via the bind chain. Do NOT call setRecipient() after a successful bind — it's redundant.
Bundled Scripts
Every write operation has a script. Always use the script — never construct calldata manually.
scripts/
├── awp-daemon.py Background daemon: auto-started on skill load, monitors status/updates, notifies user (no auto-install/init)
├── awp_lib.py Shared library (API, wallet, ABI encoding, validation)
├── wallet-raw-call.mjs Node.js bridge: sends raw contract calls via awp-wallet signing
├── relay-start.py Gasless register or bind (no ETH needed)
├── relay-register-subnet.py Gasless subnet registration (no ETH needed)
├── onchain-register.py On-chain register
├── onchain-bind.py On-chain bind to target
├── onchain-deposit.py Deposit AWP (approve + deposit)
├── onchain-allocate.py Allocate stake to agent+subnet
├── onchain-deallocate.py Deallocate stake
├── onchain-reallocate.py Move stake between agents/subnets
├── onchain-withdraw.py Withdraw from expired position
├── onchain-add-position.py Add AWP to existing position
├── onchain-register-and-stake.py One-click register+deposit+allocate
├── onchain-vote.py Cast DAO vote
├── onchain-subnet-lifecycle.py Activate/pause/resume subnet
└── onchain-subnet-update.py Set skillsURI or minStake
Wallet Setup
Write actions require the AWP Wallet — an EVM wallet CLI that manages keys internally. No password management needed in default mode.
# Initialize (auto-generates and stores credentials internally)
awp-wallet init
# Unlock and get session token (scope: read | transfer | full)
TOKEN=$(awp-wallet unlock --duration 3600 --scope transfer | python3 -c "import sys,json; print(json.load(sys.stdin)['token'])")
Scope controls what the session token can do: read (balance/status only), transfer (send/approve/sign), full (all including export). Use transfer for normal operations.
On first setup, inform the user:
[WALLET] AWP agent wallet ready.
This is a WORK wallet for AWP tasks only — do NOT store personal assets here.
Address: <address>
All scripts accept --token $TOKEN. Chain defaults to Base (configured in awp-wallet).
Gas Routing
Before bind/setRecipient/registerSubnet, check if the wallet has ETH:
awp-wallet balance --token $TOKEN
Has ETH → use onchain-*.py scripts
No ETH → use relay-*.py scripts (gasless, rate limit: 100/IP/1h)
deposit/allocate/vote always need ETH — no gasless option
Registration is free and gasless. No AWP or ETH needed.
Bind sets the reward path. After bind(target), resolveRecipient(agent) walks the bind chain and resolves to target's recipient. There is NO need to call setRecipient() after binding — it's redundant. Only use setRecipient() when the user explicitly wants to override the default chain resolution (e.g., send rewards to a different address than the bind target).
Solo Mining (bind to self):
python3 scripts/relay-start.py --token $TOKEN --mode principal
S2 · Deposit AWP (optional — only for subnets that require staking)
Most subnets have min_stake=0 and do not require any deposit. Only run these commands if the user wants to work on a subnet with min_stake > 0, or wants to earn voting power.
