agenticweb.wiki

ERC-8004: Trustless Agents

Last checked · 42 primary sources

For the minimal multi-token agent registry standard built on ERC-6909 and ERC-8048, see ERC-8122 [29]. For the on-chain job-escrow and evaluator-attestation protocol that composes with ERC-8004, see ERC-8183 [32]. For the AI agent risk-scoring verification standard on Ethereum, see ERC-8126.

Overview

ERC-8004 (Trustless Agents) is a Draft Standards Track Ethereum Request for Comment (eip: 8004) created on 13 August 2025 by Marco De Rossi (MetaMask), Davide Crapis (Ethereum Foundation), Jordan Ellis (Google), and Erik Reppel (Coinbase) [1][2][7][10]. Its abstract states: "This protocol proposes to use blockchains to discover, choose, and interact with agents across organizational boundaries without pre-existing trust, thus enabling open-ended agent economies." [1]. Rather than mandating a single verification mechanism for every interaction, the specification declares that "Trust models are pluggable and tiered, with security proportional to value at risk, from low-stake tasks like ordering pizza to high-stake tasks like medical diagnosis. Developers can choose from different trust models: reputation systems using client feedback, validation via stake-secured re-execution, zero-knowledge machine learning (zkML) proofs, or trusted execution environment (TEE) oracles." [1]. In the Motivation section, the authors position ERC-8004 as the discovery and trust layer missing from existing agent communication protocols: "Model context protocol (MCP) allows servers to list and offer their capabilities (prompts, resources, tools, and completions), while Agent2Agent (A2A) handles agent authentication, skills advertisement via AgentCards, direct messaging, and complete task-lifecycle orchestration. However, these agent communication protocols don't inherently cover agent discovery and trust." [1]. Payment settlement is kept separate from registry state; as the specification notes, "Payments are orthogonal to this protocol and not covered here. However, examples are provided showing how x402 payments can enrich feedback signals." [1].

The proposal was opened by Davide Crapis on 13 August 2025 in ethereum/ERCs Pull Request #1170 (Add ERC: Trustless Agents), opened for community discussion on the Fellowship of Ethereum Magicians on 14 August 2025 ("name":"Davide Crapis","username":"davidecrapis.eth","avatar_template":"/user_avatar/ethereum-magicians.org/davidecrapis.eth/{size}/6126_2.png","created_at":"2025-08-14T05:20:32.541Z"), and merged by lightclient on 18 August 2025 ("lightclient merged 12 commits into ethereum:master") [3][5]. In the ethereum/ERCs commit history for ERCS/erc-8004.md, the initial August 2025 draft (d30865a7) listed three authors (De Rossi, Crapis, and Ellis) before Erik Reppel joined as a co-author; commit cb7ae283 on 8 October 2025 moved the proposal to Review, commit acf085cb on 13 January 2026 ("sha": "acf085cb8411e5da26346aec3b67884dbea9b2a0", "node_id": "C_kwDOJvfjJNoAKGFjZjA4NWNiODQxMWU1ZGEyNjM0NmFlYzNiNjc4ODRkYmVhOWIyYTA", "commit": { "author": { "name": "Sam Wilson", "email": "57262657+SamWilsn@users.noreply.github.com", "date": "2026-01-13T19:32:44Z" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "date": "2026-01-13T19:32:44Z" }, "message": "Update erc-8004.md (#1470)") returned status to Draft alongside major schema revisions, and commit 503591a6 on 25 January 2026 ("sha": "503591a6e80e6e1affdd6403341e25269141f046", "node_id": "C_kwDOJvfjJNoAKDUwMzU5MWE2ZTgwZTZlMWFmZmRkNjQwMzM0MWUyNTI2OTE0MWYwNDY", "commit": { "author": { "name": "Marco De Rossi", "email": "marco.derossi@consensys.net", "date": "2026-01-25T18:11:58Z" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "date": "2026-01-25T18:11:58Z" }, "message": "Update ERC-8004: Updates from community feedback) recorded pre-launch updates from community feedback [4]. On 28 January 2026, the project portal (8004.org) announced: "Today, ERC-8004, the standard for Trustless Agents, is officially live on Ethereum mainnet." [10]. Because EIP editorial status and contract deployment are independent, ERC-8004's Identity and Reputation registries operate in production on mainnet while the canonical specification remains a Draft ERC [1][2][10][38].

