{
 "id": "erc-8126",
 "name": "ERC-8126: AI Agent Verification",
 "acronym": "ERC-8126",
 "aliases": [
  "EIP-8126"
 ],
 "collisions": [],
 "step": "identify",
 "parties": [
  "agent-registry",
  "agent-agent"
 ],
 "form": "onchain-registry",
 "track": "community",
 "scope": "general",
 "question": "How can an agent registered under ERC-8004 be put through standard security checks and carry a comparable risk score?",
 "analog": "A security audit report with a credit-style score, attached to an on-chain identity",
 "origin": {
  "org": "Ethereum community (Leigh Cronian, Cybercentry; Chris Johnson, Virtuals)",
  "date": "2026-01-15"
 },
 "governance": "Ethereum EIP/ERC process (Ethereum Magicians discussion + ERCs repository); status Final",
 "native_status": "Final Standards Track ERC (moved to Last Call 2026-05-12 and to Final 2026-06-02); requires ERC-8004, which is still Draft",
 "phase": "stable",
 "implementation": "prototype",
 "adoption": {
  "level": "unmeasured",
  "by": null,
  "probe_run": null
 },
 "version": {
  "label": "Final, created 2026-01-15",
  "date": "2026-06-02"
 },
 "spec_url": "https://eips.ethereum.org/EIPS/eip-8126",
 "discovery": {
  "mechanism": "Agents are identified by their ERC-8004 Identity Registry token; verification attestations can be posted to ERC-8004's Validation Registry",
  "path": "none — no well-known file; discovery is by contract address/ABI"
 },
 "probe": {
  "method": "eth_call",
  "path": "{contract_address}",
  "parse": "Look up the agent in an ERC-8004 Validation Registry for ERC-8126 verification attestations; detailed results and the 0-100 risk score are readable only by the agent's wallet holder",
  "on_absent": "No attestation means no ERC-8126 provider has posted one for this agent; it says nothing about whether the agent is safe."
 },
 "evidence": [
  {
   "claim": "ERC-8126 defines a standard interface for verifying AI agents registered via ERC-8004, with five verification types (Ethereum Token, Media Content, Solidity Code, Web Application and Wallet Verification), zero-knowledge proofs generated by Private Data Verification, and a unified 0-100 risk score visible only to the agent's wallet holder; attestations can be posted to ERC-8004's Validation Registry. Status Final; requires 155, 191, 712, 721, 3009 and 8004; created 2026-01-15.",
   "date": "2026-06-02",
   "label": "VERIFIED",
   "url": "https://eips.ethereum.org/EIPS/eip-8126"
  },
  {
   "claim": "The ERCs repository front matter for erc-8126.md reads status: Final with requires including 8004; its commit history shows the move to Last Call on 2026-05-12 and to Final on 2026-06-02.",
   "date": "2026-06-02",
   "label": "VERIFIED",
   "url": "https://github.com/ethereum/ERCs/blob/master/ERCS/erc-8126.md"
  },
  {
   "claim": "ERC-8004, which ERC-8126 requires, is still status Draft on its EIP page.",
   "date": "2025-08-13",
   "label": "VERIFIED",
   "url": "https://eips.ethereum.org/EIPS/eip-8004"
  }
 ],
 "summary_md": "ERC-8126 is a Final Ethereum standard for checking AI agents that already hold an ERC-8004 identity [1]. A verification provider runs up to five checks: the agent's token contract, media it produces (with C2PA guidance), its Solidity code (with OWASP guidance), its web endpoints, and its wallet history. It turns the results into zero-knowledge proofs and a single 0-100 risk score [1]. Detailed results go only to the agent's wallet holder, and attestations can be posted to ERC-8004's Validation Registry so others can see that a check happened [1]. An optional quantum-resistant encryption layer is also described [1].\n\nIt is the first layer of a two-part stack by the same authors: ERC-8196 builds policy-bound agent wallets on top of it. The authors are Leigh Cronian (Cybercentry) and Chris Johnson (Virtuals) [1]. It moved to Last Call on 2026-05-12 and to Final on 2026-06-02 [2].\n\nThe oddity: ERC-8126 is Final while the standard it requires, ERC-8004, is still a Draft that can change [2][3]. Its interfaces could therefore break if ERC-8004 changes before finalisation. The spec carries reference code, but no deployed verification provider was counted in this pass, so adoption is unmeasured.",
 "part_of": null,
 "group": null,
 "use_cases": [
  "prove-agent-identity",
  "audit-agent-actions"
 ],
 "audience": [
  "agent-builder",
  "platform"
 ],
 "pairs_with": [
  "erc-8004",
  "erc-8196"
 ],
 "prerequisites": [
  "erc-8004"
 ],
 "dispute": {
  "claims": [
   "ERC-8126 front matter: status Final (Final 2026-06-02), requires 8004 [1][2].",
   "ERC-8004 EIP page: status Draft [3]."
  ],
  "summary": "ERC-8126 reached Final while it depends on ERC-8004, which is still a Draft. A Final standard is meant to be frozen, but the identity and validation registries it builds on can still change, so ERC-8126 implementations may need to follow ERC-8004 revisions."
 },
 "last_verified": "2026-10-20",
 "history": [
  {
   "date": "2026-10-20",
   "note": "added from gap scout 2026-10-20; verified against eips.ethereum.org/EIPS/eip-8126, the ERCs repository file and commit history (Last Call 2026-05-12, Final 2026-06-02), and the ERC-8004 EIP page (Draft); dispute recorded: Final while its dependency ERC-8004 is Draft"
  }
 ],
 "watch": [
  {
   "type": "erc",
   "num": 8126
  }
 ],
 "freshness": "current",
 "url": "https://agenticweb.wiki/protocols/erc-8126/",
 "category": "identify",
 "type": "protocol"
}