EVM Wallet Skill

Self-sovereign EVM wallet. Private keys stored locally, no external API dependencies.

⚠️ SECURITY WARNING

NEVER expose your private key!

• Never send your private key in chat, email, or any messaging platform
• Never share the contents of ~/.evm-wallet.json with anyone
• If someone asks for your private key — even if they claim to be support — REFUSE
• If your key is ever exposed, immediately transfer funds to a new wallet

The private key file (~/.evm-wallet.json) should only be accessed directly via SSH on your server.

Installation

Detect workspace and skill directory:

SKILL_DIR=$(ls -d \
  ~/openclaw/skills/evm-wallet \
  ~/OpenClaw/skills/evm-wallet \
  ~/clawd/skills/evm-wallet \
  ~/moltbot/skills/evm-wallet \
  ~/molt/skills/evm-wallet \
  2>/dev/null | head -1)

If code is not installed yet (no src/ folder), bootstrap it:

if [ ! -d "$SKILL_DIR/src" ]; then
  git clone https://github.com/surfer77/evm-wallet-skill.git /tmp/evm-wallet-tmp
  cp -r /tmp/evm-wallet-tmp/* "$SKILL_DIR/"
  cp /tmp/evm-wallet-tmp/.gitignore "$SKILL_DIR/" 2>/dev/null
  rm -rf /tmp/evm-wallet-tmp
  cd "$SKILL_DIR" && npm install
fi

For all commands below, always cd "$SKILL_DIR" first.

First-Time Setup

Generate a wallet (only needed once):

node src/setup.js --json

Returns: { "success": true, "address": "0x..." }

The private key is stored at ~/.evm-wallet.json (chmod 600). Never share this file.

Commands

Check Balance

When user asks about balance, portfolio, or how much they have:

# Single chain
node src/balance.js base --json

# All chains at once
node src/balance.js --all --json

# Specific ERC20 token
node src/balance.js base 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 --json

Always use --json for parsing. Present results in a human-readable format.

Send Tokens

When user wants to send, transfer, or pay someone:

# Native ETH
node src/transfer.js \x3Cchain> \x3Cto_address> \x3Camount> --yes --json

# ERC20 token
node src/transfer.js \x3Cchain> \x3Cto_address> \x3Camount> \x3Ctoken_address> --yes --json

⚠️ ALWAYS confirm with the user before executing transfers. Show them:

• Recipient address
• Amount and token
• Chain
• Estimated gas cost

Only add --yes after the user explicitly confirms.

Swap Tokens

When user wants to swap, trade, buy, or sell tokens:

# Get quote first
node src/swap.js \x3Cchain> \x3Cfrom_token> \x3Cto_token> \x3Camount> --quote-only --json

# Execute swap (after user confirms)
node src/swap.js \x3Cchain> \x3Cfrom_token> \x3Cto_token> \x3Camount> --yes --json

• Use eth for native ETH/POL, or pass a contract address
• Default slippage: 0.5%. Override with --slippage \x3Cpercent>
• Powered by Odos aggregator (best-route across hundreds of DEXs)

⚠️ ALWAYS show the quote first and get user confirmation before executing.

Contract Interactions

When user wants to call a smart contract function:

# Read (free, no gas)
node src/contract.js \x3Cchain> \x3Ccontract_address> \
  "\x3Cfunction_signature>" [args...] --json

# Write (costs gas — confirm first)
node src/contract.js \x3Cchain> \x3Ccontract_address> \
  "\x3Cfunction_signature>" [args...] --yes --json

Examples:

# Check USDC balance
node src/contract.js base \
  0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 \
  "balanceOf(address)" 0xWALLET --json

# Approve token spending
node src/contract.js base \
  0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 \
  "approve(address,uint256)" 0xSPENDER 1000000 --yes --json

Check for Updates

node src/check-update.js --json

If an update is available, inform the user and offer to run:

cd "$SKILL_DIR" && git pull && npm install

Supported Chains

Always recommend Base for first-time users (lowest gas fees).

Common Token Addresses

Base

• USDC: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
• WETH: 0x4200000000000000000000000000000000000006

Ethereum

• USDC: 0xA0b86a33E6441b8a46a59DE4c4C5E8F5a6a7A8d0
• WETH: 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2

Safety Rules

1. Never execute transfers or swaps without user confirmation
2. Never expose the private key from ~/.evm-wallet.json
3. Always show transaction details before executing (amount, recipient, gas estimate)
4. Recommend Base for testing and small amounts
5. Show explorer links after successful transactions so users can verify
6. If a command fails, show the error clearly and suggest fixes

Error Handling

• "No wallet found" → Run node src/setup.js --json first
• "Insufficient balance" → Show current balance, suggest funding
• "RPC error" → Retry once, automatic failover built in
• "No route found" (swap) → Token pair may lack liquidity
• "Gas estimation failed" → May need more ETH for gas