ERC-8004 specifies three per-chain singleton registries [1][7]:

  1. Identity Registry (ERC721URIStorage): The specification defines the first registry as "Identity Registry - A minimal on-chain handle based on ERC-721 with URIStorage extension that resolves to an agent's registration file, providing every agent with a portable, censorship-resistant identifier." [1]. Every registered agent is globally identified across chains by the pair (agentRegistry, agentId), where agentRegistry is formatted as {namespace}:{chainId}:{identityRegistry} (for example, eip155:1:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 on Ethereum mainnet) and agentId is the incrementally assigned ERC-721 tokenId [1][7]. Calling register(string agentURI, MetadataEntry[] metadata), register(string agentURI), or register() mints the NFT and emits Registered(uint256 indexed agentId, string agentURI, address indexed owner), while setAgentURI(uint256 agentId, string newURI) updates the registration URI and emits URIUpdated [1]. The contract also exposes arbitrary key-value bytes storage via getMetadata and setMetadata, with one cryptographically protected key: "The key agentWallet is reserved and cannot be set via setMetadata() or during register() (including the metadata array overload). It represents the address where the agent receives payments and is initially set to the owner's address." [1]. Updating agentWallet requires calling setAgentWallet(uint256 agentId, address newWallet, uint256 deadline, bytes signature) backed by an EIP-712 signature (for externally owned accounts) or ERC-1271 validation (for smart-contract wallets), and "When the agent is transferred, agentWallet is automatically cleared (effectively resetting it to the zero address) and must be re-verified by the new owner." [1].

  2. Agent Registration JSON and /.well-known/agent-registration.json: An agent's agentURI resolves via HTTPS, IPFS (ipfs://...), or an on-chain base64 data:application/json;base64,... URI to a registration document whose schema header begins "type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1", "name": "myAgentName", "description": "A natural language description of the Agent, which MAY include what it does, how it works, pricing, and interaction methods" [1]. The document contains name, description, image, a customizable services array advertising endpoints such as web, A2A (pointing to an AgentCard), MCP, OASF (listing Open Agentic Schema Framework skills and domains), ENS, DID, email, or agentWallet, boolean flags x402Support and active, a registrations array binding {"agentId", "agentRegistry"} back to the on-chain token, and an optional supportedTrust array (["reputation", "crypto-economic", "tee-attestation"]) [1][8]. As the specification states, "Agents SHOULD have at least one registration (multiple are possible), and all fields in the registration are mandatory. The supportedTrust field is OPTIONAL. If absent or empty, this ERC is used only for discovery, not for trust." [1]. When a service endpoint points to an HTTPS domain not already serving the primary agentURI, the agent owner can prove domain control by hosting https://{endpoint-domain}/.well-known/agent-registration.json: "Users MAY treat the endpoint-domain as verified if the file is reachable over HTTPS and includes a registrations entry whose agentRegistry and agentId match the on-chain agent;" [1][8].

  3. Reputation Registry and Validation Registry: The Reputation Registry is linked to the Identity Registry via initialize(address identityRegistry_) and records client evaluations ("ERC-8004 is not a reputation system or algorithm: it is a standard for storing reputation data in a public registry (so it becomes a public good), so that it can be used by anyone building platforms, systems, or reputation algorithms.") [1][11]. Under the specification, "The feedback given by a clientAddress to an agent consists of a signed fixed-point value (int128) and its valueDecimals (uint8, 0-18), plus optional tag1 and tag2 (left to developers' discretion to provide maximum on-chain composability and filtering), an endpoint URI, a file URI pointing to an off-chain JSON containing additional information, and its KECCAK-256 file hash to guarantee integrity." [1]. Feedback is submitted via giveFeedback(agentId, value, valueDecimals, tag1, tag2, endpoint, feedbackURI, feedbackHash), which enforces self-review prevention: "The agentId must be a validly registered agent. The valueDecimals MUST be between 0 and 18. The feedback submitter MUST NOT be the agent owner or an approved operator for agentId." [1]. On-chain storage retains value, valueDecimals, tag1, tag2, isRevoked, and the 1-indexed feedbackIndex, while emitting endpoint, feedbackURI, and feedbackHash in NewFeedback events [1]. Clients can call revokeFeedback and any party can call appendResponse [1]. For on-chain aggregation via getSummary(agentId, clientAddresses, tag1, tag2), the specification mandates caller-supplied reviewer filtering: "clientAddresses MUST be provided (non-empty); results without filtering by clientAddresses are subject to Sybil/spam attacks." [1]. The third component, the Validation Registry, is defined as follows: "This registry enables agents to request verification of their work and allows validator smart contracts to provide responses that can be tracked on-chain." [1]. It specifies validationRequest(validatorAddress, agentId, requestURI, requestHash) and validationResponse(requestHash, response, responseURI, responseHash, tag) with uint8 response values from 0 to 100 [1]. However, both the official reference repository (erc-8004/erc-8004-contracts) and the project portal explicitly note that only the Identity and Reputation registries are deployed on mainnet: "The Validation Registry portion of the ERC-8004 spec is still under active update and discussion with the TEE community. This section will be revised and expanded in a follow-up spec update later this year." [7], and "Note: the Validation Registry is still undergoing technical due diligence and is not yet available." [11].

