Clawlett

Clawlett

Secure token swaps and Trenches trading, powered by Safe + Zodiac Roles.

Supported chains:

• Base (Chain ID: 8453) — default. KyberSwap, CoW Protocol, Trenches, CNS.
• BNB Chain (Chain ID: 56) — KyberSwap swaps + balance checking only.

Swap engines:

• KyberSwap (DEX aggregator for optimal routes) — default, available on all chains
• CoW Protocol (MEV-protected batch auctions) — Base only

Token creation & trading: Trenches (via AgentKeyFactoryV3) — Base only.

Overview

This skill enables autonomous token swaps and Trenches token creation/trading through a Gnosis Safe. The agent operates through Zodiac Roles which restricts operations to:

• Swapping tokens via KyberSwap Aggregator (default) or CoW Protocol
• Creating tokens on Trenches (Base only)
• Buying and selling Trenches tokens via factory (Base only)
• Approving tokens for KyberSwap Router and CoW Vault Relayer
• Executing swaps via ZodiacHelpers delegatecall
• Wrapping ETH to WETH and unwrapping WETH to ETH via ZodiacHelpers
• Sending swapped tokens only back to the Safe (no draining)

All scripts accept --chain <name> (default: base). The same agent.pk is shared across chains; each chain gets its own Safe and config directory (config/<chain>/).

Execution Policy

CRITICAL: The agent MUST NEVER execute an on-chain transaction unless the user explicitly asks for it. The default behavior for any swap, token creation, or trade request is quote/preview only. The agent should show the details and wait for the user to explicitly confirm execution (e.g., "execute", "do it", "go ahead", "yes, swap").

• "Swap 0.1 ETH for USDC" → get a quote and display it, do NOT execute
• "Swap 0.1 ETH for USDC and execute" → get a quote, display it, then execute
• Showing a quote and asking "should I execute?" is fine, but the agent must wait for an affirmative response before executing

This applies to all on-chain operations: swaps, token creation, buys, sells, wrapping/unwrapping.

Capabilities

Agent Name (CNS)

Each agent can optionally register a unique name via the Clawlett Name Service (CNS). This name is the agent's app-wide identifier — no two agents can share the same name. The name is minted as an NFT on Base.

Pass --name during initialization to register a CNS name. If omitted, CNS registration is skipped. Once registered, it cannot be changed.

Token Safety

Verified Tokens

Protected tokens can ONLY resolve to verified addresses per chain.

Base Mainnet:

BNB Chain:

If a scam token impersonates these symbols, the agent will detect and warn.

Unverified Token Search

Tokens not in the verified list are searched via DexScreener (Base pairs). Search results include:

• Contract address (on-chain verified)
• 24h trading volume and liquidity
• DEX where the token trades

Agent behavior for unverified tokens:

• Always display the warning with contract address, volume, and liquidity
• Ask the user to confirm before proceeding with the swap
• Never silently swap an unverified token

Setup

1. Owner provides their wallet address (and optionally an agent name and chain)
2. Agent generates keypair → Owner sends gas to agent (at least 0.0001 native token on the target chain; 0.001 recommended)
3. Agent deploys Safe on the target chain (agent as initial owner)
4. Agent deploys Zodiac Roles module
5. Agent configures Roles permissions via MultiSend (enable module, scope targets, assign roles)
6. Agent registers with backend API
7. Agent optionally mints CNS name on-chain (if --name provided)
8. Agent transfers Safe ownership to human owner and removes itself as owner (keeps Roles access)
9. Agent registers on ERC-8004 Identity Registry and transfers identity NFT to Safe
10. Owner funds Safe on Base Mainnet with tokens to trade

Usage

Initialize

Initialize my wallet with owner 0x123...
Initialize my wallet with owner 0x123... and name MYAGENT
Initialize my wallet on BNB Chain with owner 0x123...

Check Balance

What's my balance?
How much USDC do I have?

Swap Tokens

Swap 0.1 ETH for USDC
Swap 100 USDC for ETH
Exchange 50 DAI to AERO

