Base 8004
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a coherent instruction-only guide for registering an agent on Base, but it involves private-key handling, funding a wallet, and irreversible onchain actions that users should treat carefully.
Before using this skill, verify the official ERC-8004 Identity Registry address, use a fresh wallet with only the funds needed for registration, protect the private key carefully, and review any agent metadata or service endpoints because they may become public and persistent onchain.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the private key is exposed, someone else could spend funds in that wallet or control the registered agent identity.
The skill instructs the user to store a wallet private key, which is expected for signing Base transactions but gives whoever has the key control over the wallet and onchain identity.
AGENT_PRIVATE_KEY=0x...your_private_key_here...
Use a fresh low-value wallet, keep the .env file out of source control, avoid sharing the key in chat or logs, and consider a secret manager or hardware wallet for higher-value use.
Running the transaction will spend Base ETH for gas and create public onchain state for the agent registration.
The instructions send a Base mainnet contract transaction. This is aligned with the registration purpose, but blockchain transactions are irreversible and spend gas.
const hash = await walletClient.writeContract({ address: IDENTITY_REGISTRY, abi: registerAbi, functionName: "register", args: [uri] });Verify the contract address, registration metadata, chain, and gas estimate before signing or broadcasting the transaction.
Installing packages from npm brings in third-party code that runs in the user's development environment.
The skill asks users to install an unpinned npm package. This is normal for a viem-based blockchain tutorial, but it is still a dependency supply-chain consideration.
npm install viem
Install from a trusted project directory, consider pinning a known viem version, and use normal package-lock/audit practices.
Publicly listed agent endpoints may receive traffic from unknown parties or agents if they are deployed.
The registration metadata can publish A2A or MCP service endpoints for discovery. This is part of the stated purpose, but it makes those endpoints public.
services: [{ name: "A2A", endpoint: "https://your-agent.example.com/a2a" }, { name: "MCP", endpoint: "https://your-agent.example.com/mcp" }]Only publish endpoints intended to be public, and protect real A2A or MCP services with appropriate authentication, authorization, rate limits, and logging.