In its Security Considerations section, ERC-8004 highlights two structural boundaries of an open on-chain registry [1]. First, because registration and feedback submission are permissionless, "Sybil attacks are possible, inflating the reputation of fake agents. The protocol's contribution is to make signals public and use the same schema." [1]. Second, even when an HTTPS domain is bound via /.well-known/agent-registration.json, "it cannot cryptographically guarantee that advertised capabilities are functional and non-malicious." [1]. Around the same period, several adjacent ERCs emerged to address related layers or alternative design trade-offs: Prem Makeig's Draft ERC-8122 (Minimal Agent Registry, created 17 December 2025) observes that "ERC-8004 provides an existing agent registry standard, but it defines a singleton registry—one per chain. A registry standard that supports custom deployments is necessary for specialized use cases," and therefore "This protocol proposes a lightweight onchain registry for discovering AI agents using ERC-6909 as the underlying registry design, ERC-7930 for cross-chain agent identification, and ERC-8048 for onchain metadata." [29]; Makeig and Rafael Abuawad's Draft ERC-8048 (Onchain Metadata for Token Registries, created 30 September 2025) states "This ERC defines an onchain metadata standard for multi-token and NFT registries including ERC-721, ERC-1155, and ERC-6909. The standard provides a key-value store allowing for arbitrary bytes to be stored onchain." and defines an ERC-721T agent metadata profile (endpoint[mcp], endpoint[a2a], endpoint[web], endpoint[x402]) [30]; and Davide Crapis, Bryan Lim, Tay Weixiong, and Chooi Zuhwa's Draft ERC-8183 (Agentic Commerce, created 25 February 2026) specifies a four-state escrowed job lifecycle ("This specification defines the Agentic Commerce Protocol: a job with escrowed budget, four states (Open → Funded → Submitted → Terminal), and an evaluator who alone may mark the job completed.") whose rationale states: "ACP remains the payment and escrow layer; ERC‑8004 is the identity and reputation layer." [32]. A January 2026 governance discussion in ethcatherders/EIPIP Issue #399 regarding authorship credit for on-chain metadata in ERC-8004 concluded without changing the four-author list, with ERC editor Sam Wilson noting that "In the ERC process, practically everything boils down to author discretion. We don't have a policy around attribution/recognition" and co-author Marco De Rossi stating that "The text of the 8004 spec was written entirely by the four authors, including the Onchain Metadata section" [31].

Who uses it

ERC-8004 is used in production by the official multi-chain singleton contract deployments, by autonomous agent services publishing live /.well-known/agent-registration.json files over HTTPS to bind their service domains to on-chain agentId tokens, and by agent-commerce platforms that mint ERC-8004 identities and write on-chain reviews for registered agents [7][13][15][17][19][21]:

Who reads it

On-chain IdentityRegistry and ReputationRegistry events, off-chain agentURI registration JSONs, and /.well-known/agent-registration.json domain-verification endpoints are consumed by multi-chain explorers, trust-scoring MCP servers, and TypeScript/Python/TEE agent SDKs [8][9][11][12][22][23][24][25][26][27][28]:

Recent coverage

See also