Two swap engines are available:

KyberSwap Aggregator (default):

• Finds optimal routes across multiple DEXs
• Native ETH supported directly (no wrapping needed)
• Best for finding the best price across fragmented liquidity
• 0.1% partner fee

CoW Protocol:

• MEV-protected batch auctions
• ETH is automatically wrapped to WETH (CoW requires ERC20s)
• Best for larger swaps where MEV protection matters
• 0.5% partner fee

To use CoW Protocol explicitly:

Swap 0.1 ETH for USDC using CoW
Use cow to swap 100 USDC for ETH

Wrap/Unwrap ETH

Wrap 0.5 ETH to WETH
Unwrap 0.5 WETH to ETH

Wrapping and unwrapping is done via ZodiacHelpers delegatecall. When swapping from ETH via CoW, wrapping is handled automatically as part of the swap transaction.

Trenches Trading

Trenches enables token creation and trading on Base. Tokens are created and traded via the AgentKeyFactoryV3 contract.

All on-chain operations go through ZodiacHelpers wrapper functions (createViaFactory, tradeViaFactory) which validate the factory address and forward calls with explicit ethValue (since msg.value doesn't work in delegatecall).

Create a token called "My Token" with symbol MTK
Create a token paired with BID (default base token)
Create a token with anti-bot disabled and an initial buy
Buy 0.01 ETH worth of MTK on Trenches
Buy 100 BID worth of CLAWLETT on Trenches
Buy all my BID into CLAWLETT
Sell all my MTK tokens
What's trending on Trenches?
Show me the top gainers
Get info on MTK token

IMPORTANT — Token creation parameter collection: When a user asks to create a token, the agent MUST collect ALL of the following parameters before executing. If the user's request is missing any of these, ask them to provide the missing values. Do NOT use defaults silently — always confirm each parameter with the user.

The agent should present the user with a summary of all parameters (including defaults) and ask for confirmation before executing the creation.

Token creation defaults:

• Base token: BID (use --base-token ETH for ETH pairing)
• Anti-bot protection: ON (10-minute sniper protection window)
• Initial buy is blocked when anti-bot is enabled (agent can't buy during protection window)
• Use --no-antibot to disable protection and allow initial buy
• Use --image to attach a custom token image (PNG/JPEG/WEBP, max 4MB)

Image upload flow:

• Images are uploaded to /api/skill/image before token creation
• The returned imageUrl is passed to the token creation API
• If image upload fails, the token creation will fail (image is required)

Anti-bot protection and buying:

• The agent cannot buy any token that has anti-bot protection currently active (within the 10-minute window after creation)
• This applies to all tokens, not just ones the agent created
• Both the client and backend enforce this — the backend will refuse to issue a swap signature for protected tokens
• Wait for the protection window to expire before buying

Token creation flow:

1. Upload token image via /api/skill/image (returns imageUrl)
2. Get creation signature from /api/skill/token/create (includes imageUrl)
3. Display token details — do NOT execute yet
4. STOP and wait for the user to explicitly confirm — do not proceed without confirmation
5. Only after user confirms: execute via Safe + Roles (ZodiacHelpers delegatecall)
6. After creation, share the token page URL: https://trenches.bid/tokens/[address]

Swap flow:

1. Resolve token symbols (with scam protection)
2. Get quote from KyberSwap (default) or CoW Protocol
3. Display swap details (quote only — do NOT execute yet):
   • Token symbols (e.g., ETH → USDC)
   • Token addresses (verified Base Mainnet contracts)
   • Input amount (what you're selling)
   • Output amount (estimated amount you'll receive)
   • Fee breakdown
4. STOP and wait for the user to explicitly ask to execute — do not proceed without confirmation
5. Only after user confirms: execute via Safe + Roles

Scripts

All scripts accept --chain <name> (default: base).

Examples

# Initialize (name is optional, registers on CNS if provided)
node scripts/initialize.js --owner 0x123...
node scripts/initialize.js --owner 0x123... --name MYAGENT
node scripts/initialize.js --chain bnb --owner 0x123...

# Check balance
node scripts/balance.js
node scripts/balance.js --token USDC
node scripts/balance.js --chain bnb --all

# Swap tokens (KyberSwap Aggregator, default - optimal routes)
node scripts/swap.js --from ETH --to USDC --amount 0.1
node scripts/swap.js --from USDC --to ETH --amount 100 --execute
node scripts/swap.js --from DAI --to AERO --amount 50 --execute --slippage 1
node scripts/swap.js --chain bnb --from BNB --to USDC --amount 0.1

# Swap tokens (CoW Protocol, MEV-protected, Base only)
node scripts/cow.js --from ETH --to USDC --amount 0.1
node scripts/cow.js --from USDC --to WETH --amount 100 --execute
node scripts/cow.js --from USDC --to DAI --amount 50 --execute --timeout 600

# With custom slippage (0-0.5 range, e.g., 0.05 = 5%)
node scripts/cow.js --from ETH --to USDC --amount 0.1 --slippage 0.03 --execute

# Trenches: Create a token (BID base token by default, anti-bot ON)
node scripts/trenches.js create --name "My Token" --symbol MTK --description "A cool token"
node scripts/trenches.js create --name "My Token" --symbol MTK --description "desc" --base-token ETH
node scripts/trenches.js create --name "My Token" --symbol MTK --description "desc" --no-antibot --initial-buy 0.01
node scripts/trenches.js create --name "My Token" --symbol MTK --description "desc" --image ./logo.png

# Trenches: Buy/sell tokens (amount is in base token: ETH or BID depending on pair)
node scripts/trenches.js buy --token MTK --amount 0.01
node scripts/trenches.js buy --token CLAWLETT --all
node scripts/trenches.js sell --token MTK --amount 1000
node scripts/trenches.js sell --token MTK --all

# Trenches: Token info and discovery
node scripts/trenches.js info MTK
node scripts/trenches.js trending
node scripts/trenches.js trending --window 1h --limit 5
node scripts/trenches.js new
node scripts/trenches.js top-volume
node scripts/trenches.js gainers
node scripts/trenches.js losers

Configuration

Config is stored per-chain in config/<chain>/wallet.json. The agent private key (config/agent.pk) is shared across all chains.

config/
  agent.pk              # shared across all chains
  base/
    wallet.json         # Base Safe, Roles, etc.
  bnb/
    wallet.json         # BNB Safe, Roles, etc.

Existing users with config/wallet.json (old flat structure) will be auto-migrated to config/base/wallet.json on first run.

Environment Variables

Contracts (Base Mainnet)

Updating

When the user says "update to latest", follow this procedure:

1. git fetch --tags origin in the clawlett repo
2. Read current version from scripts/package.json
3. Identify the latest git tag (e.g., git tag -l --sort=-v:refname | head -1)
4. Read MIGRATION_GUIDE.md for the migration path between current and latest version
5. Show the user: current version, new version, summary of changes, and whether on-chain steps are required
6. ASK the user: "Do you want to proceed with this update?" — do NOT proceed without explicit confirmation
7. If confirmed: git checkout <tag>, then walk through each migration step with the user

Some updates are code-only (just checkout the new tag). Others require on-chain transactions signed by the Safe owner (e.g., updating Roles permissions for a new ZodiacHelpers contract). The migration guide specifies which.

Security Model

1. Safe holds all funds - Agent wallet only has gas
2. Zodiac Roles restricts operations:
   • Can only interact with ZodiacHelpers
   • ZodiacHelpers scoped with allowTarget (Send + DelegateCall)
   • Can only approve tokens for CoW Vault Relayer and KyberSwap Router
3. No transfer/withdraw - Agent cannot move funds out
4. Scam protection - Common tokens resolve to verified addresses only
5. MEV protection - CoW Protocol batches orders, preventing sandwich attacks and other MEV extraction