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.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- sperax-skillsSkill
- agent-wallet-securitySkill
- ai-agent-defi-guideSkill
- airdrop-hunting-guideSkill
- arbitrum-defi-guideSkill
- chainlink-oracle-guideSkill
- cross-chain-bridge-guideSkill
- crypto-governance-guideSkill
- crypto-market-sentimentSkill
- crypto-news-aggregationSkill
- crypto-portfolio-managementSkill
- crypto-price-data-guideSkill
- crypto-tax-basicsSkill
- dca-strategy-guideSkill
- defi-dashboard-buildingSkill
- defi-lending-guideSkill
- defillama-analytics-guideSkill
- defi-risk-assessmentSkill
- defi-yield-strategiesSkill
- gas-optimization-guideSkill
- impermanent-loss-explainedSkill
- mev-protection-guideSkill
- nft-analytics-guideSkill
- onchain-analytics-guideSkill
- plutus-plsassets-guideSkill
- plutus-protocol-overviewSkill
- plutus-vaults-guideSkill
- restaking-explainedSkill
- smart-contract-reading-guideSkill
- sperax-ecosystem-overviewSkill
- sperax-farms-guideSkill
- sperax-spa-stakingSkill
- sperax-usds-guideSkill
- stablecoin-mechanicsSkill
- subgraph-development-guideSkill
- token-approval-safetySkill
- token-discovery-guideSkill
- token-swap-best-practicesSkill
- web3-glossarySkill
- whale-watching-guideSkill
- yield-vault-guideSkill
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
- Distinctive: line 27
Every agent gets an NFT identity — a unique, transferrable on-chain identity.
- Very specific: line 128
All contracts use vanity addresses starting with 0x8004...
- Distinctive: line 163
Use the ERC-8004 registries to:
- Distinctive: line 165
Check reputation before trusting
- Distinctive: line 166
Call via MCP or A2A protocols
≈ “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.
Files
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.
| Signal | Measures | Scale |
starred | Quality rating | 0–100 |
reachable | Endpoint reachable | binary |
uptime | Availability | percentage |
successRate | Task completion rate | percentage |
responseTime | Response latency | milliseconds |
tradingYield | Trading return | signed percentage |
revenues | Cumulative revenue | USD |
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
| Service | Purpose | Use When |
| MCP | Model Context Protocol | Agent exposes tools for other AI to call |
| A2A | Agent-to-Agent | Agent participates in multi-agent workflows |
| ENS | Ethereum Name Service | Human-readable agent address |
| DID | Decentralized Identifier | Cross-chain identity |
Key Operations
| Operation | Description |
registerAgent | Mint an agent NFT with metadata |
lookupAgent | Query agent details by token ID |
searchAgents | Find agents by criteria |
updateMetadata | Update agent's registration file |
transferAgent | Transfer ownership to new address |
getAgentReputation | Fetch reputation signals |
submitFeedback | Post a reputation signal |
addValidation | Add validator attestation |
getValidations | Query validations for an agent |
listAgents | List agents by owner |
Supported Chains (12)
| Chain | Networks |
| Ethereum | Mainnet, Sepolia |
| BNB Chain | Mainnet, Testnet |
| Arbitrum | Mainnet, Sepolia |
| Base | Mainnet, Sepolia |
| Optimism | Mainnet, Sepolia |
| Polygon | Mainnet, Amoy |
All contracts use vanity addresses starting with 0x8004...
Best Practices
Registration
- Always include a rich registration file with name, description, image, and services
- Declare services explicitly — other agents need to know how to communicate
- Keep metadata current — update when endpoints change
- Use active flag — set
"active": falsewhen taking agent offline
Reputation
- Encourage feedback — more signals = more trust
- Monitor your scores — respond to quality issues
- Use standard signal types — stick to the defined tags for interoperability
- Trusted probers (infra watchtowers) should regularly publish uptime/reachability
Security
- Validate callers — check msg.sender for sensitive operations
- Rate-limit feedback — prevent spam signals
- 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:
- Deploy agent registration via ERC-8004
- Advertise MCP endpoints so other agents can discover your tools
- Build reputation over time as users interact
Discover & Interact With Other Agents
Use the ERC-8004 registries to:
- Find specialized agents (e.g., "DeFi yield optimizer on Arbitrum")
- Check reputation before trusting
- 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
| Resource | URL |
| ERC-8004 Spec | https://eips.ethereum.org/EIPS/eip-8004 |
| Best Practices | https://github.com/nirholas/best-practices |
| Agent Creator UI | https://github.com/nirholas/erc8004-agent-creator |
| Demo Agent | https://github.com/nirholas/erc-8004-demo-agent |
| Solidity Contracts | https://github.com/nirholas/erc-8004-contracts |
| Subgraph | https://github.com/nirholas/subgraph |
| SperaxOS | https://sperax.io |
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
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.

