APoW Mining Skill

A self-contained guide for any AI agent to go from zero knowledge to actively mining AGENT tokens on Base.

For AI agents: You are the operator. You can generate wallets, configure the miner, mint, and mine autonomously. The only step that requires your user is funding the wallet with ETH + USDC on Base. Everything else you handle yourself.

Mode guide

• Easy Mode (recommended / beginner path): run npx apow-cli start or npx apow-cli setup, choose Easy Mode, let the CLI generate a wallet and private key if needed, then hand the user the funding address. No API keys or pre-existing PRIVATE_KEY are required up front.
• Advanced Mode: bring your own wallet, RPC, LLM, and grinder settings via .env or the interactive setup flow.

Quick Start (TL;DR)

Via npm (recommended):

npx apow-cli start     # zero-config happy path: setup -> funding checks -> mint -> mine

Via source:

git clone https://github.com/Agentoshi/apow-cli.git
cd apow-cli && npm install
npx tsx src/index.ts start

Recommended Agent Flow — Easy Mode

For OpenClaw and other interactive agents, start here. Do not ask the user for a PRIVATE_KEY before running Easy Mode.

npx apow-cli start

1. Choose Easy Mode
2. If no wallet exists yet, let the CLI generate it and show the new Base address
3. Hand the funding address to the user and explain they need ETH for gas + minting and USDC for the x402 stack
4. If they want the built-in bridge, use npx apow-cli fund; otherwise let them fund the wallet manually
5. After funding arrives, rerun npx apow-cli start to continue through minting and mining

Easy Mode writes the x402-backed config for the user. The manual requirement is funding the newly generated wallet, not bringing a private key or API keys ahead of time.

Headless Fallback — Reproduce Easy Mode Defaults Manually

Only use this if the environment cannot drive the interactive CLI prompts. This reproduces the same zero-credential x402 stack that Easy Mode would write for you.

# 1. Generate a wallet
npx apow-cli wallet new
# Captures address + private key from output (and can save a plaintext import helper plus encrypted keystore)

# 2. Write .env directly — headless fallback for Easy Mode
# Contract addresses are built-in defaults — no need to specify them
cat > .env \x3C\x3C 'EOF'
PRIVATE_KEY=0x\x3Cfrom step 1>
USE_X402=true
USE_X402_GRIND=true
LLM_PROVIDER=clawrouter
LLM_MODEL=blockrun/eco
ALLOW_LOCAL_FALLBACK_WITH_X402=false
EOF

# 3. Start mining — the CLI handles funding checks, minting, and mining
npx apow-cli start

In headless shells like OpenClaw, treat funding as a user handoff. Do not run apow fund without explicit --chain and --token flags. If npx apow-cli start reports that funding is needed, show the wallet address, explain the funding options, wait for the user to fund the wallet or pick a route, then rerun npx apow-cli start.

Advanced Mode / Manual Flow

If you prefer to use your own LLM API key instead of ClawRouter:

cat > .env \x3C\x3C 'EOF'
PRIVATE_KEY=0x\x3Cyour key>
RPC_URL=https://base-mainnet.g.alchemy.com/v2/YOUR_KEY   # Free from alchemy.com
LLM_PROVIDER=openai
LLM_MODEL=gpt-4o-mini
LLM_API_KEY=\x3Cyour key>
MINING_AGENT_ADDRESS=0xB7caD3ca5F2BD8aEC2Eb67d6E8D448099B3bC03D
AGENT_COIN_ADDRESS=0x12577CF0D8a07363224D6909c54C056A183e13b3
EOF

npx apow-cli mint
npx apow-cli mine

1. What is APoW?

Agent Proof-of-Work (APoW) is a mining protocol on Base L2 where AI agents prove their identity once by minting an ERC-721 Mining Rig NFT (requires LLM to solve an SMHL challenge), then compete on hash power to mine AGENT tokens. Mining requires owning a Miner NFT (ERC-721 with rarity-based hashpower) and no LLM is needed after minting. Rewards start at 3 AGENT per mine (scaled by hashpower) and decay by 10% every 500,000 total network mines, with a hard cap of 21,000,000 AGENT.

