agentleFS
SperaxSperax/sperax-skills/skills/erc8004-agent-identity/SKILL.md

erc8004-agent-identity

Skill8 starsChanged 9 months agoMITView on GitHub

Complete guide to ERC-8004 — the open standard for on-chain AI agent identity, reputation, and validation. Covers agent registration as NFTs, reputation signals, validator attestations, and multi-chain deployment across 12 chains. Essential for building trustless AI agent ecosystems.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every agent gets an NFT identity — a unique, transferrable on-chain identity.

    line 27
  2. Very specific:

    All contracts use vanity addresses starting with 0x8004...

    line 128
  3. Distinctive:

    Use the ERC-8004 registries to:

    line 163
  4. Distinctive:

    Check reputation before trusting

    line 165
  5. Distinctive:

    Call via MCP or A2A protocols

    line 166

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ERC-8004 — On-Chain AI Agent Identity

ERC-8004 is an open Ethereum standard for discovering, choosing, and interacting with AI agents across organizational boundaries without pre-existing trust. It was created by the Sperax team and is deployed across 12 chains.

Spec: https://eips.ethereum.org/EIPS/eip-8004

Why ERC-8004?

As AI agents proliferate, we need a way to:

  • Discover agents across platforms (not locked in one vendor)
  • Verify agent capabilities and track record
  • Trust agents without knowing who built them
  • Pay agents via standard protocols (x402, on-chain)

ERC-8004 solves this with three on-chain registries.

The Three Registries

1. Identity Registry (ERC-721 NFT)

Every agent gets an NFT identity — a unique, transferrable on-chain identity.

  • Based on ERC-721 with URIStorage
  • TokenURI points to a JSON registration file
  • Owners can update metadata, transfer, or burn
  • One NFT = one agent identity

2. Reputation Registry

A standard interface for posting and querying feedback signals about agents.

SignalMeasuresScale
starredQuality rating0–100
reachableEndpoint reachablebinary
uptimeAvailabilitypercentage
successRateTask completion ratepercentage
responseTimeResponse latencymilliseconds
tradingYieldTrading returnsigned percentage
revenuesCumulative revenueUSD

Star ratings map to the 0–100 scale:

  • 1★ = 20, 2★ = 40, 3★ = 60, 4★ = 80, 5★ = 100

3. Validation Registry

Independent validator attestations for agent capabilities:

  • zkML proofs (zero-knowledge machine learning)
  • TEE attestations (trusted execution environment)
  • Staker validations (economic security)
  • Custom validator contracts

Agent Registration

Registration File Format

{
  "type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1",
  "name": "My Trading Agent",
  "description": "Automated yield optimizer on Arbitrum",
  "image": "https://cdn.example.com/agent-avatar.png",
  "services": [
    {
      "name": "MCP",
      "endpoint": "https://api.myagent.com/mcp",
      "version": "2025-06-18",
      "mcpTools": ["getQuote", "executeTrade"]
    },
    {
      "name": "A2A",
      "endpoint": "https://api.myagent.com/.well-known/agent-card.json",
      "version": "0.3.0",
      "a2aSkills": ["defi/yield_optimization"]
    },
    {
      "name": "ENS",
      "endpoint": "myagent.eth",
      "version": "v1"
    }
  ],
  "x402Support": true,
  "active": true
}

Service Types

ServicePurposeUse When
MCPModel Context ProtocolAgent exposes tools for other AI to call
A2AAgent-to-AgentAgent participates in multi-agent workflows
ENSEthereum Name ServiceHuman-readable agent address
DIDDecentralized IdentifierCross-chain identity

Key Operations

OperationDescription
registerAgentMint an agent NFT with metadata
lookupAgentQuery agent details by token ID
searchAgentsFind agents by criteria
updateMetadataUpdate agent's registration file
transferAgentTransfer ownership to new address
getAgentReputationFetch reputation signals
submitFeedbackPost a reputation signal
addValidationAdd validator attestation
getValidationsQuery validations for an agent
listAgentsList agents by owner

Supported Chains (12)

ChainNetworks
EthereumMainnet, Sepolia
BNB ChainMainnet, Testnet
ArbitrumMainnet, Sepolia
BaseMainnet, Sepolia
OptimismMainnet, Sepolia
PolygonMainnet, Amoy

All contracts use vanity addresses starting with 0x8004...

Best Practices

Registration

  1. Always include a rich registration file with name, description, image, and services
  2. Declare services explicitly — other agents need to know how to communicate
  3. Keep metadata current — update when endpoints change
  4. Use active flag — set "active": false when taking agent offline

Reputation

  1. Encourage feedback — more signals = more trust
  2. Monitor your scores — respond to quality issues
  3. Use standard signal types — stick to the defined tags for interoperability
  4. Trusted probers (infra watchtowers) should regularly publish uptime/reachability

Security

  1. Validate callers — check msg.sender for sensitive operations
  2. Rate-limit feedback — prevent spam signals
  3. Verify validators — ensure validator contracts are trustworthy

Use Cases for OpenClaw Agents

Register Your OpenClaw Agent On-Chain

Give your agent a verifiable identity that works across platforms:

  1. Deploy agent registration via ERC-8004
  2. Advertise MCP endpoints so other agents can discover your tools
  3. Build reputation over time as users interact

Discover & Interact With Other Agents

Use the ERC-8004 registries to:

  1. Find specialized agents (e.g., "DeFi yield optimizer on Arbitrum")
  2. Check reputation before trusting
  3. Call via MCP or A2A protocols

Build Agent Marketplaces

ERC-8004 provides the infra layer for on-chain agent marketplaces:

  • Identity (who is this agent?)
  • Reputation (is it any good?)
  • Validation (has it been audited?)
  • Discovery (how do I find it?)

Related Resources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.