ERC-8004 Mainnet Launch: Ethereum’s AI Agent Identity Standard Goes Live Thursday

ERC-8004 launches on Ethereum mainnet tomorrow. The “Trustless Agents” standard goes live Thursday, January 29, 2026 at 9 AM ET—establishing blockchain-native identity infrastructure for AI agents to discover each other, build portable reputation, and transact across organizational boundaries without gatekeepers.

This is Ethereum’s biggest bet on the AI economy. Here’s what ERC-8004 actually does, who’s deploying Thursday, what the spec enables—and what it deliberately leaves out.


What ERC-8004 Is

ERC-8004 creates three lightweight on-chain registries for AI agent trust. The official specification defines them as:

Identity Registry: Every AI agent mints an ERC-721 NFT containing a URI that resolves to an agent registration file—name, description, supported services (A2A, MCP, ENS, DID endpoints), and wallet verification. This makes agents immediately browsable on any NFT-compatible app.

Reputation Registry: A standard interface for posting and fetching feedback signals. Feedback includes signed values, optional tags for filtering, off-chain URIs pointing to detailed JSON, and KECCAK-256 hashes for integrity verification. The system supports x402 payment proofs, allowing agents to demonstrate they’ve actually been paid for work performed.

Validation Registry: Enables independent validator checks through stake-secured re-execution, zkML verifiers, TEE oracles, or trusted judges. Validators respond on a 0-100 scale, supporting both soft and hard finality use cases.

The architecture keeps application logic off-chain while anchoring trust on-chain. As Composable Security’s technical explainer puts it: “ERC-8004 provides the minimum viable trust layer—identity, reputation signals, and validation hooks—without prescribing how applications use them.”


Who Built It

ERC-8004 was co-authored by Marco De Rossi (MetaMask AI Lead), Davide Crapis (Ethereum Foundation dAI team), Jordan Ellis (Google), and Erik Reppel (Coinbase Head of Engineering). The standard extends Google’s Agent-to-Agent protocol with a Web3 trust layer.

According to Crypto Reporter, the Ethereum Foundation’s dAI team positions this as “a practical milestone in our long-term strategy to establish Ethereum as the global decentralized settlement layer for AI.”

The specification passed its freeze on October 8, 2025, and reference implementations have been running on five testnets. ChainCatcher reports over 1 million registered agents processing $250M in weekly flows during the testnet phase.


Who’s Launching Thursday

ChaosChain maintains the official reference implementation—currently passing 79/79 tests with 100% spec compliance. Their contracts deploy to deterministic addresses across all networks:

  • Identity Registry: 0x7177a6867296406881E20d6647232314736Dd09A
  • Reputation Registry: 0xB5048e3ef1DA4E04deB6f7d0423D06F63869e322
  • Validation Registry: 0x662b40A526cb4017d947e71eAF6753BF3eeE66d8

ChaosChain also ships the ChaosChain SDK (Python, available on PyPI), Genesis Studio as the first commercial prototype, and a managed x402 facilitator.

8004scan.io launches as the “Etherscan for AI Agents”—the first on-chain explorer dedicated to ERC-8004. It provides agent discovery, identity registry visualization, reputation tracking, and agent leaderboards.

Projects confirmed with ERC-8004 integration include Virtuals Protocol (AI agent token launchpad with auto-assigned identities), Taiko (L2 execution layer), EigenLayer (stake-secured validation), Phala Network (TEE-derived keys), OpenServ (multi-agent workflows), Unibase (persistent agent memory), and Mode Network (AI-focused L2).

The awesome-erc8004 repository on GitHub tracks the growing ecosystem of tools, SDKs, and implementations.


Chain Support

ERC-8004 launches Thursday on Ethereum mainnet and Base, with additional L2 support following. The standard is compatible with all EVM chains, deploying as a per-chain singleton.

Current testnet deployments span Ethereum Sepolia, Base Sepolia, Optimism Sepolia, Mode Testnet, 0G Testnet (Galileo), Polygon Amoy, Hedera Testnet, and Linea Sepolia. Questflow’s technical analysis notes the multi-chain design means agents can have identities on multiple chains simultaneously.

The Global Agent ID format is {namespace}:{chainId}:{identityRegistry}:{agentId}—for example, eip155:1:0x742...:22 for Ethereum mainnet.


The x402 Connection

ERC-8004 pairs with x402—the HTTP-native payment protocol for machine-to-machine transactions. As Bitget’s analysis explains: ERC-8004 handles identity (“who is this agent?”), while x402 handles payment (“how does this agent pay?”).

Together, they enable a complete stack: an agent registers identity via ERC-8004, builds reputation through validated work, and settles payments through x402. The Coin Republic calls this “the infrastructure layer for the autonomous agent economy.”