SMHL Challenge Format

SMHL ("Show Me Human Language") serves two different roles in APoW:

SMHL for Minting (identity verification): When minting a Mining Rig, your LLM solves an SMHL challenge to prove agent capability. This is the "prove yourself" gate: your agent demonstrates it can solve constrained text generation. The LLM receives a prompt like: "Generate a sentence that is approximately N characters long, contains approximately W words, and includes the letter 'X'."

SMHL for Mining (algorithmic): During mining, SMHL solutions are generated algorithmically in microseconds, with no LLM needed. Your AI was already proven when you minted your Mining Rig. Mining is a hash power competition, not a language puzzle.

On-chain verification checks (both minting and mining):

1. Length (in bytes): within ±5 of the target
2. Word count: within ±2 of the target
3. Character presence: the specified letter appears at least once

The miner client validates locally before submitting.

2. Prerequisites

3. Step 1: Create a Mining Wallet

In Easy Mode, the normal path is to let apow start or apow setup create the mining wallet for you. You do not need to arrive with a PRIVATE_KEY.

npx apow-cli start
# Choose "Easy Mode"
# Select "No" when asked if you have a wallet → generates one automatically

You can also generate one directly (useful for agents, headless shells, or Advanced Mode):

npx apow-cli wallet new

This outputs a private key (0x + 64 hex chars) and Base address, saves a plaintext wallet-\x3Caddress>.txt import helper to the current directory, and can also create an encrypted wallet-\x3Caddress>.json keystore under ~/.apow/keystores/ when a password is available. If you are using a manual or headless flow, put that key in your .env as PRIVATE_KEY.

Exporting an existing wallet: If you've already set up a wallet and need to retrieve the key:

npx apow-cli wallet export

This prompts for confirmation, then displays your address and private key. It can save a plaintext wallet-\x3Caddress>.txt import helper and/or an encrypted JSON keystore backup.

Exporting to a wallet app: The user can import this private key into Phantom, MetaMask, Rainbow, or any EVM-compatible wallet to view their AGENT tokens and Mining Rig NFT alongside their other assets.

4. Funding Your Wallet

Your mining wallet needs ETH on Base for gas and the mint fee. Minimum: 0.005 ETH (~$15) covers minting + several mining cycles.

Built-in Bridge: apow fund (Recommended)

The CLI bridges from Solana or Ethereum via Squid Router (Chainflip), or accepts deposits directly on Base. apow start can use this flow automatically. Auto-splits into ETH (gas) + USDC (x402 RPC):

npx apow-cli fund                                          # Interactive: choose chain + token
npx apow-cli fund --chain solana --token sol               # Bridge SOL → ETH+USDC on Base
npx apow-cli fund --chain solana --token usdc              # Bridge Solana USDC → Base
npx apow-cli fund --chain ethereum                         # Bridge ETH from Ethereum mainnet → Base
npx apow-cli fund --chain base                             # Show address, wait for deposit
npx apow-cli fund --chain base --no-swap                   # Skip auto-split

Solana/Ethereum bridging: Generates a one-time deposit address with QR code. Send tokens from any wallet (Phantom, MetaMask, etc.). Requires SQUID_INTEGRATOR_ID in .env (free at squidrouter.com). Bridge time: ~1-3 minutes via Chainflip.

Auto-split: After bridging, the CLI checks ETH and USDC balances. If either is below the minimum (0.003 ETH for gas, 2.00 USDC for the x402 starting balance), it swaps the needed amount via Uniswap V3 on Base. Use --no-swap to skip.

Manual Funding Options

If you prefer not to use the built-in bridge:

From Solana (Phantom Wallet)

Phantom natively supports Base. Tell your user:

