ERC-8004 and ERC-8183 Wire Agent-to-Agent Markets, TEEs and zkML Close the Trust Loop
Two new Ethereum drafts standardize agent discovery and escrowed task settlement, while TEEs and zkML provide the verification backbone for autonomous agent economies.
The infrastructure for autonomous agent economies is snapping into place. Two Ethereum Improvement Proposals — ERC-8004 and ERC-8183 — define the discovery and settlement layers, while TEEs and zkML provide the verification backbone. Together, they enable a trust-minimized loop: identify an agent, hire it, pay it, and audit its work without a centralized platform.
ERC-8004 standardizes agent identity through three on-chain registries: an ERC-721 identity registry, a reputation registry with signed feedback, and a validation registry for independent checks like zkML verifiers or TEE oracles [^claim_1484]. The identity registry makes agents browsable and transferable as NFTs, with metadata that includes agent wallets, ENS, DID, MCP, and A2A endpoints [^claim_1485]. That turns agents into first-class on-chain assets — discoverable, portable, and composable with existing NFT infrastructure.
ERC-8183 complements discovery with settlement. It defines a Job primitive with escrowed budget and a four-state lifecycle: Open, Funded, Submitted, and Terminal. Only the evaluator may mark a submitted job completed or rejected [^claim_1486]. The spec supports composability with ERC-8004 by allowing optional attestation reasons on complete/reject events and recommending outcome-based trust signals and reputation interop [^claim_1487]. Hooks can wrap core actions (setProvider, fund, submit, complete, reject), but refund-by-expiry is intentionally not hookable — a design choice that prevents griefing [^claim_1488].
On the verification side, TEE-based verifiable compute runs inference inside an enclave, signs the output with a key bound to the loaded code measurement, and lets a verifier check the attestation chain rooted in the chip vendor PKI [^claim_1489]. Several production systems already ship attested AI inference using TEEs, including Marlin Oyster, Phala Network, Atoma Network, Automata, and Tinfoil [^claim_1490]. Chainlink’s verifiable AI stack says AI outputs can be mathematically verified onchain before state changes, using either zkML or TEEs to prove correct execution [^claim_1491]. Mina’s zkML library lets developers generate zero-knowledge proofs from AI inference jobs with private inputs and submit those proofs to Mina for trustless verification [^claim_1492].
Finally, Coinbase launched Agentic Wallets as wallet infrastructure built specifically for AI agents so they can spend, earn, and trade autonomously [^claim_1493]. This closes the loop: an agent identified via ERC-8004 can be hired via ERC-8183, execute work verified by TEE or zkML, and transact autonomously via Agentic Wallets.
The design choice for crypto-native builders is no longer whether to use AI with blockchain, but which trust primitive to pair with the workflow: reputation, TEE attestation, zk proof, or on-chain dispute resolution. The primitives are here. The market is wiring them together.
Provenance ledger
10 claims web-citedEvery claim below cites a source URL, and each URL was checked for validity before publish. The excerpt shown is the researcher's own summary of the page — it is not re-derived from the source, so it is not a verified verbatim quote. Follow the link to confirm any claim against the original. Citation markers in the text jump here.
[1] ERC-8004 defines three on-chain registries for autonomous agents: an ERC-721 identity registry, a reputation registry with signed feedback, and a validation registry for independent checks such as zkML verifiers or TEE oracles. web-cited
Abstract and specification describe identity, reputation, and validation registries; the validation registry explicitly mentions zkML verifiers and TEE oracles.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[2] ERC-8004’s identity registry makes agents browsable and transferable as NFTs, with agent metadata stored in a registration file and optional support for agent wallets, ENS, DID, MCP, and A2A endpoints. web-cited
The identity registry uses ERC-721 with URIStorage; the registration file includes services such as web, A2A, MCP, ENS, DID, and email, plus an agentWallet field.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[3] ERC-8183 defines a Job primitive with escrowed budget and a four-state lifecycle: Open, Funded, Submitted, and Terminal, where only the evaluator may mark a submitted job completed or rejected. web-cited
Abstract and state machine specify job escrow with evaluator attestation, four states, and evaluator-only completion/rejection after submission.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[4] ERC-8183 supports composability with ERC-8004 by allowing optional attestation reasons on complete/reject events and recommending outcome-based trust signals and reputation interop. web-cited
The spec says optional attestation reason enables audit and composition with reputation, and the extension section recommends integrating with ERC-8004.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[5] ERC-8183’s reference design includes optional hook contracts that can run before and after core actions, but refund-by-expiry is intentionally not hookable. web-cited
Hooks section says beforeAction/afterAction can wrap setProvider, setBudget, fund, submit, complete, and reject, while claimRefund is not hookable.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[6] TEE-based verifiable compute works by running inference inside an enclave, signing the output with a key bound to the loaded code measurement, and letting a verifier check the attestation chain rooted in the chip vendor PKI. web-cited
The article explains enclave provisioning, attested model loading, output signing, and verification against Intel PCS, AMD KDS, or AWS Nitro attestation roots.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[7] Several production systems already ship attested AI inference using TEEs, including Marlin Oyster, Phala Network, Atoma Network, Automata, and Tinfoil. web-cited
The page lists these systems as production ships for attested AI inference.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[8] Chainlink’s verifiable AI stack says AI outputs can be mathematically verified onchain before state changes, using either zkML or TEEs to prove correct execution. web-cited
The article describes cryptographic verification with zkML or TEEs, then onchain delivery where the smart contract verifies the proof before executing state changes.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[9] Mina’s zkML library lets developers generate zero-knowledge proofs from AI inference jobs with private inputs and submit those proofs to Mina for trustless verification. web-cited
The developer guide says the library generates ZKPs from AI inference jobs using private inputs and settles those proofs on Mina blockchain.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
[10] Coinbase launched Agentic Wallets as wallet infrastructure built specifically for AI agents so they can spend, earn, and trade autonomously. web-cited
The Coinbase launch page states the wallets are built specifically for agents and equip them with autonomous spending, earning, and trading.
This excerpt was not re-derived from the source page, and may paraphrase or condense it. Check the source before relying on it.
Sources
- https://eips.ethereum.org/EIPS/eip-8004
- https://eips.ethereum.org/EIPS/eip-8183
- https://eco.com/support/en/articles/14796365-tees-for-ai-agents-verifiable-compute
- https://chain.link/article/verifiable-ai-stack
- https://minaprotocol.com/blog/minas-zkml-library-developer-guide
- https://www.coinbase.com/developer-platform/discover/launches/agentic-wallets