Ethereum (ETH) announced ERC-8004 is heading to mainnet, positioning the network as a neutral infrastructure for a problem the AI industry can't yet solve: how agents prove they're trustworthy when no single platform controls the reputation layer. The timing reveals the underlying tension, as AI agents are moving from demos into production systems that trigger real transactions. Mastercard is drafting commerce standards for agentic checkout, UK banks are piloting customer-facing agent trials slated for early 2026, and Gartner projects 40% of enterprise applications will integrate task-specific agents by year-end. However, a Camunda report found that while 71% of organizations now deploy AI agents, only 11% of use cases reached production over the past year. The blockers are trust, transparency, and regulatory risk. Dynatrace surveys show roughly half of agentic projects stalled in pilot, with 52% citing security and compliance issues, and about 70% of AI decisions still requiring human verification. ERC-8004 tries to productize that trust gap by defining three lightweight registries: identity, reputation, and validation. Those can be deployed on mainnet or layer-2 blockchains as application-layer contracts, not a protocol fork. Ethereum's official account framed the standard as enabling “discovery and portable reputation,” so AI services can “interoperate without gatekeepers.” The canonical spec remains in draft status on eips. ethereum. org. Surveys from Camunda and Dynatrace show 71% of organizations deploy AI agents, but only 11% reach production due to security and human verification requirements. Three registries, three coordination problemsThe Identity Registry turns each agent into an ERC-721 NFT with a global identifier and a pointer to a structured registration file. That file lists capabilities, endpoints (MCP, A2A, ENS, DID, web URLs), and contact methods, essentially serving as a service directory for machine actors. Agents become discoverable and transferable using standard NFT tooling. The spec includes optional endpoint domain verification to prove domain control, and reserves an “agentWallet” field that requires EIP-712 signature or ERC-1271 verification to change. The design choice prevents “I'm reputable, pay here” hijacks, where an attacker swaps the payment address while preserving the reputation. Identity solves composability, as reputations and validations can be indexed to a stable agent ID rather than a platform account.