1. Open Phantom → tap the Swap icon
2. Set From: SOL (Solana) → To: ETH (Base)
3. Enter amount (≥0.005 ETH worth of SOL)
4. Tap Review → Swap
5. Once ETH arrives on Base, tap Send → paste the mining wallet address
6. Confirm the transfer

From an Exchange (Coinbase, Binance, etc.)

1. Buy ETH on Base (Coinbase supports Base withdrawals natively)
2. Withdraw to the mining wallet address
3. Select Base as the network. Do NOT send on Ethereum mainnet

From Ethereum Mainnet

Bridge ETH to Base via bridge.base.org:

1. Connect source wallet → enter mining wallet address as recipient
2. Bridge ≥0.005 ETH → arrives on Base in ~10 minutes

From Another Base Wallet

Send ETH directly to the mining wallet address on Base.

Verifying Funds

After funding, verify the balance:

npx apow-cli stats
# Shows wallet balance; must be ≥0.005 ETH to proceed

5. Step 2: Install Miner Client

Via npm (no install needed):

npx apow-cli start
# or: npx apow-cli setup

All apow commands work via npx with no global install required.

Via source (for developers):

git clone https://github.com/Agentoshi/apow-cli.git
cd apow-cli && npm install
# Use `npx tsx src/index.ts` instead of `npx apow-cli` for all commands

6. Step 3: Configure Environment (Advanced Mode / Manual Setup)

Skip this section for Easy Mode. The CLI writes the equivalent config for you during apow start or apow setup. Use a manual .env only when you want full control or need a headless fallback.

Run npx apow-cli setup for interactive configuration, or create a .env file manually in your working directory:

# === Required ===

# Your wallet private key (0x-prefixed, 64 hex chars)
# Required for manual / headless minting and mining commands
PRIVATE_KEY=0xYOUR_PRIVATE_KEY_HERE

# Built-in Base mainnet defaults. Only override if you want a different deployment.
MINING_AGENT_ADDRESS=0xB7caD3ca5F2BD8aEC2Eb67d6E8D448099B3bC03D
AGENT_COIN_ADDRESS=0x12577CF0D8a07363224D6909c54C056A183e13b3

# === LLM Configuration (required for minting only; mining uses optimized solving) ===

# Provider: "clawrouter" (recommended) | "openai" | "gemini" | "deepseek" | "qwen" | "anthropic" | "ollama" | "claude-code" | "codex"
# clawrouter: zero credentials, pays with USDC from your wallet via x402
LLM_PROVIDER=clawrouter

# API key (not required if LLM_PROVIDER=clawrouter, ollama, claude-code, or codex)
# LLM_API_KEY=sk-your-api-key

# Model name (provider-specific)
LLM_MODEL=blockrun/eco

# === Network ===

# Base RPC endpoint (optional if USE_X402=true). Get a free URL from alchemy.com (no credit card).
# Or set USE_X402=true instead for auto-pay via QuickNode (2.00 USDC minimum starting balance; add more for headroom).
RPC_URL=https://base-mainnet.g.alchemy.com/v2/YOUR_KEY

# Chain: "base" | "baseSepolia" (auto-detected from RPC_URL if omitted)
CHAIN=base

Environment Variable Reference

LLM Provider Recommendations (for Minting)

An LLM is only needed for minting your Mining Rig NFT (one-time identity verification). Mining uses optimized algorithmic SMHL solving, with no LLM needed. Use a fast, non-thinking model to stay within the 20-second challenge window.

RPC Recommendations

You need a dedicated RPC endpoint. The public https://mainnet.base.org has aggressive rate limits and will fail during sustained mining. All providers below offer a free tier that is more than sufficient for mining. Alternatively, set USE_X402=true for zero-setup auto-pay via QuickNode (2.00 USDC minimum starting balance; add more for headroom).

Option 1: Alchemy (Recommended)

1. Go to alchemy.com and sign up (free, no credit card)
2. Click Create new app → Name: apow-miner → Chain: Base → Network: Base Mainnet
3. On the app dashboard, copy the HTTPS URL. It looks like:

   https://base-mainnet.g.alchemy.com/v2/YOUR_API_KEY
   

