{
 "id": "erc-8001",
 "name": "ERC-8001: Agent Coordination Framework",
 "acronym": "ERC-8001",
 "aliases": [
  "EIP-8001"
 ],
 "collisions": [],
 "step": "coordinate",
 "parties": [
  "agent-agent"
 ],
 "form": "onchain-registry",
 "track": "community",
 "scope": "general",
 "question": "How can several agents agree on-chain that a coordinated action may run only once every required participant has signed an acceptance?",
 "analog": "A contract that takes effect only when every party has countersigned",
 "origin": {
  "org": "Ethereum community (Kwame Bryan)",
  "date": "2025-08-02"
 },
 "governance": "Ethereum EIP/ERC process (Ethereum Magicians discussion + ERCs repository); status Final",
 "native_status": "Final Standards Track ERC (moved to Last Call 2025-12-02 and to Final 2025-12-16)",
 "phase": "stable",
 "implementation": "prototype",
 "adoption": {
  "level": "unmeasured",
  "by": null,
  "probe_run": null
 },
 "version": {
  "label": "Final, created 2025-08-02",
  "date": "2025-12-16"
 },
 "spec_url": "https://eips.ethereum.org/EIPS/eip-8001",
 "discovery": {
  "mechanism": "EVM smart-contract interface; an initiator posts an EIP-712 intent and participants post EIP-712 or ERC-1271 acceptances to an ERC-8001 contract",
  "path": "none — no well-known file; discovery is by contract address/ABI"
 },
 "probe": {
  "method": "eth_call",
  "path": "{contract_address}",
  "parse": "Contract implements the ERC-8001 functions (proposeCoordination, acceptCoordination, executeCoordination, cancelCoordination, getCoordinationStatus, getRequiredAcceptances, getAgentNonce) and emits the mandatory lifecycle events",
  "on_absent": "Absence at a given contract address only shows that deployment does not implement ERC-8001; there is no registry of ERC-8001 deployments to enumerate."
 },
 "evidence": [
  {
   "claim": "ERC-8001 defines a minimal single-chain primitive for multi-party agent coordination: an initiator posts an intent, each participant provides a verifiable acceptance attestation, and the intent is executable once the required set of acceptances is present and fresh. It requires EIP-712, ERC-1271, EIP-2098 and EIP-5267, leaves privacy, reputation, thresholds, bonding and cross-chain semantics to optional modules, and ships a reference implementation (AgentCoordination.sol). Status Final, created 2025-08-02, author Kwame Bryan.",
   "date": "2025-12-16",
   "label": "VERIFIED",
   "url": "https://eips.ethereum.org/EIPS/eip-8001"
  },
  {
   "claim": "The ERCs repository front matter for erc-8001.md reads status: Final; its commit history shows the move to Last Call on 2025-12-02 and to Final on 2025-12-16.",
   "date": "2025-12-16",
   "label": "VERIFIED",
   "url": "https://github.com/ethereum/ERCs/blob/master/ERCS/erc-8001.md"
  },
  {
   "claim": "ERC-8107 'ENS Trust Registry for Agent Coordination' (status Review, created 2025-12-16, same author) defines a web-of-trust registry keyed by ENS names, with OpenPGP-style trust levels and path verification, as the trust and delegation module that ERC-8001 anticipates; it requires ERC-8001.",
   "date": "2025-12-16",
   "label": "VERIFIED",
   "url": "https://eips.ethereum.org/EIPS/eip-8107"
  }
 ],
 "summary_md": "ERC-8001 is a Final Ethereum standard for agents that need to act together without a trusted coordinator [1]. An initiator posts an EIP-712 signed intent naming the participants; each participant posts its own signed acceptance (EIP-712, or ERC-1271 for contract wallets); and the intent becomes executable only once every required acceptance is present and unexpired [1]. Canonical, sorted participant lists, nonces and standard typed data give replay protection and wallet compatibility, and the spec fixes the lifecycle and the events a contract must emit [1].\n\nIt is deliberately small. The authors leave privacy, reputation, threshold policies, bonding and cross-chain coordination to optional modules that reference it, and the spec includes a reference contract rather than pointing to production deployments [1]. It moved to Last Call on 2025-12-02 and to Final on 2025-12-16 [2].\n\nRelated: ERC-8107, an ENS Trust Registry by the same author and still in Review, is written as the trust and delegation module ERC-8001 anticipates. Agents vouch for or deny each other under ENS names, and a coordinator can admit only participants reachable through a trust path [3]. No count of ERC-8001 deployments was found, so adoption is unmeasured.",
 "part_of": null,
 "group": null,
 "use_cases": [
  "agent-to-agent-messaging"
 ],
 "audience": [
  "agent-builder",
  "platform"
 ],
 "pairs_with": [
  "erc-8183",
  "erc-8004"
 ],
 "prerequisites": [],
 "dispute": null,
 "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-8001, the ERCs repository file and commit history (Last Call 2025-12-02, Final 2025-12-16), and eips.ethereum.org/EIPS/eip-8107 (related ENS Trust Registry, Review)"
  }
 ],
 "watch": [
  {
   "type": "erc",
   "num": 8001
  },
  {
   "type": "erc",
   "num": 8107
  }
 ],
 "freshness": "current",
 "url": "https://agenticweb.wiki/protocols/erc-8001/",
 "category": "coordinate",
 "type": "protocol"
}