{
 "acronym": "ERC-8004",
 "adoption": {
  "by": "Forbes (2026-02-05) citing community trackers; community-maintained awesome-erc8004 deployment list",
  "level": "claimed",
  "probe_run": null
 },
 "aliases": [
  "Trustless Agents"
 ],
 "analog": "DNS plus a public review/reputation ledger",
 "collisions": [],
 "discovery": {
  "mechanism": "ERC-721 Identity Registry token (agentId) resolves via agentURI to a JSON agent registration file; optional HTTPS domain proof at a fixed well-known path",
  "path": "/.well-known/agent-registration.json"
 },
 "dispute": {
  "claims": [
   "Forbes and community trackers describe mainnet deployment as of 2026-01-29, but this is not an IETF/W3C-style finalized standard — it remains a Draft ERC.",
   "getSummary() reputation reads require an explicit non-empty clientAddresses filter specifically because unfiltered aggregation is vulnerable to Sybil/spam feedback, per the spec's own Security Considerations.",
   "An independent June 2026 study found that most on-chain registrations are not backed by a live agent (3–15% valid, live registration files) and that reputation feedback is dominated by coordinated Sybil reviewers (~90.6%), so registration counts overstate real adoption and reputation scores are not yet usable for trust decisions [4]."
  ],
  "summary": "The Validation Registry (stake/zkML/TEE-backed independent checking) is not finalized while Identity and Reputation are; adoption is reported by trackers and press, not independently counted by us. Registration counts should be read as a ceiling: the June 2026 empirical study found only 3–15% of registrations point at a live endpoint."
 },
 "evidence": [
  {
   "claim": "EIP-8004 defines three per-chain singleton registries (Identity, Reputation, Validation) and the JSON agent registration file format, including the optional /.well-known/agent-registration.json domain-verification file",
   "date": "2025-08-13",
   "label": "VERIFIED",
   "url": "https://eips.ethereum.org/EIPS/eip-8004"
  },
  {
   "claim": "Identity Registry (0x8004A169FB4a3325136EB29fA0ceB6D2e539a432) and Reputation Registry (0x8004BAa17C55a88189AE136b182e5fdA19dE9b63) deployed at identical addresses on Ethereum mainnet since 29 Jan 2026, after ~3 months of testnet use (10,000+ agents, 20,000+ feedback entries reported)",
   "date": "2026-02-05",
   "label": "VERIFIED",
   "url": "https://www.forbes.com/sites/digital-assets/2026/02/05/ai-agents-gain-trust-via-ethereum-erc-8004-on-mainnet/"
  },
  {
   "claim": "Community-maintained tracker lists the same two contract addresses deployed identically across 16+ EVM chains (Base, Arbitrum, Optimism, Polygon, etc.) and documents the Validation Registry as still under active revision, unlike the finalized Identity/Reputation contracts",
   "date": null,
   "label": "REPORTED",
   "url": "https://github.com/sudeepb02/awesome-erc8004"
  },
  {
   "claim": "Empirical study of 112,921 registrations across Ethereum, BSC and Base: only 3–15% expose a valid ERC-8004 registration file with at least one live service endpoint, and about 90.6% of reputation reviewers exhibit coordinated Sybil behaviour (Xiong et al., arXiv 2606.26028, 2026-06-24).",
   "date": "2026-06-24",
   "label": "VERIFIED",
   "url": "https://arxiv.org/abs/2606.26028"
  }
 ],
 "form": "onchain-registry",
 "governance": "Ethereum EIP process; no formal steward until finalized",
 "group": null,
 "history": [
  {
   "date": "2026-09-05",
   "note": "seeded from Exa Agent research run"
  },
  {
   "date": "2026-09-06",
   "note": "verified against EIP-8004 primary text, Forbes mainnet-launch report (2026-02-05), and community deployment tracker (awesome-erc8004)"
  },
  {
   "date": "2026-09-07",
   "note": "added the arXiv 2606.26028 empirical study on live endpoints and Sybil feedback"
  }
 ],
 "id": "erc-8004",
 "implementation": "multi-implementation",
 "last_verified": "2026-09-07",
 "name": "ERC-8004: Trustless Agents",
 "native_status": "Draft Standards Track ERC",
 "origin": {
  "date": "2025-08-13",
  "org": "Ethereum community (De Rossi, Crapis, Ellis, Reppel)"
 },
 "part_of": null,
 "parties": [
  "agent-registry",
  "agent-agent"
 ],
 "phase": "draft",
 "probe": {
  "method": "GET",
  "on_absent": "Endpoint-domain control is not proven by this optional file; the agent's core identity may still be valid via the onchain agentURI directly (a JSON file at any URI scheme, not necessarily HTTPS at this path)",
  "parse": "JSON body has a registrations[] entry whose agentRegistry (eip155:{chainId}:{identityRegistry}) and agentId match the onchain agent being checked",
  "path": "https://{endpoint-domain}/.well-known/agent-registration.json"
 },
 "question": "Who is an agent, and what onchain identity, reputation and validation record does it carry?",
 "scope": "general",
 "spec_url": "https://eips.ethereum.org/EIPS/eip-8004",
 "step": "identify",
 "summary_md": "ERC-8004 (\"Trustless Agents\") is a draft Ethereum standard that gives autonomous agents a portable, onchain identity plus pluggable trust signals, so that agents from different organizations can discover and transact with one another without a pre-existing relationship [1]. It defines three per-chain singleton registries: an Identity Registry (an ERC-721 token whose tokenURI, here called agentURI, points to a JSON registration file listing the agent's name, description and service endpoints — A2A agent cards, MCP endpoints, ENS names, DIDs, wallets); a Reputation Registry (a standard interface for clients to post signed numeric feedback, with onchain filtering by reviewer and tag to blunt Sybil attacks); and a Validation Registry (generic hooks for requesting and recording independent checks of an agent's work, e.g. by staked re-execution, zkML proofs, or TEE attestations) [1].\n\nIt solves discovery-plus-trust for cross-organizational agent economies: MCP and A2A cover how an agent is invoked and how it advertises skills, but neither defines a portable identity an unrelated party can look up and score [1]. ERC-8004 does not itself define payments (it notes x402 as a complementary, orthogonal protocol), does not prescribe how validation is actually computed (that is left to competing validator networks), and — by the authors' own admission — cannot cryptographically guarantee that an agent's advertised capabilities are functional or non-malicious; it only anchors identity and makes trust signals public and structured [1].\n\nCurrent state: still a Draft ERC (no EIP number finalization; created 2025-08-13) [1]. The Identity and Reputation Registry contracts went live on Ethereum mainnet on 2026-01-29 at deterministic addresses (0x8004A169... and 0x8004BAa1...), following roughly three months of testnet activity reported at over 10,000 registered agents and 20,000 feedback entries [2]. A community-maintained tracker shows the same two contracts redeployed at identical addresses across at least 16 EVM chains (Base, Arbitrum, Optimism, Polygon, Avalanche, and others), while listing the Validation Registry as still under active revision rather than finalized [3]. Reference implementations and a client-side verification dApp (AtlasNexus Verify) are cited by the same tracker [3].\n\nImplementers: the reference implementation repository (erc8004/reference-implementation), the coordinating site 8004.org, and independent tooling such as AtlasNexus Verify [2][3]. The EIP requires EIP-155, EIP-712, EIP-721 and EIP-1271 as building blocks [1].\n\nDisputed or unknown: adoption figures (10,000+ agents, 20,000+ feedback entries) come from press and community trackers, not a probe we ran ourselves, so we label them claimed rather than measured. It is also unresolved whether the Validation Registry will ship as specified or be substantially revised, and whether reputation aggregation across chains will be standardized or remain ad hoc per aggregator [1][3].",
 "track": "community",
 "version": {
  "date": "2025-08-13",
  "label": "Draft ERC, created 2025-08-13; Identity and Reputation Registries live on Ethereum mainnet since 2026-01-29"
 }
}