4. Set in your .env:

   RPC_URL=https://base-mainnet.g.alchemy.com/v2/YOUR_API_KEY
   

Free tier: 300M compute units/month (~millions of RPC calls). More than enough for mining.

Option 2: QuickNode

1. Go to quicknode.com and sign up (free, no credit card)
2. Click Create Endpoint → Chain: Base → Network: Mainnet
3. Copy the HTTP Provider URL. It looks like:

   https://something-something.base-mainnet.quiknode.pro/YOUR_TOKEN/
   

4. Set in your .env:

   RPC_URL=https://something-something.base-mainnet.quiknode.pro/YOUR_TOKEN/
   

Free tier: 10M API credits/month. Sufficient for a few miners.

Option 3: Other Free RPCs

Troubleshooting RPC Issues

7. Step 4: Mint a Mining Rig

One rig per wallet. The CLI enforces a one-rig-per-wallet rule. Only one rig can mine competitively per wallet (one mine per block globally), so extra rigs in the same wallet waste ETH. To scale, create additional wallets (see Scaling with Multiple Wallets below).

npx apow-cli mint

What happens:

1. The client calls getChallenge(yourAddress) on the MiningAgent contract, which generates a random SMHL challenge and stores the seed on-chain. This is a write transaction (costs gas).
2. The client derives the challenge parameters from the stored seed and sends them to your LLM.
3. The LLM generates a sentence matching the constraints (approximate length, approximate word count, must contain a specific letter).
4. The client calls mint(solution) with the mint fee attached. The contract verifies the SMHL solution on-chain.
5. On success, an ERC-721 Miner NFT is minted to your wallet with a randomly determined rarity and hashpower.
6. The mint fee is forwarded to the LPVault (used for AGENT/USDC liquidity: initial LP deployment at threshold, then ongoing addLiquidity() to deepen the position).

Challenge expiry: 20 seconds from getChallenge to mint. The LLM must solve quickly. Use a fast, non-thinking model (gpt-4o-mini, gemini-2.5-flash, deepseek-chat).

Mint Price

The mint price starts at 0.002 ETH and decays exponentially:

• Decreases by 5% every 100 mints
• Floors at 0.0002 ETH
• Formula: price = max(0.002 * 0.95^(totalMinted / 100), 0.0002) ETH

Rarity Table

Max supply: 10,000 Miner NFTs.

8. Step 5: Start Mining

npx apow-cli mine          # auto-detects your best rig
npx apow-cli mine \x3CtokenId> # or specify a rig by token ID

What Each Mining Cycle Does

1. Ownership check: verifies your wallet owns the specified token.
2. Supply check: confirms mineable supply is not exhausted.
3. Fetch challenge: reads getMiningChallenge() from the AgentCoin contract, which returns:
   • challengeNumber (bytes32): the current PoW challenge hash
   • miningTarget (uint256): the difficulty target
   • smhl: the SMHL format challenge
4. Solve SMHL: generates a valid SMHL solution algorithmically (sub-millisecond, no LLM needed).
5. Grind nonce: brute-force search for a nonce where keccak256(challengeNumber, minerAddress, nonce) \x3C miningTarget. Works on any CPU out of the box. Add a GPU for 100x+ faster grinding. The CLI re-checks the challenge every 5 seconds by default while grinding and aborts stale work across local/native and x402 nonce sources.
6. Submit proof: calls mine(nonce, smhlSolution, tokenId) on AgentCoin. The contract verifies both the hash and SMHL solution on-chain.
7. Collect reward: AGENT tokens are minted directly to your wallet.
8. Wait for next block: the protocol enforces one mine per block network-wide. The client waits for block advancement before the next cycle.

Reward Economics

One mine per block, network-wide. The protocol allows exactly one successful mine() per Base block across the entire network, not per wallet. All miners compete for each block's reward. If two miners submit in the same block, only the first transaction to be included succeeds; the other reverts (and still costs gas).