References

  1. Marco De Rossi, Davide Crapis, Jordan Ellis & Erik Reppel — ERC-8004: Trustless Agents, Ethereum Improvement Proposals (created 13 Aug 2025; Draft Standards Track ERC): "This protocol proposes to use blockchains to discover, choose, and interact with agents across organizational boundaries without pre-existing trust, thus enabling open-ended agent economies." "Trust models are pluggable and tiered, with security proportional to value at risk, from low-stake tasks like ordering pizza to high-stake tasks like medical diagnosis. Developers can choose from different trust models: reputation systems using client feedback, validation via stake-secured re-execution, zero-knowledge machine learning (zkML) proofs, or trusted execution environment (TEE) oracles." "Model context protocol (MCP) allows servers to list and offer their capabilities (prompts, resources, tools, and completions), while Agent2Agent (A2A) handles agent authentication, skills advertisement via AgentCards, direct messaging, and complete task-lifecycle orchestration. However, these agent communication protocols don't inherently cover agent discovery and trust." "Payments are orthogonal to this protocol and not covered here. However, examples are provided showing how x402 payments can enrich feedback signals." "Identity Registry - A minimal on-chain handle based on ERC-721 with URIStorage extension that resolves to an agent's registration file, providing every agent with a portable, censorship-resistant identifier." "The key agentWallet is reserved and cannot be set via setMetadata() or during register() (including the metadata array overload). It represents the address where the agent receives payments and is initially set to the owner's address." "When the agent is transferred, agentWallet is automatically cleared (effectively resetting it to the zero address) and must be re-verified by the new owner." ""type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1", "name": "myAgentName", "description": "A natural language description of the Agent, which MAY include what it does, how it works, pricing, and interaction methods"" "Agents SHOULD have at least one registration (multiple are possible), and all fields in the registration are mandatory. The supportedTrust field is OPTIONAL. If absent or empty, this ERC is used only for discovery, not for trust." "Users MAY treat the endpoint-domain as verified if the file is reachable over HTTPS and includes a registrations entry whose agentRegistry and agentId match the on-chain agent;" "The feedback given by a clientAddress to an agent consists of a signed fixed-point value (int128) and its valueDecimals (uint8, 0-18), plus optional tag1 and tag2 (left to developers' discretion to provide maximum on-chain composability and filtering), an endpoint URI, a file URI pointing to an off-chain JSON containing additional information, and its KECCAK-256 file hash to guarantee integrity." "The agentId must be a validly registered agent. The valueDecimals MUST be between 0 and 18. The feedback submitter MUST NOT be the agent owner or an approved operator for agentId." "clientAddresses MUST be provided (non-empty); results without filtering by clientAddresses are subject to Sybil/spam attacks." "This registry enables agents to request verification of their work and allows validator smart contracts to provide responses that can be tracked on-chain." "Sybil attacks are possible, inflating the reputation of fake agents. The protocol's contribution is to make signals public and use the same schema." "it cannot cryptographically guarantee that advertised capabilities are functional and non-malicious." — https://eips.ethereum.org/EIPS/eip-8004
  2. ethereum/ERCs — ERCS/erc-8004.md raw Markdown source (master branch): "eip: 8004 title: Trustless Agents description: Discover agents and establish trust through reputation and validation author: Marco De Rossi (@MarcoMetaMask), Davide Crapis (@dcrapis) <davide@ethereum.org>, Jordan Ellis <jordanellis@google.com>, Erik Reppel <erik.reppel@coinbase.com> discussions-to: https://ethereum-magicians.org/t/erc-8004-trustless-agents/25098 status: Draft type: Standards Track category: ERC created: 2025-08-13 requires: 155, 712, 721, 1271" — https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-8004.md
  3. Davide Crapis (dcrapis) — Add ERC: Trustless Agents by dcrapis · Pull Request #1170 · ethereum/ERCs · GitHub (opened 13 Aug 2025; merged 18 Aug 2025): "lightclient merged 12 commits into ethereum:master" — https://github.com/ethereum/ERCs/pull/1170
  4. GitHub REST API — Commit history for ERCS/erc-8004.md in ethereum/ERCs (2025-08-18 through 2026-01-25): ""sha": "acf085cb8411e5da26346aec3b67884dbea9b2a0", "node_id": "C_kwDOJvfjJNoAKGFjZjA4NWNiODQxMWU1ZGEyNjM0NmFlYzNiNjc4ODRkYmVhOWIyYTA", "commit": { "author": { "name": "Sam Wilson", "email": "57262657+SamWilsn@users.noreply.github.com", "date": "2026-01-13T19:32:44Z" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "date": "2026-01-13T19:32:44Z" }, "message": "Update erc-8004.md (#1470)"" ""sha": "503591a6e80e6e1affdd6403341e25269141f046", "node_id": "C_kwDOJvfjJNoAKDUwMzU5MWE2ZTgwZTZlMWFmZmRkNjQwMzM0MWUyNTI2OTE0MWYwNDY", "commit": { "author": { "name": "Marco De Rossi", "email": "marco.derossi@consensys.net", "date": "2026-01-25T18:11:58Z" }, "committer": { "name": "GitHub", "email": "noreply@github.com", "date": "2026-01-25T18:11:58Z" }, "message": "Update ERC-8004: Updates from community feedback" — https://api.github.com/repos/ethereum/ERCs/commits?path=ERCS/erc-8004.md&per_page=100
  5. Davide Crapis (davidecrapis.eth) — Fellowship of Ethereum Magicians thread #25098 JSON feed, ERC-8004: Trustless Agents (14 Aug 2025): ""name":"Davide Crapis","username":"davidecrapis.eth","avatar_template":"/user_avatar/ethereum-magicians.org/davidecrapis.eth/{size}/6126_2.png","created_at":"2025-08-14T05:20:32.541Z"" — https://ethereum-magicians.org/t/erc-8004-trustless-agents/25098.json
  6. erc-8004/erc-8004-contracts — GitHub - erc-8004/erc-8004-contracts: Registry contracts curated by the 8004 team · GitHub: "Implementation of the ERC-8004 protocol for agent discovery and trust through reputation and validation." — https://github.com/erc-8004/erc-8004-contracts
  7. erc-8004/erc-8004-contracts — README.md raw Markdown (master branch; contract addresses and architecture): "ERC-8004 is a community effort coordinated by Marco De Rossi (MetaMask) and Davide Crapis (EF), with the co-authorship of Jordan Ellis (Google) and Erik Reppel (Coinbase)." "IdentityRegistry: 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 ReputationRegistry: 0x8004BAa17C55a88189AE136b182e5fdA19dE9b63" "The Validation Registry portion of the ERC-8004 spec is still under active update and discussion with the TEE community. This section will be revised and expanded in a follow-up spec update later this year." — https://raw.githubusercontent.com/erc-8004/erc-8004-contracts/master/README.md
  8. erc-8004/best-practices — Agent Registration Guide (Registration.md): "Think of your registration as your agent's business card that will be displayed across all ERC-721 compatible applications, explorers, and marketplaces." "Many agents advertised on-chain are not reachable and don't work anymore – maybe they were just tests. While we'll probably create watchtower services to monitor and advertise reachability in the future, but it's nice to keep active = false (or unset) until you're ready for prime time!" — https://raw.githubusercontent.com/erc-8004/best-practices/main/Registration.md
  9. erc-8004/best-practices — Agent Reputation Guide (Reputation.md): "ERC-8004 provides a public good information layer for agent feedback: a standard way to publish and retrieve feedback signals. It is up to each project (explorer, marketplace, indexer, insurer, auditor network, etc.) to build the algorithms and UX that filter, rank, weight, and display this data." — https://raw.githubusercontent.com/erc-8004/best-practices/main/Reputation.md
  10. 8004.org — 8004 - Trustless Autonomous Agents on Open Protocols, "Welcome to ERC-8004 and the open agentic economy" (28 Jan 2026): "Today, ERC-8004, the standard for Trustless Agents, is officially live on Ethereum mainnet." "During three months on testnet, the ecosystem registered 10,000+ agents and exchanged 20,000+ feedback entries. Community-built scanners, SDKs, and tooling emerged organically. The contracts have been audited by Cyfrin, Nethermind, and the Ethereum Foundation Security Team." "The Validation registry isn't currently on Mainnet and will be deployed in the following weeks with its own deep dive." — https://www.8004.org/blog/welcome-to-8004
  11. 8004.org — 8004 - Trustless Autonomous Agents on Open Protocols, Learn / FAQ page: "In one sentence: it is an agent discovery and trust protocol." "ERC-8004 is not a reputation system or algorithm: it is a standard for storing reputation data in a public registry (so it becomes a public good), so that it can be used by anyone building platforms, systems, or reputation algorithms." "Note: the Validation Registry is still undergoing technical due diligence and is not yet available." — https://www.8004.org/learn
  12. 8004.org — 8004 - Trustless Autonomous Agents on Open Protocols, Build AI Agents With ERC-8004: "Learn how to build on-chain Trustless Agents using the ERC-8004 standard. Give your agents identity, trust, verifiability on Ethereum." — https://www.8004.org/build
  13. anchor-x402 — Live ERC-8004 domain-verification and registration-v1 file (/.well-known/agent-registration.json, checked 29 Oct 2026): ""type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1", "name": "anchor-x402"," ""agentId": 47261, "agentRegistry": "eip155:8453:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432"" — https://anchor-x402.com/.well-known/agent-registration.json
  14. Christopher Ferjo — anchor-x402 — 18 x402-paid services for AI agents: "anchor-x402 is eighteen stateless x402 endpoints that any AI agent can call and pay for in a single round-trip." — https://anchor-x402.com/
  15. Producer by Suede Labs — Live ERC-8004 registration-v1 file (/.well-known/agent-registration.json, checked 29 Oct 2026): ""type":"https://eips.ethereum.org/EIPS/eip-8004#registration-v1","name":"Producer by Suede Labs","description":"Agent-commerce readiness desk for ACP and x402. Scores any agent, app, business, token, or service for agent-commerce readiness and sells the same engine as fixed-price USDC jobs: quick score, performance audit, offer optimization, agent setup, market arbitrage report, x402 promotion plan, and buyer growth list. Settled in USDC on Base."" ""registrations":[{"agentId":58592,"agentRegistry":"eip155:8453:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432"}],"supportedTrust":["reputation"]" — https://perform.suedeai.ai/.well-known/agent-registration.json
  16. Suede Labs — Suede ACP/x402 Performance Engine: "The Suede Performance Engine is a free 60-second test that scores whether your business is ready to sell to AI agents over ACP and x402." — https://perform.suedeai.ai/
  17. Clicks Protocol — Live ERC-8004 domain-verification file (/.well-known/agent-registration.json, checked 29 Oct 2026): ""name": "Clicks Protocol", "description": "Agent Commerce Settlement Router on Base." ""agentRegistry": "0x8004A169FB4a3325136EB29fA0ceB6D2e539a432", "agentId": "45074", "chain": "base", "chainId": 8453, "txHash": "0x76123d72379d35251c35747cbb8f43e09893d57501d9f4ba0f4e75d4aec296d6"" — https://clicksprotocol.xyz/.well-known/agent-registration.json
  18. Clicks Protocol — Clicks Protocol — Agent Commerce Settlement Router: "Route submitted USDC into liquid working capital" — https://clicksprotocol.xyz/
  19. CompraBTC — Live ERC-8004 minimal registrations domain-verification file (/.well-known/agent-registration.json, checked 29 Oct 2026): ""agentId": 9665, "agentRegistry": "eip155:42220:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432"" — https://comprabtc.vercel.app/.well-known/agent-registration.json
  20. CompraBTC — CompraBTC - Ahorra en Bitcoin sin complicaciones: "CompraBTC automatiza pequeñas compras de Bitcoin, desde $0.10 USDT, directo a tu billetera y bajo tu control." — https://comprabtc.vercel.app/
  21. Virtuals Protocol — ACP Changelogs | Virtuals Protocol Whitepaper (release update 1 Feb 2026): "ERC-8004 support has been fully enabled for all agents that have completed the ACP agent registration process." "All graduated agents are automatically registered on ERC-8004. Agent identity data maintained on the platform is continuously synchronized on-chain. Any subsequent identity updates performed on the platform are reflected on ERC-8004 without manual intervention." "Agent reviews and ratings are now written directly on-chain via ERC-8004, under the corresponding agent identity." — https://whitepaper.virtuals.io/acp/acp-changelogs
  22. AltLayer — 8004scan | 8004scan explorer homepage (checked 29 Oct 2026): "Identity, reputation and validation for trustless agents across 29 chains." — https://8004scan.io/
  23. Quicknode — ERC-8004 Explorer · by Quicknode (checked 29 Oct 2026): "Search and audit AI agents, their reputations, feedback, and validations — transparently computed and reproducibly scored across multiple EVM networks." "Query ERC-8004 registrations, reputation, feedback, and validations across 32 EVM networks through a single JSON-RPC endpoint." — https://erc-8004.quicknode.com/
  24. RNWY (AI Rights Institute) — skill.md MCP server and trust-intelligence specification (version: 7.5.0): "Free trust intelligence for AI agents. MCP server with 8 tools: trust scoring, transaction risk intelligence, sybil detection, funding source analysis, coordinated review detection, sock puppet scanning, fake review detection, reviewer wallet behavior profiling, agent comparison, commerce data, and network stats. Covers ERC-8004, Olas, Virtuals, and SATI registries across 11 EVM chains + Solana" "Pass/fail trust verdict. Score, tier, badges, reasoning. Works for ERC-8004, Olas, Virtuals, SATI." — https://rnwy.com/skill.md
  25. agent0lab/agent0-ts — Agent0 SDK (README.md): "Register your AI agent on-chain with a unique identity, configure presentation fields (name, description, image), set wallet addresses, and manage trust models with x402 support" — https://raw.githubusercontent.com/agent0lab/agent0-ts/main/README.md
  26. Phala-Network/erc-8004-tee-agent — ERC-8004 TEE Agent (README.md): "AI agent with on-chain identity (ERC-8004), TEE attestation (Intel TDX), and chat interface." "GET /.well-known/agent-registration.json - Domain verification Dashboard & Registration GET /dashboard - Registration dashboard GET /developer - Chat interface GET /api/status - Agent status POST /api/register - Register on-chain" — https://raw.githubusercontent.com/Phala-Network/erc-8004-tee-agent/main/README.md
  27. ChaosChain/chaoschain — ChaosChain (README.md): "Built on open standards like ERC-8004 and x402, ChaosChain turns trust into a programmable primitive for AI agents" "RewardsDistributor V4 correctly publishes verifier consensus accuracy to ERC-8004. Both sides of reputation now populated." — https://raw.githubusercontent.com/ChaosChain/chaoschain/main/README.md
  28. Sudeep (sudeepb02/awesome-erc8004) — README.md curated resource list: "A curated list of awesome resources for ERC-8004: Trustless Agents" — https://raw.githubusercontent.com/sudeepb02/awesome-erc8004/main/README.md
  29. Prem Makeig (@nxt3d) — ERC-8122: Minimal Agent Registry, Ethereum Improvement Proposals (created 17 Dec 2025; Draft): "ERC-8004 provides an existing agent registry standard, but it defines a singleton registry—one per chain. A registry standard that supports custom deployments is necessary for specialized use cases" "This protocol proposes a lightweight onchain registry for discovering AI agents using ERC-6909 as the underlying registry design, ERC-7930 for cross-chain agent identification, and ERC-8048 for onchain metadata." — https://eips.ethereum.org/EIPS/eip-8122
  30. Prem Makeig & Rafael Abuawad — ERC-8048: Onchain Metadata for Token Registries, Ethereum Improvement Proposals (created 30 Sep 2025; Draft): "This ERC defines an onchain metadata standard for multi-token and NFT registries including ERC-721, ERC-1155, and ERC-6909. The standard provides a key-value store allowing for arbitrary bytes to be stored onchain." — https://eips.ethereum.org/EIPS/eip-8048
  31. Ethereum Cat Herders (ethcatherders/EIPIP) — Requesting guidance on authorship for PR 1477 · Issue #399 · ethcatherders/EIPIP · GitHub (20–21 Jan 2026): "In the ERC process, practically everything boils down to author discretion. We don't have a policy around attribution/recognition" "The text of the 8004 spec was written entirely by the four authors, including the Onchain Metadata section" — https://github.com/ethcatherders/EIPIP/issues/399
  32. Davide Crapis, Bryan Lim, Tay Weixiong & Chooi Zuhwa — ERC-8183: Agentic Commerce, Ethereum Improvement Proposals (created 25 Feb 2026; Draft): "This specification defines the Agentic Commerce Protocol: a job with escrowed budget, four states (Open → Funded → Submitted → Terminal), and an evaluator who alone may mark the job completed." "ACP remains the payment and escrow layer; ERC‑8004 is the identity and reputation layer." — https://eips.ethereum.org/EIPS/eip-8183
  33. Sander Lutz — Is AI the Future of Ethereum? The Network's Developers Are Banking on It - Decrypt (30 Aug 2025): "Ethereum core developer Davide Crapis has proposed ERC-8004, a standard for AI agents to discover, verify, and transact with one another." "Jordan Ellis, one of the core Google employees behind its Agent2Agent protocol, is a co-author of ERC-8004." — https://decrypt.co/337403/ai-future-ethereum-developers-banking-on-it
  34. Sander Lutz — Google Reveals AI Agent Payments Protocol Backed by Coinbase, Ethereum Foundation - Decrypt (16 Sep 2025): "ERC-8004 will support many forms of payments, but having the x402 extension helps the developer experience," — https://decrypt.co/339752/google-reveals-ai-agent-payments-protocol-coinbase-ethereum-foundation
  35. Shaurya Malwa — Ethereum unveils new rules to make AI agents trustworthy, CoinDesk (28 Jan 2026): "Ethereum developers are set to roll out ERC-8004, a new standard that gives AI software agents persistent on-chain identities and a shared framework for establishing credibility." — https://www.coindesk.com/markets/2026/01/28/ethereum-s-erc-8004-aims-to-put-identity-and-trust-behind-ai-agents
  36. Danny Park — Ethereum to launch standard for AI agent economy on mainnet this week, The Block (28 Jan 2026): "By enabling discovery and portable reputation, ERC-8004 allows AI agents to interact across organizations ensuring credibility travels everywhere," — https://www.theblock.co/news/ecosystems/2026-01-28-ethereum-ai-agentic-economy-mainnet-387345
  37. Martin Young — Ethereum AI Agent Standard ERC-8004 Launches This Week, Cointelegraph (28 Jan 2026): "ERC-8004, which a lead developer has tipped will be deployed to mainnet this week, enables AI agents to discover and trust each other across platforms without centralized gatekeepers." — https://cointelegraph.com/news/ethereum-standard-trustless-ai-agents-erc-8004-likely-mainnet-on-thursday
  38. Marko Stokić — AI Agents Gain Trust Via Ethereum: ERC-8004 On Mainnet, Forbes Digital Assets (5 Feb 2026): "ERC-8004, a draft Ethereum standard for AI agent identity and reputation, is now live on mainnet." "On January 29, 2026, the core registries were finally deployed on Ethereum mainnet, putting a reference implementation of agent identity and reputation onto the same rails that already secure trillions in value." "ERC-8004 being marked " Draft " is a reminder that the spec is still moving, even if the contracts are live." — https://www.forbes.com/sites/digital-assets/2026/02/05/ai-agents-gain-trust-via-ethereum-erc-8004-on-mainnet/
  39. CertiK — The Rise of the Agent Economy, Part 2: Security Deep Dive into EIP-8004, EIP-8183, Hooks, and Evaluators - CertiK (11 May 2026): "In Part 1 of this series, we described how EIP-8004, EIP-8183, and x402 can combine into a practical machine economy stack: identity, transaction coordination, and payment." "the contract calls _safeMint before it finishes its internal bookkeeping and event emit. Because _safeMint can invoke onERC721Received, the receiver could "hijack" the transaction mid-flight," — https://www.certik.com/blog/the-rise-of-the-agent-economy-part-2
  40. Xihan Xiong, Zelin Li, Wei Wei, Qin Wang, William Knottenbelt & Zhipeng Wang — [2606.26028] Can Trustless Agents Be Trusted? An Empirical Study of the ERC-8004 Decentralized AI Agent Ecosystem, arXiv abstract page (v1 submitted 24 Jun 2026; v3 revised 18 Oct 2026): "On the identity side, we find that most registrations are placeholders rather than active agents, with only a small fraction (3%, 4%, and 15% across Ethereum, BSC, and Base) exposing a valid ERC-8004 registration file with at least one live service endpoint." "On the reputation side, we show that the Registry, as currently deployed, cannot function as a trust signal: values are not commensurable, feedback records are rarely grounded in verifiable interactions, and reputation can be manipulated at minimal cost." "Consistent with these design weaknesses, we find that a substantial fraction of reviewers (73.5%, 59.2%, and 90.6% across Ethereum, BSC, and Base) exhibit coordinated Sybil behavior. After removing Sybil-flagged feedback, 15.8%, 77.9%, and 86.8% of rated agents, respectively, are left with no valid feedback." — https://arxiv.org/abs/2606.26028
  41. Xihan Xiong et al. — Can Trustless Agents Be Trusted? An Empirical Study of the ERC-8004 Decentralized AI Agent Ecosystem, arXiv HTML full text (arXiv:2606.26028v3): "Introduced on the Ethereum mainnet on January 29, 2026, it establishes an on-chain trust layer between agent communication protocols" "The results are striking: Sybil feedback is not concentrated in the low-evidence category but pervades all three evidence classes." — https://arxiv.org/html/2606.26028
  42. BNB Chain — BNB Chain AI Agent Landscape: Agents, Tools, and Payments - BNB Chain Blog (16 Jul 2026): "BNB Chain hosts more registered AI agents than any other network under ERC-8004, the standard for onchain agent identity: about 200,000 ERC-8004 agents, roughly 60% of all agents across 26 chains" "BNBAgent SDK, a Python toolkit now live on mainnet and the first live implementation of ERC-8183, the standard for onchain agent commerce." — https://www.bnbchain.org/en/blog/bnb-chain-ai-agent-landscape-agents-tools-and-payments

JSON · Markdown · OKF v0.2