Field guide · ERC-8004 · 8004scan.io
ERC-8004 turns an AI agent from "a wallet someone claims is theirs" into a portable onchain identity — an ERC-721 Agent ID, with reputation and validation anyone can check. This is the exact setup we used to register Muse on four chains in one evening, written so you can do the same for your own agent.
One agent wallet, four registrations. Same identity, four networks — so people on any of those chains can find and verify the same agent.
Personal AI agent · airdrop DYOR, multichain EVM work, token operations. The fluffy headphone character is the profile image on every listing.
Agent wallet (Privy): 0x0A1D2730f4Ae736Bac3D772FaB8607BFd7F650C4
Base #1166847 Arc #391488 Polygon #696 Robinhood #21484
| Chain | Chain ID | Agent ID | Registered | Status on 8004scan |
|---|---|---|---|---|
| Base | 8453 | 1166847 | Nov 6, 2026 · 18:04 GMT+7 · 0.00000426 ETH gas | Verified |
| Arc | 5042 | 391488 | Nov 6, 2026 · 18:12 GMT+7 | Verified |
| Polygon | 137 | 696 | Nov 6, 2026 · 18:12 GMT+7 | Registered · setAgentURI update pending lower gas |
| Robinhood Chain | 4663 | 21484 | Nov 6, 2026 · ~19:23 GMT+7 · ~0.00009325 ETH gas | Verified |
Verify any of them yourself: 8004scan.io — search the agent wallet. That one search is the whole point of the standard: no trust-me post, just an onchain record.
Profile refresh — 12 Nov 2026: all four profiles (Base #1166847, Arc #391488, Polygon #696, Robinhood #21484) were refreshed and synced with an updated bio and details. The canonical registration file behind every listing is published here: muse-agent.json.
EIP-8004 is a draft standard for trustless agents. It defines three registries that work together — and it is designed to sit alongside A2A agent communication, MCP tooling, and x402 payments, not replace them.
An ERC-721 NFT is your Agent ID. Portable across chains, owned by your wallet, pointed at a registration file that says who the agent is and what it does. This guide is about this registry.
Anyone who works with your agent can leave onchain feedback. Over time that becomes a public track record — the reason a stranger might trust your agent over an anonymous one.
Independent checks on the agent's work: TEE attestations, zkML proofs, staking-backed validation. Heavier machinery — you don't need it to register, but it's where serious agent work is heading.
Draft means draft. ERC-8004 is not Final yet, so the spec can still change. Registrations already minted are real ERC-721s on real chains — they don't disappear if the spec evolves — but don't treat any tooling around it as settled forever. Check 8004scan.io for the current chain list (29 chains at the time we registered).
Everything public about your agent lives in one JSON file — the agentURI points at it. Ours is the registration-v1 format from the spec. Strip the image to a hosted URL or a small data URI; don't paste megabytes of base64 into a guide, host it properly or keep it lean.
{
"type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1",
"name": "Muse",
"description": "Muse is a personal AI agent for 0xlinu. Airdrop DYOR agent: researches and verifies airdrops, tracks entries and results, and works multichain across EVM networks. Owner: 0xlinu. Agent wallet: 0x0A1D2730f4Ae736Bac3D772FaB8607BFd7F650C4 (Privy agent wallet, Base).",
"image": "https://…/muse-fluffy-logo.png",
"active": true,
"x402Support": false,
"supportedTrust": ["reputation"],
"services": [
{ "name": "DID", "version": "v1",
"endpoint": "did:pkh:eip155:8453:0x0A1D2730f4Ae736Bac3D772FaB8607BFd7F650C4" }
],
"registrations": [
{ "agentId": 1166847, "agentRegistry": "eip155:8453:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432" },
{ "agentId": 391488, "agentRegistry": "eip155:5042:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432" },
{ "agentId": 696, "agentRegistry": "eip155:137:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432" },
{ "agentId": 21484, "agentRegistry": "eip155:4663:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432" }
]
}
Field notes: registrations starts empty on your first chain — you fill each entry in after that chain mints. services is where you advertise how to reach the agent (DID, A2A, MCP, web endpoint). supportedTrust declares which trust models you claim — don't list validation until you actually have validators.
Hosted HTTPS / IPFS URL — best for most people. Put the JSON on a stable URL and use that URL as the agentURI. Easy to update later with setAgentURI.
data: URI — what we used first. Encode the whole file as data:application/json;base64,… and it lives entirely onchain. No hosting, no pinning — but every update is a new onchain transaction with the full file again.
One chain at a time. Do Base (or your cheapest chain) first, confirm it appears on 8004scan, then repeat — the process is identical everywhere because the registry is deployed at the same address on every mainnet.
Identity Registry · Mainnets: 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432
Identity Registry · Testnets: 0x8004A818BFB912233c491871b3d84c89A494BD9e
Same CREATE2 address on every supported mainnet — verify it once on the chain explorer (on Basescan it's labelled "8004: Identity Registry", token AgentIdentity (AGENT): basescan.org/address/0x8004A169…) and reuse it. Only ever register against this address. Lookalike registries are the obvious scam here.
Write the JSON above with your agent's name, description, image, and services. Leave registrations as [] for the first chain. Publish it and copy the URL — or build the data URI:
# turn the file into a data URI (our first agentURI)
base64 -w0 muse-agent.json | sed 's|^|data:application/json;base64,|' > muse-agent-data-uri.txt
cat muse-agent-data-uri.txt
Send a small amount of the chain's native token to the agent wallet itself (not to the address that will "help" register — remember the rule). On Base, well under 0.001 ETH covers registration many times over. On Polygon you'll need POL; on Arc, USDC is the native gas token.
Polygon warning from our run: gas there spiked to 232–255 gwei, and a later setAgentURI update needs roughly 4M gas. Register when gas is calm, or be ready to wait — our Polygon profile update is still queued for ≤40 gwei rather than overpaying.
One transaction mints the Agent ID. Two ways to send it:
Route A — explorer (you sign in your wallet): Open the registry on the chain explorer → Write Contract → connect the agent wallet → register → paste your agentURI → confirm. Best for a first, human-checked registration.
Route B — agent sends it (what we did, via the Privy CLI): The agent prepares the exact call and you review it before it goes:
# restore the pinned machine identity first (see the Privy wallet guide),
# then send register(agentURI) to the Identity Registry on Base (8453)
privy-agent-wallet rpc --json '{ "method": "eth_sendTransaction", "caip2": "eip155:8453", "params": { "transaction": { "to": "0x8004A169FB4a3325136EB29fA0ceB6D2e539a432", "chainId": 8453, "data": "<register(agentURI) calldata>" }} }'
The calldata is just the ABI encoding of register(string) with your URI — any ABI tool or explorer's read/write UI will generate it. Double-check to is the canonical registry before confirming. Registration moves no funds except gas.
The Registered event in the transaction receipt carries your new agentId. That number is the identity — Base gave us 1166847, Robinhood Chain gave us 21484. Save it with the chain ID and the transaction; you'll need the exact pair for the next step.
Add the new entry to registrations in your JSON:
{ "agentId": 1166847, "agentRegistry": "eip155:8453:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432" }
Republish the file. If your agentURI is a hosted URL and the content changed in place, you're done. If it's a data URI (or the URL changed), call setAgentURI(agentId, newURI) from the owner wallet — we verified the tokenURI matched after doing this on Base and Robinhood Chain, and confirmed success on Arc.
Then check yourself the way a stranger would: search your wallet on 8004scan.io and confirm the name, image, and description render correctly. If 8004scan can't read it, nobody else can either — fix the file, not the listing.
November 6, 2026 (GMT+7), the same evening the Privy agent wallet was funded. Registrations followed funding by about an hour.