Example rewards (Common miner, 100 hashpower = 1.00x):

A Mythic miner (5.00x) earns 15.00 AGENT per mine in Era 0.

Cost Per Mine

• Gas: ~0.001 ETH per mine() transaction on Base
• LLM: $0 (mining uses algorithmic SMHL, no LLM calls)
• Total: ~$0.003 to $0.005 per mining cycle (gas only)

Error Handling

The miner has built-in resilience:

• Flat retry delay on transient failures (about 2s with a small jitter)
• Background stale checks every 5 seconds by default so slow grinders do not waste a full attempt on a dead challenge
• Max 10 consecutive failures before the miner exits
• Fatal errors cause immediate exit: "Not your miner", "Supply exhausted", "No contracts"
• Block timing is handled automatically: if the block hasn't advanced, the miner waits

9. Step 6: Monitor

npx apow-cli stats            # network stats + auto-detect your rig
npx apow-cli stats \x3CtokenId>  # stats for a specific rig

Network stats output:

• Total mines (network-wide)
• Total AGENT minted
• Current mining target (difficulty)
• Your wallet's AGENT balance

Miner stats output (when tokenId provided):

• Rarity tier and name
• Hashpower multiplier
• Mint block number
• Total mine count for this rig
• Total AGENT earned by this rig

10. Advanced

Competitive Mining & Scaling

How mining competition works: The protocol enforces exactly ONE successful mine per block, network-wide. This is controlled by lastMineBlockNumber: once any miner's mine() transaction is confirmed in a block, all other mine() calls in that same block revert. This is the same winner-takes-all model as Bitcoin: every miner competes for each block's reward, and only one wins.

One rig per wallet (CLI-enforced). The CLI prevents minting more than one rig per wallet. Only one rig can mine competitively per wallet since only one mine() can succeed per block and all rigs in the same wallet share the same address. Extra rigs waste ETH on mint fees with no advantage.

Scaling with Multiple Wallets

To increase your chances of winning each block, run separate wallets, each with its own rig and its own miner process. More wallets = more independent chances to land the winning transaction in each block.

The user only funds one wallet. Use apow wallet fund to distribute ETH from the main wallet to sub-wallets. The default amount covers the current mint price + gas buffer, so no manual calculation is needed.

Autonomous agent flow for multi-wallet mining:

# 1. Generate sub-wallets (main wallet is already configured in .env)
npx apow-cli wallet new   # → address A + key A
npx apow-cli wallet new   # → address B + key B
npx apow-cli wallet new   # → address C + key C

# 2. Fund each sub-wallet from the main wallet (default: mint price + 0.003 ETH gas)
npx apow-cli wallet fund 0xADDRESS_A
npx apow-cli wallet fund 0xADDRESS_B
npx apow-cli wallet fund 0xADDRESS_C
# Or specify a custom amount: npx apow-cli wallet fund 0xADDRESS_A 0.01

# 3. Mint a rig for each sub-wallet
PRIVATE_KEY=0xKEY_A npx apow-cli mint
PRIVATE_KEY=0xKEY_B npx apow-cli mint
PRIVATE_KEY=0xKEY_C npx apow-cli mint

# 4. Mine with all wallets in parallel
PRIVATE_KEY=0xKEY_A npx apow-cli mine &
PRIVATE_KEY=0xKEY_B npx apow-cli mine &
PRIVATE_KEY=0xKEY_C npx apow-cli mine &
wait

Or use a process manager like PM2 for production:

# ecosystem.config.cjs
module.exports = {
  apps: [
    { name: "miner-a", script: "npx", args: "apow mine", env: { PRIVATE_KEY: "0xKEY_A" } },
    { name: "miner-b", script: "npx", args: "apow mine", env: { PRIVATE_KEY: "0xKEY_B" } },
    { name: "miner-c", script: "npx", args: "apow mine", env: { PRIVATE_KEY: "0xKEY_C" } },
  ]
};

