# ERC-8001: Agent Coordination Framework ERC-8001

[6 · Coordinate](/category/coordinate/)

| ERC-8001: Agent Coordination Framework |
| --- |
| Category | [Coordinate](/category/coordinate/) |
| Governed by | Ethereum EIP/ERC process (Ethereum Magicians discussion + ERCs repository); status Final |
| Status | Final Standards Track ERC (moved to Last Call 2025-12-02 and to Final 2025-12-16) |
| Phase | stable |
| Implementation | prototype |
| Adoption | unmeasured |
| Version | Final, created 2025-08-02 (2025-12-16) |
| Specification | [https://eips.ethereum.org/EIPS/eip-8001](https://eips.ethereum.org/EIPS/eip-8001) |
| Found at | none — no well-known file; discovery is by contract address/ABI |
| Last checked | 2026-10-20 |
| Freshness | current · checked 2026-10-20 |
| Solves | Let agents talk to other agents |

ERC-8001: Agent Coordination Framework is an agentic-web standard (on-chain registry) at step 6, Coordinate, governed by Ethereum EIP/ERC process (Ethereum Magicians discussion + ERCs repository); its own status is "Final Standards Track ERC (moved to Last Call 2025-12-02 and to Final 2025-12-16)" (stable). It answers: How can several agents agree on-chain that a coordinated action may run only once every required participant has signed an acceptance? Adoption is unmeasured, last verified 2026-10-20.

[Coordinate](/category/coordinate/) ERC-8001 is a Final Ethereum standard for agents that need to act together without a trusted coordinator [[1]](#ref-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]](#ref-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]](#ref-1).

## Overview
It 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]](#ref-1). It moved to Last Call on 2025-12-02 and to Final on 2025-12-16 [[2]](#ref-2).

Related: 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]](#ref-3). No count of ERC-8001 deployments was found, so adoption is unmeasured.

## Discovery and probe

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 · none — no well-known file; discovery is by contract address/ABI

```
eth_call {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.
```

Not probed live: not-http. An Ethereum contract; observable via eth_call, not HTTP.

## History
- 2026-10-20 — 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)

## Instances

No instances recorded yet.

## See also

## References

- 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. — [https://eips.ethereum.org/EIPS/eip-8001](https://eips.ethereum.org/EIPS/eip-8001) (2025-12-16) VERIFIED
- 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. — [https://github.com/ethereum/ERCs/blob/master/ERCS/erc-8001.md](https://github.com/ethereum/ERCs/blob/master/ERCS/erc-8001.md) (2025-12-16) VERIFIED
- 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. — [https://eips.ethereum.org/EIPS/eip-8107](https://eips.ethereum.org/EIPS/eip-8107) (2025-12-16) VERIFIED

[JSON](/data/protocols/erc-8001.json) · [Markdown](/protocols/erc-8001/index.md)