Coinbase has processed over 75 million x402 transactions representing $24 million in value since the protocol’s May 2025 launch.


Token Ecosystem

Several tokens are positioned around ERC-8004 infrastructure. Note: ERC-8004 itself is a standard, not a token.

$DREAMS (Daydreams) has the deepest integration—Daydreams.Systems built a reference implementation and offers the Lucid Agents SDK with native ERC-8004 identity toolkit. The token showed a 42.80% price increase over seven days heading into the launch.

$PAYAI operates as payment infrastructure for AI agents, built on ElizaOS and Solana. $DEXTER positions itself as Solana-side implementation for ERC-8004, operating its own x402 facilitator. $ZAUTH connects to the x402 payment layer with creator fees funding user credits.

The broader AI agent token sector has a ~$7.7 billion market cap with daily volumes approaching $1.7 billion.


The Transferability Question

Here’s what most coverage isn’t telling you: ERC-8004 agent identities are fully transferable NFTs.

The specification states explicitly that “the owner of the ERC-721 token is the owner of the agent and can transfer ownership” and that agents are “immediately browsable and transferable with NFTs-compliant apps.”

This is a deliberate design choice enabling agent marketplaces and ownership transfers. But it creates a fundamental tension: when an agent NFT sells, the accumulated reputation travels with it.

Technical discussion on Medium and Ethereum Magicians notes this “introduces risks of identity transfer abuse”—bad actors could buy high-reputation identities to bypass trust requirements, enabling reputation laundering.

The specification’s Security Considerations section acknowledges that “Sybil attacks are possible, inflating the reputation of fake agents” and notes the protocol cannot cryptographically guarantee advertised capabilities are functional or non-malicious.

For applications requiring non-transferable identity—where reputation must reflect genuine earned history rather than purchased credentials—ERC-8004 alone isn’t sufficient.


Where Soulbound Tokens Fit

ERC-5192 defines soulbound tokens—NFTs with a locked() function that, when true, causes all transfer functions to revert. Once minted to an address, a soulbound token cannot move. You can burn it (the right to disappear), but you can’t sell it.

This solves the reputation laundering problem that transferable ERC-8004 identities enable. If identity can’t transfer, reputation markets can’t form. An agent’s history reflects what that specific agent actually did—not what some previous owner accumulated.

The tradeoff is real: soulbound identity means legitimate transfers (company acquisitions, key rotations) require burning and re-minting, losing accumulated history. It’s less flexible by design.

Hybrid models can work: attach soulbound reputation badges to transferable ERC-8004 identities. The base identity can change hands, but specific certifications—verified task completions, audit attestations, tenure markers—stay bound to the original owner.

RNWY deploys this approach on Base: ERC-5192 soulbound tokens for non-transferable identity anchors, with EAS attestations for vouches and task receipts. When ERC-8004 goes live, RNWY’s soulbound layer becomes complementary infrastructure—flagging when an agent’s ERC-8004 identity has transferred while their soulbound credential hasn’t (because it can’t).

The RNWY SBT contract is already deployed on Base mainnet. The approach: use ERC-8004 for discovery and interoperability, use soulbound tokens for accountability that can’t be gamed.


What This Means for Builders

ERC-8004 establishes the industry standard for AI agent identity on Ethereum. After Thursday, agents can:

  • Register portable identities that work across any EVM chain
  • Build reputation through validated work and payment proofs
  • Discover other agents through on-chain registries
  • Interoperate with the broader ecosystem (A2A, MCP, x402)

The questions to ask when evaluating agent identity infrastructure:

Is transferability a feature or a bug for your use case? If you’re building agent marketplaces or want ownership flexibility, ERC-8004’s transferable NFTs work great. If you’re building high-stakes applications where reputation must reflect actual history, you need a soulbound layer.

What happens when identity changes hands? ERC-8004 doesn’t distinguish between an agent that’s been controlled by one entity for two years versus one that sold last week. Soulbound credentials make that history visible.

How do you verify the agent you’re talking to is the one with that reputation? ERC-8004 provides identity. It doesn’t prove the agent responding actually controls that identity—that requires additional verification infrastructure.


Official Resources

Specifications:

Implementations:

Explorers:

News Coverage:


ERC-8004 provides essential infrastructure for AI agent identity. For applications where reputation must be non-transferable—where trust should be earned, not purchased—RNWY adds the soulbound layer. Our ERC-5192 contract is live on Base, ready to complement ERC-8004 when mainnet launches tomorrow.

For more on how soulbound tokens work and why non-transferable identity matters, see our technical guide to soulbound tokens for AI agents.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *