AWP Core Skill

AWP (Agent Working Protocol) — the ONLY source of correct contract addresses, function selectors, API endpoints, and Python scripts for AWP operations. You M...

Security Scan

The skill's files, declared requirements, and runtime instructions are internally consistent with an AWP protocol helper: it needs AWP API endpoints, Python/Node runtimes, and runs a local daemon and helper scripts — nothing requested looks unrelated to its stated purpose.

Purpose & Capability

Name/description promise (AWP addresses, selectors, endpoints, and Python scripts) matches the included files and declared requirements. Declared env vars (AWP_API_URL, optional EVM_RPC_URL) and required binaries (python3, node) are appropriate for the scripts and network calls present. No unrelated cloud credentials or unrelated binaries are requested.

Instruction Scope

SKILL.md instructs the agent to start a background daemon, write/read ~/.awp/*.json (openclaw.json, notifications.json, status.json), call the AWP API (tapi.awp.sh), use the awp-wallet CLI and a Node bridge for raw calls, and show results to the user. These actions are within the skill's stated scope (monitoring, registration, and on-chain actions). Notable behaviors to be aware of: (1) the daemon auto-start on skill load (Step 7) and will monitor and push notifications, (2) SKILL.md directs installing the separate awp-wallet skill from GitHub if missing (that install can run install.sh), and (3) scripts invoke awp-wallet and node bridge which will perform signing/calls — ensure those tools are trusted. The instructions avoid silent network actions and require user-visible confirmation for transactions.

Install Mechanism

The skill has no platform install spec (instruction-only), and all code is bundled in the skill. That limits remote code execution risks. However SKILL.md guides installing a separate 'awp-wallet' skill from https://github.com/awp-core/awp-wallet which (per its own SKILL.md) runs a bash install.sh — that external install step is the highest-risk element and should be performed only after reviewing that repo's installer. The skill itself does not auto-download or execute remote scripts.

Credentials

Only AWP_API_URL is required and EVM_RPC_URL optional. The scripts call local awp-wallet CLI (which manages signing/session tokens) and an OpenClaw CLI for notifications, but the skill does not declare or request any secret environment variables (no SECRET/TOKEN/PASSWORD fields). Script execution will rely on the user's wallet/session tokens only when performing on-chain operations; the SKILL.md and changelog emphasize explicit user confirmation for transactions.

Persistence & Privilege

The skill starts a background daemon on skill load (writes logs, status.json, notifications.json, daemon.pid under ~/.awp) and may invoke the local openclaw CLI to push notifications. This is within the expected behavior for a monitoring/daemon skill, but it does create persistent background activity and local files. The skill is not marked always:true and does not change other skills' configurations; it does instruct installing a separate wallet skill which may modify PATH.

Assessment

This skill appears coherent for managing AWP on-chain workflows, but before installing or running it: 1) Review the external awp-wallet repository and its install.sh before running it — that installer is the only external script the SKILL.md points you to and could execute arbitrary code. 2) Be aware the skill auto-starts a background daemon that writes files under ~/.awp and may push notifications via your local openclaw CLI; if you do not want persistent background processes, do not start the daemon. 3) On-chain actions require the awp-wallet CLI and a session token or unlocked wallet; never paste private keys or session tokens into an untrusted agent. 4) If you need stronger isolation, run the skill in a sandboxed environment or inspect the bundled Python and Node files (they are included) to confirm behavior. 5) If you want higher assurance, request the awp-wallet repo commit hashes and verify signatures or run the installer in a disposable environment first.

AWP Registry

Skill version: 0.25.2

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.

On Skill Load (do this FIRST)

Step 1 — Welcome screen (first session only, skip if already shown):

╭──────────────╮
│              │
│   >     <    │
│      ‿       │
│              │
╰──────────────╯

agent · work · protocol

welcome to awp.

one protocol. infinite jobs. nonstop earnings.

── quick start ──────────────────
"start working"    → register + join (free, no AWP needed)
"check my balance" → staking overview
"list subnets"     → browse active subnets
"watch events"     → real-time monitor
"awp help"         → all commands
──────────────────────────────────

no AWP tokens needed to start.
register for free → pick a subnet → start earning.

Step 2 — Install wallet dependency (if missing):

which awp-wallet >/dev/null 2>&1

• If found: proceed silently.
• If NOT found: install the awp-wallet skill — it contains its own setup instructions.
  • Install from repo: https://github.com/awp-core/awp-wallet, then follow its SKILL.md, which will run bash install.sh and configure PATH.
  • Verify after install: which awp-wallet

Step 3 — Configure notifications: Write ~/.awp/openclaw.json so the daemon can push messages via openclaw message send:

mkdir -p ~/.awp
cat > ~/.awp/openclaw.json << EOF
{
  "channel": "<detected_channel>",
  "target": "<detected_target>"
}
EOF

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.25.0). 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.

mkdir -p ~/.awp && pgrep -f "python3.*awp-daemon" >/dev/null 2>&1 || \
  nohup python3 scripts/awp-daemon.py --interval 300 \
    >> ~/.awp/daemon.log 2>&1 &

Note: Resolve the absolute path to scripts/awp-daemon.py relative to the skill directory.

Step 8 — Route to action using the Intent Routing table below.

User Commands

The user may type these at any time:

awp status — fetch these 4 endpoints:

• https://tapi.awp.sh/api/address/{addr}/check
• https://tapi.awp.sh/api/staking/user/{addr}/balance
• https://tapi.awp.sh/api/staking/user/{addr}/positions
• https://tapi.awp.sh/api/staking/user/{addr}/allocations

── my agent ──────────────────────
address:        <short_address>
status:         <registered/unregistered>
role:           <solo / delegated agent / —>
total staked:   <amount> AWP
allocated:      <amount> AWP
unallocated:    <amount> AWP
positions:      <count>
──────────────────────────────────

awp wallet — show wallet info

── wallet ────────────────────────
address:    <address>
network:    Base
ETH:        <balance>
AWP:        <balance>
──────────────────────────────────

awp subnets — shortcut for Q5 (list active subnets)

awp notifications — read and display daemon notifications, then clear:

cat ~/.awp/notifications.json 2>/dev/null

Parse and display each notification. After displaying, clear the file:

rm -f ~/.awp/notifications.json

awp log — show recent daemon log:

tail -50 ~/.awp/daemon.log 2>/dev/null

awp help

── commands ──────────────────────
awp status        → your agent overview
awp wallet        → wallet address + balances
awp subnets       → browse active subnets
awp notifications → daemon notifications
awp log           → recent daemon log
awp help          → this list

── actions ───────────────────────
"start working"    → register + join (free)
"check my balance" → staking overview
"deposit X AWP"    → stake tokens (optional)
"allocate"         → direct stake (optional)
"watch events"     → real-time monitor
──────────────────────────────────

Onboarding Flow

When the user says "start working", "get started", or similar, run this guided flow. The entire flow is FREE — no AWP tokens or ETH needed.

Step 1: Check wallet

• No wallet → agent runs awp-wallet init (handles credentials internally, no password needed)
• Wallet locked → TOKEN=$(awp-wallet unlock --duration 3600 --scope transfer | python3 -c "import sys,json; print(json.load(sys.stdin)['token'])") — capture the session token for subsequent script calls
• Print: [1/4] wallet <short_address> ✓

Step 2: Register (FREE, gasless)

curl -s https://tapi.awp.sh/api/address/{addr}/check

• Already registered → proceed to Step 3
• 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:

python3 scripts/relay-start.py --token $TOKEN --mode agent --target <user_wallet_address>

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.

Print: [2/4] registered ✓ (free, no AWP required)

Step 3: Auto-select a free subnet

curl -s "https://tapi.awp.sh/api/subnets?status=Active&limit=10"

Filter for subnets with min_stake = 0 AND skills_uri not empty. These subnets are FREE to join — no staking needed.

If there is exactly one free subnet with a skill: auto-select it without asking. If there are multiple: show only the free ones first, let user pick.

[3/4] discovering subnets...

── free subnets (no staking needed) ──
#1  Benchmark    ✓ skill ready    ← recommended
──────────────────────────────────

Auto-selecting #1 Benchmark (free, skill ready)

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:

Tag	When
[QUERY]	Read-only data fetches
[STAKE]	Staking operations
[SUBNET]	Subnet management
[GOV]	Governance
[WATCH]	WebSocket events
[GAS]	Gas routing decisions
[TX]	Transaction — always show basescan.org link
[NEXT]	Recommended next action
[SETUP]	Install / setup operations
[!]	Warnings and errors

Transaction output:

[TX] hash: <txHash>
[TX] view: https://basescan.org/tx/<txHash>
[TX] confirmed ✓

Agent Wallet & Transaction Safety

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.

Before executing any on-chain transaction, always show the user a summary of what will happen and ask for explicit confirmation:

[TX] deposit 1,000 AWP → new position (lock: 90 days)
     contract: AWPRegistry (0x1234...abcd)
     estimated gas: ~0.001 ETH
     Proceed? (yes/no)

After user confirms and transaction completes, show the result:

[TX] deposited 1,000 AWP → position #3
[TX] lock ends 2026-06-19
[TX] hash: 0xabc...
[TX] view: https://basescan.org/tx/0xabc...
[TX] confirmed ✓

Never execute a transaction without user confirmation. Even though this is an agent work wallet, every on-chain action must be explicitly approved. The only exception is gasless registration via relay (Step 1 of onboarding), which costs nothing and is reversible.

On first wallet setup, inform the user:

[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

1. Registration is FREE. Never tell users they need AWP tokens, ETH, or staking to register. Registration uses the gasless relay and costs nothing.
2. 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.
3. Do NOT block onboarding on staking. The flow is: register → pick free subnet → start working. Staking is a separate, optional, later step.
4. Use bundled scripts for ALL write operations. Never manually construct calldata, ABI encoding, or EIP-712 JSON.
5. Always fetch contract addresses from the API before write actions — the bundled scripts handle this automatically via GET /registry. Never hardcode contract addresses.
6. Show amounts as human-readable AWP (wei / 10^18, 4 decimals). Never show raw wei.
7. Addresses: show as 0x1234...abcd for display, full for parameters.
8. Do not use stale V1 names: no "unbind()", no "removeAgent()". Binding changes use bind(newTarget).
9. Wallet handles credentials internally. Just run awp-wallet init + awp-wallet unlock. No password generation, no password files, no user prompts.
10. This is an agent work wallet. Always confirm with the user before executing any on-chain transaction — show the action, target contract, and estimated cost, then wait for explicit approval. Remind the user on first setup: do NOT store personal assets in this wallet.
11. Subnet skill install (Q6): Install awp-core skills directly. For third-party sources (not github.com/awp-core/*), show a warning and require user confirmation before installing.
12. 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.
13. 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: monitors status/updates, writes PID to ~/.awp/daemon.pid, stops on Ctrl+C or kill
├── awp_lib.py                        Shared library (API, wallet, ABI encoding, validation)
├── wallet-raw-call.mjs               Node.js bridge: contract calls restricted to /registry allowlist only
├── 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

Security Controls

Contract allowlist: wallet-raw-call.mjs fetches the AWP contract registry (/registry) on every invocation and rejects any --to address not present in the registry. This prevents calls to arbitrary contracts — only known AWP protocol contracts (AWPRegistry, StakeNFT, SubnetNFT, AWPDAO, AWPToken, etc.) are permitted.

Transaction confirmation: All on-chain operations require explicit user confirmation before execution (see "Agent Wallet & Transaction Safety" above).

Daemon lifecycle: awp-daemon.py writes its PID to ~/.awp/daemon.pid on start and removes it on exit. Stop it via Ctrl+C or kill $(cat ~/.awp/daemon.pid). The daemon never auto-installs software, never auto-initializes wallets, and never executes transactions — it only monitors and notifies.

Third-party skill installs: Subnet skills from non-awp-core sources require explicit user confirmation before installation.

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

Pre-Flight Checklist (before ANY write action)

1. Wallet unlocked?     → TOKEN=$(awp-wallet unlock --duration 3600 --scope transfer | python3 -c "import sys,json; print(json.load(sys.stdin)['token'])")
2. Wallet address?      → WALLET_ADDR=$(awp-wallet receive | python3 -c "import sys,json; print(json.load(sys.stdin)['eoaAddress'])")
3. Registration status? → curl -s https://tapi.awp.sh/api/address/$WALLET_ADDR/check
4. Has gas?             → awp-wallet balance --token $TOKEN

---

Query (read-only, no wallet needed)

Q1 · Query Subnet

curl -s https://tapi.awp.sh/api/subnets/{id}

Print:

[QUERY] Subnet #<id>
── subnet ────────────────────────
name:           <name>
status:         <status>
owner:          <short_address>
alpha token:    <short_address>
skills:         <uri or "none">
min stake:      <amount> AWP
──────────────────────────────────

Q2 · Query Balance

Fetch three endpoints in parallel:

curl -s https://tapi.awp.sh/api/staking/user/{addr}/balance
curl -s https://tapi.awp.sh/api/staking/user/{addr}/positions
curl -s https://tapi.awp.sh/api/staking/user/{addr}/allocations

Print:

[QUERY] Balance for <short_address>
── staking ───────────────────────
total staked:   <amount> AWP
allocated:      <amount> AWP
unallocated:    <amount> AWP

positions:
  #<id>  <amount> AWP  lock ends <date>

allocations:
  agent <short> → subnet #<id>  <amount> AWP
──────────────────────────────────

Q3 · Query Emission [DRAFT]

curl -s https://tapi.awp.sh/api/emission/current
curl -s https://tapi.awp.sh/api/emission/schedule

Print:

[QUERY] Emission
── emission ──────────────────────
epoch:          <number>
daily rate:     <amount> AWP
decay:          ~0.3156% per epoch
──────────────────────────────────

Q4 · Query Agent

curl -s https://tapi.awp.sh/api/subnets/{subnetId}/agents/{agent}

Q5 · List Subnets

curl -s "https://tapi.awp.sh/api/subnets?status=Active&page=1&limit=20"

Sort: subnets with skills first, then min_stake ascending.

[QUERY] Active subnets
── subnets ───────────────────────
#<id>  <name>        min: 0 AWP      skills: ✓
#<id>  <name>        min: 100 AWP    skills: —
──────────────────────────────────
[NEXT] Install a subnet skill: say "install skill for subnet #<id>"

Q6 · Install Subnet Skill

curl -s https://tapi.awp.sh/api/subnets/{id}/skills

For awp-core sources (github.com/awp-core/*), install directly:

[SETUP] Installing subnet #1 skill ...
[SETUP] Installed ✓

For third-party sources, show a warning and ask for confirmation before installing:

[SETUP] Subnet #5 skill source: https://github.com/other/repo
        ⚠ Third-party source — not maintained by awp-core.
        Install? (yes/no)

Install to skills/awp-subnet-{id}/.

Q7 · Epoch History [DRAFT]

curl -s "https://tapi.awp.sh/api/emission/epochs?page=1&limit=20"

---

Registration & Staking (load commands-staking.md first)

S1 · Register / Bind (FREE, gasless)

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

Delegated Mining (bind to another wallet):

python3 scripts/relay-start.py --token $TOKEN --mode agent --target <root_address>

If the wallet has ETH, use on-chain scripts instead:

python3 scripts/onchain-bind.py --token $TOKEN --target <root_address>

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.

New deposit:

python3 scripts/onchain-deposit.py --token $TOKEN --amount 5000 --lock-days 90

Add to existing position:

python3 scripts/onchain-add-position.py --token $TOKEN --position 1 --amount 1000 --extend-days 30

Withdraw (expired positions only):

python3 scripts/onchain-withdraw.py --token $TOKEN --position 1

S3 · Allocate / Deallocate / Reallocate (only after S2 deposit)

Only needed if the user has deposited AWP and wants to direct it to a specific agent+subnet.

Allocate:

python3 scripts/onchain-allocate.py --token $TOKEN --agent <addr> --subnet 1 --amount 5000

Deallocate:

python3 scripts/onchain-deallocate.py --token $TOKEN --agent <addr> --subnet 1 --amount 5000

Reallocate (move between agents/subnets):

python3 scripts/onchain-reallocate.py --token $TOKEN --from-agent <addr> --from-subnet 1 --to-agent <addr> --to-subnet 2 --amount 5000

One-click register+stake (advanced):

python3 scripts/onchain-register-and-stake.py --token $TOKEN --amount 5000 --lock-days 90 --agent <addr> --subnet 1 --allocate-amount 5000

---

Subnet Management (wallet + SubnetNFT ownership — load commands-subnet.md first)

M1 · Register Subnet (gasless)

python3 scripts/relay-register-subnet.py --token $TOKEN --name "MySubnet" --symbol "MSUB" --skills-uri "ipfs://QmHash"

M2 · Activate / Pause / Resume

python3 scripts/onchain-subnet-lifecycle.py --token $TOKEN --subnet 1 --action activate
python3 scripts/onchain-subnet-lifecycle.py --token $TOKEN --subnet 1 --action pause
python3 scripts/onchain-subnet-lifecycle.py --token $TOKEN --subnet 1 --action resume

M3 · Update Skills URI

python3 scripts/onchain-subnet-update.py --token $TOKEN --subnet 1 --skills-uri "ipfs://QmNewHash"

M4 · Set Min Stake

python3 scripts/onchain-subnet-update.py --token $TOKEN --subnet 1 --min-stake 1000000000000000000

---

Governance (wallet + StakeNFT positions — load commands-governance.md for G1/G2)

G1 · Create Proposal

Load commands-governance.md. Needs >= 1M AWP voting power.

G2 · Vote

python3 scripts/onchain-vote.py --token $TOKEN --proposal 42 --support 1 --reason "I support this"

Support: 0=Against, 1=For, 2=Abstain. The script handles position filtering and ABI encoding.

G3 · Query Proposals

curl -s "https://tapi.awp.sh/api/governance/proposals?page=1&limit=20"

G4 · Query Treasury

curl -s https://tapi.awp.sh/api/governance/treasury

---

Monitor (real-time WebSocket, no wallet needed)

W1 · Watch Events

Connect to wss://tapi.awp.sh/ws/live, subscribe to event presets:

Preset	Events (26 total)	Emoji
staking	Deposited, Withdrawn, PositionIncreased, Allocated, Deallocated, Reallocated	$
subnets	SubnetRegistered, SubnetActivated, SubnetPaused, SubnetResumed, SubnetBanned, SubnetUnbanned, SubnetDeregistered, LPCreated, SkillsURIUpdated, MinStakeUpdated	#
emission	EpochSettled, RecipientAWPDistributed, DAOMatchDistributed, GovernanceWeightUpdated, AllocationsSubmitted, OracleConfigUpdated	~
users	Bound, RecipientUpdated, DelegateGranted, DelegateRevoked	@

Display format:

$ Deposited | 0x1234...abcd deposited 5,000.0000 AWP | lock ends 2026-12-01 | https://basescan.org/tx/0xabc...
# SubnetRegistered | #12 "DataMiner" by 0x5678...efgh | https://basescan.org/tx/0xdef...
~ EpochSettled | Epoch 42 | 15,800,000.0000 AWP to 150 recipients | https://basescan.org/tx/0x123...

W2 · Emission Alert [DRAFT]

Subscribe to EpochSettled + RecipientAWPDistributed + DAOMatchDistributed.

---

Error Recovery

Error	Print	Recovery
400 Bad Request	[!] invalid request: <detail>	Check inputs
404 Not Found	[!] not found	Suggest list/search
429 Rate Limit	[!] rate limited. retrying in 60s...	Auto-retry
"not registered"	[!] not registered. say "start working"	Guide to onboarding
"insufficient balance"	[!] insufficient balance	Guide to S2
PositionExpired	[!] position expired. withdraw first.	Guide to S2
Session expired	[!] re-unlocking wallet...	Auto re-unlock
Wallet not found	[!] initializing wallet...	Agent runs awp-wallet init
WS disconnected	[WATCH] reconnecting...	Backoff reconnect