{"id":100941,"date":"2025-09-30T13:47:07","date_gmt":"2025-09-30T13:47:07","guid":{"rendered":"https:\/\/mycryptomania.com\/?p=100941"},"modified":"2025-09-30T13:47:07","modified_gmt":"2025-09-30T13:47:07","slug":"erc-8004-a-trustless-extension-of-googles-a2a-protocol-for-on-chain-agents","status":"publish","type":"post","link":"https:\/\/mycryptomania.com\/?p=100941","title":{"rendered":"ERC-8004: A Trustless Extension of Google\u2019s A2A Protocol for On-chain Agents"},"content":{"rendered":"

Over the past few years, Ethereum has become the go-to platform for financial apps, stablecoins, and tokenised assets. Now, the next big step is bringing AI agents<\/strong> on-chain.<\/p>\n

Why does this matter? Imagine having AI agents that\u00a0can:<\/p>\n

Discover and hire each other<\/strong> to get work done automatically.Share reputation and track records<\/strong> so you know which ones to\u00a0trust.Verify results on-chain<\/strong> so payments only happen when jobs are done correctly.<\/p>\n

That\u2019s where ERC-8004<\/strong> comes in. It extends Google\u2019s Agent-to-Agent (A2A)<\/a> protocol but adds Ethereum\u2019s strengths: trustless verification, cryptographic proofs, and a permanent on-chain record. This way, agents can coordinate safely without needing to \u201cjust trust\u201d each\u00a0other.<\/p>\n

In short, ERC-8004 is about making AI agents as reliable and trustworthy as smart contracts.<\/strong><\/p>\n

ERC-8004 in\u00a0Detail<\/h3>\n

1. Identity\u00a0Registry<\/h4>\n

The Identity Registry<\/strong> provides a universal, verifiable identity for each\u00a0agent.<\/p>\n

Agents register their Agent Card<\/strong> on-chain.The card includes metadata (name, description, capabilities) and an EVM\u00a0address<\/strong>.ERC-8004 aligns with the CAIP-10 standard<\/strong><\/a>, meaning agents can be referenced across different chains<\/strong>.<\/p>\n

Example Agent Card\u00a0(JSON)<\/strong>:<\/p>\n

{
“agent_id”: “agent.eth#0x1234567890abcdef”,
“name”: “ResearchAgent”,
“description”: “AI agent specialized in DeFi research”,
“capabilities”: [“data_analysis”, “onchain_query”, “report_generation”],
“evm_address”: “0x1234567890abcdef1234567890abcdef12345678”,
“schemas”: [“erc8004\/identity\/v1”]
}<\/p>\n

Solidity Interface (simplified)<\/strong>:<\/p>\n

interface IIdentityRegistry {
function registerAgent(
address agentAddress,
string calldata agentURI
) external;<\/p>\n

function getAgent(address agentAddress)
external
view
returns (string memory agentURI);
}<\/p>\n

\ud83d\udc49 This allows an off-chain system to fetch an agent\u2019s JSON card from a URI stored on-chain.<\/p>\n

2. Reputation Registry<\/h4>\n

The Reputation Registry<\/strong> records structured feedback after tasks are completed.<\/p>\n

Client agents submit feedback attestations<\/strong> about server\u00a0agents.Feedback can be multi-dimensional (accuracy, reliability, timeliness, etc.).Attestation layers like Ethereum Attestation Service (EAS)<\/strong> can be plugged\u00a0in.<\/p>\n

Example Feedback Data\u00a0(JSON)<\/strong>:<\/p>\n

{
“feedback_id”: “fbk_001”,
“client_agent”: “agent.eth#0xabc123…”,
“server_agent”: “agent.eth#0x123456…”,
“task_id”: “task_789”,
“ratings”: {
“accuracy”: 5,
“timeliness”: 4,
“reliability”: 5
},
“comments”: “Task completed successfully and ahead of schedule”,
“timestamp”: “2025-09-29T12:00:00Z”
}<\/p>\n

Solidity Interface (simplified)<\/strong>:<\/p>\n

interface IReputationRegistry {
function submitFeedback(
address client,
address server,
string calldata feedbackURI
) external;<\/p>\n

function getFeedback(address server)
external
view
returns (string[] memory feedbackURIs);
}<\/p>\n

\ud83d\udc49 Developers can store only the URI to feedback JSON<\/strong> on-chain, keeping gas costs low, while off-chain indexers aggregate ratings.<\/p>\n

3. Validation Registry<\/h4>\n

The Validation Registry<\/strong> ensures that tasks are actually executed correctly.<\/p>\n

Server agents request validation after publishing a DataHash<\/strong> of their\u00a0results.Validators can\u00a0use:<\/p>\n

\u2192 Crypto-economic methods<\/strong> (restaking, AVSs).<\/p>\n

\u2192 Cryptographic proofs<\/strong> (zkTLS, TEE attestations).<\/p>\n

A ValidationResponse<\/strong> is then posted on-chain.<\/p>\n

Validation Request\u00a0(JSON)<\/strong>:<\/p>\n

{
“validation_request_id”: “valreq_123”,
“server_agent”: “agent.eth#0x123456…”,
“task_id”: “task_789”,
“data_hash”: “0xabcdef1234567890…”,
“validation_type”: “zkTLS”
}<\/p>\n

Validation Response\u00a0(JSON)<\/strong>:<\/p>\n

{
“validation_request_id”: “valreq_123”,
“validator_agent”: “agent.eth#0x987654…”,
“status”: “verified”,
“proof”: “0xdeadbeefcafebabe…”,
“timestamp”: “2025-09-29T12:05:00Z”
}<\/p>\n

Solidity Interface (simplified)<\/strong>:<\/p>\n

interface IValidationRegistry {
function requestValidation(
address server,
string calldata dataHash,
string calldata validationType
) external returns (uint256 requestId);<\/p>\n

function submitValidationResponse(
uint256 requestId,
address validator,
string calldata proof,
bool verified
) external;<\/p>\n

function getValidation(uint256 requestId)
external
view
returns (bool verified, string memory proof);
}<\/p>\n

\ud83d\udc49 Developers can integrate this registry into escrow contracts<\/strong> so that funds are released only if validation succeeds.<\/p>\n

Full Agent\u00a0Workflow<\/h3>\n

Identity: <\/strong>Agents register their Agent Card in the Identity Registry.Discovery: <\/strong>Client finds Server via Agent\u00a0Card.Task Execution<\/strong>: Server executes the task, publishes a data\u00a0hash<\/strong>.Validation<\/strong>: Validators check outputs, post responses on-chain.Feedback: <\/strong>Clients submit feedback linked to the validation result.Payments<\/strong>: Escrow contracts release funds if validations succeed.<\/p>\n

Developer Benefits<\/h3>\n

Composable APIs<\/strong>: Easy-to-integrate Solidity interfaces.Gas Efficiency<\/strong>: URIs point to JSON files instead of storing large amounts of\u00a0data.Modular Trust Models<\/strong>: Choose between crypto-economic or cryptographic verification.Cross-Chain Compatibility<\/strong>: Identity Registry aligns with\u00a0CAIP-10<\/strong>.Extensible Design<\/strong>: New proof systems (e.g., zkML, decentralised TEEs) can be plugged\u00a0in.<\/p>\n

Example Use Cases for Developers<\/h3>\n

Onchain Research-as-a-Service<\/strong>\u200a\u2014\u200aAgents provide verified reports with reputation scores.DeFi Yield Agents<\/strong>\u200a\u2014\u200aStrategies validated before rewards are distributed.Onchain Credit<\/strong>\u200a\u2014\u200aBorrower agents rated via feedback registry.Conditional Gig Payouts<\/strong>\u200a\u2014\u200aEscrow tied to successful validation proofs.<\/p>\n

Putting ERC-8004 Into\u00a0Practice<\/h3>\n

So far, we\u2019ve looked at ERC-8004 as a specification<\/strong>: identity, reputation, and validation registries. But how does this look in a real\u00a0system<\/strong>?<\/p>\n

One of the most useful examples to learn from is the code of ChaosChain Genesis Studio<\/strong>\u200a\u2014\u200athe first end-to-end commercial prototype of ERC-8004<\/strong>.<\/p>\n

\ud83d\udc49 Repo: ChaosChain\/chaoschain-genesis-studio<\/a><\/p>\n

What does it demonstrate?<\/strong><\/p>\n

On-chain agent identity registration<\/strong>Verifiable work<\/strong> using data hashes & validationDirect USDC payments<\/strong> linked to validation successFoundations for IP monetisation<\/strong>, where contributions can be attributed and\u00a0rewarded<\/p>\n

Example Flow: Alice, Bob, and\u00a0Charlie<\/h3>\n

Alice (Server Agent)<\/strong> runs a task (e.g. DeFi analysis) and posts a data\u00a0hash<\/strong>.Bob (Validator Agent)<\/strong> validates the task and posts a Validation Response<\/strong>.Charlie (Client Agent)<\/strong> leaves feedback in the Reputation Registry.If validation passes, the escrowed USDC payment<\/strong> is released to\u00a0Alice.<\/p>\n

Code Patterns from ChaosChain Prototype<\/h3>\n

Identity Registration (Solidity)<\/h4>\n

Agents need to be discoverable. In the prototype, this is done with a simple Solidity function:<\/p>\n

function registerAgent(address agent, string calldata agentURI) external {
require(agent != address(0), “Invalid agent”);
identities[agent] = agentURI;
emit AgentRegistered(agent, agentURI);
}<\/p>\n

This ensures every agent has a unique on-chain record pointing to its metadata (Agent\u00a0Card).<\/p>\n

Validation Request\u00a0(JSON)<\/strong><\/p>\n

When a task is finished, the server agent publishes a validation request<\/strong>. In practice, this looks like a JSON structure:<\/p>\n

{
“validation_request_id”: “valreq_123”,
“server_agent”: “0x123456…”,
“task_id”: “task_789”,
“data_hash”: “0xabcdef123456…”,
“validation_type”: “zkTLS”
}<\/p>\n

This JSON\u00a0defines:<\/p>\n

who did the work (server_agent)What was done (task_id)a cryptographic commitment to the result (data_hash)how it should be verified (validation_type)<\/p>\n

Payment Hook (USDC\u00a0Escrow)<\/h4>\n

Once validation succeeds, USDC payments are released directly to the server\u00a0agent:<\/p>\n

function releasePayment(address to, uint256 amount) external onlyValidator {
require(validationsPassed[to], “Validation not complete”);
usdc.transfer(to, amount);
emit PaymentReleased(to, amount);
}<\/p>\n

This guarantees \u201cno work, no pay\u201d<\/strong>. If validation fails, no funds leave\u00a0escrow.<\/p>\n

The ChaosChain prototype proves ERC-8004\u00a0can:<\/p>\n

Coordinate multiple agents in a trustless environment<\/strong>Link validation and payments<\/strong> directly\u00a0on-chainSupport real commercial use cases<\/strong> like research agents, DeFi strategies, and automated credit\u00a0scoring<\/p>\n

It\u2019s also the foundation for IP monetisation<\/strong>: once agents have identities, reputations, and on-chain payment flows, their outputs (research, strategies, data) can be treated as valuable, tradable intellectual property.<\/p>\n

Conclusion<\/h3>\n

ERC-8004 extends Google\u2019s A2A protocol into the Web3 agentic economy<\/strong>, introducing identity, reputation, and validation registries<\/strong> that developers can use to build trustless, verifiable agent ecosystems.<\/p>\n

Identity Registry<\/strong> \u2192 discoverable, cross-chain agent\u00a0IDs.Reputation Registry<\/strong> \u2192 structured, verifiable feedback.Validation Registry<\/strong> \u2192 cryptographic + crypto-economic task verification.<\/p>\n

For developers, this means a plug-and-play standard<\/strong> to build agents that can cooperate across ecosystems while preserving Ethereum\u2019s trust guarantees.<\/p>\n

ERC-8004 is still early, but it could become the cornerstone standard<\/strong> for agent-to-agent collaboration in DeFi, RWA, AI coordination, and\u00a0beyond.<\/p>\n

References<\/h3>\n

ERC-8004: Trustless Agents (EIP\u00a0Draft)<\/a>Ethereum Magicians: ERC-8004 Discussion<\/a>Google A2A Protocol Announcement<\/a>ERC-8004 and the Agent\u00a0Economy<\/a><\/p>\n

ERC-8004: A Trustless Extension of Google\u2019s A2A Protocol for On-chain Agents<\/a> was originally published in Coinmonks<\/a> on Medium, where people are continuing the conversation by highlighting and responding to this story.<\/p>","protected":false},"excerpt":{"rendered":"

Over the past few years, Ethereum has become the go-to platform for financial apps, stablecoins, and tokenised assets. Now, the next big step is bringing AI agents on-chain. Why does this matter? Imagine having AI agents that\u00a0can: Discover and hire each other to get work done automatically.Share reputation and track records so you know which […]<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-100941","post","type-post","status-publish","format-standard","hentry","category-interesting"],"_links":{"self":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/100941"}],"collection":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=100941"}],"version-history":[{"count":0,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/100941\/revisions"}],"wp:attachment":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=100941"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=100941"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=100941"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}