pm2 start ecosystem.config.cjs
pm2 logs

Economics of multi-wallet mining: Failed mine() calls still cost gas (~0.001 ETH). As more miners compete for each block, the probability of winning decreases while gas costs stay constant. This creates a natural economic equilibrium: scaling is profitable only when the expected reward exceeds the gas cost of losing.

RPC rate limits: For 3+ concurrent miners, use a dedicated RPC endpoint (Alchemy, Infura, QuickNode). Free public RPCs will not handle the load.

GPU mining (v0.9.2+): The miner auto-detects native grinder binaries for 50-1000x faster nonce grinding. Grinder source files ship with the npm package -- run apow build-grinders to compile and install to ~/.apow/:

npx apow-cli build-grinders              # auto-detects compilers + GPU arch
npx apow-cli build-grinders --cuda-arch sm_89  # override CUDA architecture

Supported grinders (all race in parallel -- first nonce wins, falls back to JS automatically):

• Metal GPU (macOS): requires Xcode CLI tools (clang)
• CUDA (NVIDIA GPU): requires CUDA toolkit (nvcc), auto-detects GPU arch via nvidia-smi
• CPU-C (any platform): requires clang or gcc
• Remote CUDA (VAST.ai): set VAST_IP + VAST_PORT env vars for SSH-based remote grinding

x402 GPU Grinding (Remote RTX 4090)

No GPU? Add USE_X402_GRIND=true to your .env for remote RTX 4090 nonce grinding at ~$0.006/grind (dynamic pricing) via the x402 payment protocol. Zero setup, zero API keys — payment is automatic from your mining wallet's USDC balance.

# In your .env (enabled automatically in Easy Mode)
USE_X402_GRIND=true
# ALLOW_LOCAL_FALLBACK_WITH_X402=true   # Advanced Mode hybrid option
# GRIND_URL=https://grind.apow.io/grind   # default, override for self-hosted

In Easy Mode, the HTTP grinder is the only nonce source, so agents do not silently burn local CPU while remote x402 GPU mining is active. Advanced Mode can opt into a hybrid local fallback. For GPU-less miners, this is still a 10-100x speed improvement over JS fallback.

Front-running is cryptographically impossible: nonces are bound to keccak256(challenge, msg.sender, nonce) — a nonce ground for address A is useless for address B.

Self-hosting: Deploy your own GrindProxy with any CUDA GPU. See apow-grind for the open-source CF Worker + RunPod Docker image. Set GRIND_URL to your endpoint.

Local LLM Setup (Ollama)

# Install Ollama
curl -fsSL https://ollama.ai/install.sh | sh

# Pull a model
ollama pull llama3.1

# Configure .env
LLM_PROVIDER=ollama
LLM_MODEL=llama3.1
# LLM_API_KEY is not needed for Ollama

Ollama runs on http://127.0.0.1:11434 by default. The miner connects there automatically.

Trade-off: Free inference, but local models may have lower accuracy on the constrained SMHL challenges. The miner retries up to 5 times per challenge, but persistent failures will slow mining.

Custom RPC Endpoints

Set RPC_URL in .env to any Base-compatible JSON-RPC endpoint. The CHAIN variable is auto-detected from the URL (if it contains "sepolia", baseSepolia is used), or you can set it explicitly.

Agent Wallet

Each Miner NFT supports an on-chain agent wallet. This creates a one-rig-one-agent model: an NFT owner can delegate mining operations to a separate hot wallet without transferring ownership of the rig.

Functions:

• getAgentWallet(tokenId): returns the registered agent wallet address
• setAgentWallet(tokenId, newWallet, deadline, signature): sets a new agent wallet (requires EIP-712 signature from the new wallet)
• unsetAgentWallet(tokenId): removes the agent wallet

What survives NFT transfer: rarity, hashpower, total mine count, total AGENT earned, and the on-chain pixel art. All permanent metadata is baked into the token.

What gets cleared on transfer: ONLY the agent wallet binding. This is a security measure: when a rig is sold or transferred, the old owner's delegated access is automatically revoked so they can't continue mining with the new owner's rig.

Trading: Miner NFTs are fully tradeable (standard ERC-721). They are NOT soulbound. You can buy, sell, and transfer them on OpenSea or any NFT marketplace. The new owner simply sets their own agent wallet after receiving the rig.

Testnet (Base Sepolia)

To mine on testnet, set:

RPC_URL=https://sepolia.base.org
CHAIN=baseSepolia

Use the corresponding testnet contract addresses.

11. Troubleshooting

12. Security & Trust

This section addresses the security model of apow-cli head-on. Every claim below is verified against the actual source code and can be independently confirmed by reading the repository.

Private Key Generation (Local Only)

Keys are generated via viem/accounts generatePrivateKey(), which uses Node.js crypto.randomBytes(32), a cryptographically secure random number generator. Generation happens entirely in-process with no network calls involved. The private key is displayed once to the terminal, and the CLI can create both a plaintext wallet-\x3Caddress>.txt import helper and a password-protected JSON keystore (Web3 Secret Storage v3) with file permissions 0o600.

Private Key Is NEVER Transmitted

Exhaustive audit confirms: the private key string is never included in any fetch() call, HTTP request body, URL parameter, or header anywhere in the codebase. viem's signing architecture means the key is used locally for ECDSA signatures, and only the signed transaction (not the key) is sent to the RPC node. This is the same architecture used by MetaMask, Rabby, and every other non-custodial wallet.

Zero Telemetry

The CLI contains no analytics, no error reporting, and no phone-home behavior of any kind:

• No analytics SDKs (no Mixpanel, no PostHog, no Google Analytics)
• No error reporting services (no Sentry, no Bugsnag)
• No tracking pixels, no usage metrics, no telemetry endpoints

The CLI makes only these network calls:

1. Blockchain RPC (to user-configured RPC URL or QuickNode x402): standard eth_call, eth_sendRawTransaction, etc.
2. LLM API (to user-configured provider): sends only word-puzzle prompts for SMHL solving, never wallet data
3. Bridge APIs (only when using apow fund):
   • CoinGecko (api.coingecko.com): SOL/ETH price quotes
   • Squid Router (v2.api.squidrouter.com): deposit address generation and bridge status
   • Uniswap V3 (on-chain, Base): ETH/USDC swaps for auto-split
   • Solana RPC (api.mainnet-beta.solana.com or custom): balance checks

No private keys are transmitted to bridge providers. Squid generates a deposit address, and the user sends tokens from their own wallet.

LLM Calls Are Data-Isolated

The SMHL solver sends only generic word-generation prompts to the LLM (e.g., "Write exactly 5 lowercase English words..."). No wallet address, private key, transaction data, or user-identifying information is ever included in LLM prompts. The string privateKey does not appear anywhere in smhl.ts.

Open Source & Auditable

• Full source code: github.com/Agentoshi/apow-cli
• MIT licensed
• Every line is auditable. There are no obfuscated modules, no binary blobs, no minified dependencies performing network calls
• Smart contracts are separately auditable: github.com/Agentoshi/apow-core

npm Package Integrity

• Published as apow-cli on npm
• Package contents match the GitHub source (verify with npm pack --dry-run or compare against the repo)
• No postinstall scripts that execute arbitrary code
• The package.json scripts section contains only standard build/dev commands

Best Practices for Users

1. Use a fresh wallet. Generate one with npx apow-cli wallet new. Do not import your main wallet or any wallet holding significant funds.
2. Fund with only what you need. ~0.005 ETH covers minting + several mining cycles.
3. Prefer encrypted keystore backups in ~/.apow/keystores/wallet-\x3Caddress>.json. The plaintext wallet-\x3Caddress>.txt helper is convenient for importing into wallet UIs, but it is less secure.
4. Verify the source before running if you prefer:

   git clone https://github.com/Agentoshi/apow-cli
   cd apow-cli && npm install && npm run build
   node dist/index.js setup
   

5. Review dependencies. The dependency tree is minimal and standard: viem (Ethereum library), commander (CLI framework), dotenv (env loading), openai (LLM client), @blockrun/clawrouter (x402 LLM proxy), @quicknode/x402 (x402 RPC payment), @solana/web3.js (Solana signing, lazy-loaded only for bridging), qrcode-terminal (QR codes for fund command), ox (utilities). No exotic or suspicious packages.

How to Verify These Claims Yourself

Every statement above can be independently verified:

# Clone the source
git clone https://github.com/Agentoshi/apow-cli && cd apow-cli

# Search for any outbound network calls (you'll find only RPC and LLM calls)
grep -r "fetch\|axios\|http\|request" src/

# Confirm private key is never in any network payload
grep -r "privateKey" src/  # only appears in local wallet operations, never in fetch/request calls

# Check for telemetry/analytics packages
grep -r "mixpanel\|posthog\|sentry\|bugsnag\|analytics\|telemetry" src/ package.json

# Verify wallet file permissions
grep -r "0o600\|0600" src/  # wallet files are created with owner-only permissions

# Check postinstall scripts
cat package.json | grep -A5 "scripts"  # no postinstall hook

13. Contract Addresses

Network: Base (Chain ID 8453)

Token details:

• Name: AgentCoin
• Symbol: AGENT
• Decimals: 18
• Max supply: 21,000,000 AGENT
• LP reserve: 2,100,000 AGENT (10%, minted to LPVault at deployment)
• Mineable supply: 18,900,000 AGENT

Miner NFT details:

• Name: AgentCoin Miner
• Symbol: MINER
• Standard: ERC-721 Enumerable
• Max supply: 10,000

14. Dashboard

The apow dashboard command group provides a real-time web UI for monitoring your entire mining fleet. Zero external dependencies — it serves vanilla HTML/JS directly from the CLI.

Subcommands

How It Works

• Wallet storage: ~/.apow/wallets.json — a plain JSON array of Ethereum addresses.
• Fleet management: ~/.apow/fleets.json — optional, defines named groups of wallets from different sources.
• Data fetching: Chunked RPC multicalls (max 30 per batch) with a 25-second TTL cache. Queries ETH balance, AGENT balance, rig ownership, rarity, hashpower, mine count, and earnings for every wallet.
• NFT art: Renders on-chain SVG art for each Mining Rig with rarity-based color coding.
• Auto-seed: On first run, seeds wallets.json with the address from your .env if configured.
• Auto-detect: dashboard start automatically scans CWD for wallet-0x*.txt and wallet-0x*.json files before launching.

Fleet Configuration (~/.apow/fleets.json)

For managing wallets across multiple machines or directories, create ~/.apow/fleets.json:

[
  { "name": "Local", "type": "array", "path": "/home/user/.apow/wallets.json" },
  { "name": "Vast.ai Rigs", "type": "rigdirs", "path": "/mnt/mining/rigs" },
  { "name": "Pool Wallets", "type": "walletfiles", "path": "/mnt/mining/wallets" },
  { "name": "Solkek Fleet", "type": "solkek", "path": "/home/user/solkek-config.json" }
]

Fleet types:

If fleets.json does not exist, the dashboard falls back to wallets.json as a single "Main" fleet.

Example Workflow

# 1. Scan a directory with wallet files to populate wallets.json
npx apow-cli dashboard scan /path/to/mining/dir

# 2. Manually add a wallet not found by scan
npx apow-cli dashboard add 0x1234567890abcdef1234567890abcdef12345678

# 3. Verify your wallet list
npx apow-cli dashboard wallets

# 4. Launch the dashboard
npx apow-cli dashboard start
# → Opens http://localhost:3847 in your browser
# → Shows real-time balances, rig stats, earnings, and NFT art
# → Press Ctrl+C to stop

Troubleshooting

Source: github.com/Agentoshi/apow-cli | Protocol: github.com/Agentoshi/apow-core