The Ethereum standard ERC-8196, titled "AI Agent Authenticated Wallet," has officially reached final status, concluding its formal review process and making its technical specifications available for developer implementation. Under the Ethereum Request for Comments process, "Final" is the terminal status a proposal reaches after passing through Draft, Review, and Last Call, signaling that the specification is considered stable and complete rather than still open to revision. Co-authored by Leigh Cronian of Cybercentry and Chris Johnson of Virtuals Protocol, the standard introduces a policy-based execution framework built specifically for AI agent wallets.

Chris Johnson announced the finalization on social media, noting that the specification has been reviewed and finalized by the community and that no substantial changes are anticipated.

The development addresses a critical gap in Web3 infrastructure: enabling autonomous agents to execute trades, manage assets, and interact with decentralized applications without requiring human approval for every transaction, while avoiding the security risks of unrestricted private key access. In practice, these requirements pull in opposite directions: manual approval of every action negates autonomy, while sharing raw key material exposes the entire wallet to any compromise of the agent or its host.

At its core, ERC-8196 establishes the Agent Authenticated Wallet (AAW), which replaces blanket credential delegation with precisely defined, cryptographically enforceable permissions. Rather than transferring private keys to an agent, the wallet owner registers a policy that governs which actions are permissible. The policy specifies authorized agent addresses, allowed operation types, whitelisted and blacklisted contracts, single-transaction and daily spending limits, and delegation timeframes.

Each action must reference this policy through an EIP-712 structured signature — EIP-712 being Ethereum's established standard for signing and verifying human-readable, typed data — ensuring that authorization created for one set of permissions cannot be replayed to obtain broader authority. The wallet verifies compliance at the execution layer, meaning the policy—not the agent's underlying model or hosting infrastructure—ultimately determines which transactions may proceed.

— DonJohnson (@DonJohnsonSays) August 28, 2026

Dynamic Verification and Security Safeguards

ERC-8196 operates as the execution layer of a three-tier trust architecture for autonomous agents, working alongside ERC-8126, which covers identity verification and risk scoring, and ERC-8004, which handles decentralized agent registration. Before any transaction executes, the wallet must query the agent's current risk score under ERC-8126 using its agent identifier. If the score exceeds the policy's minimum verification threshold, or if the system detects signals such as sanctioned funds or association with known malicious addresses, the operation is rejected.

This design ensures that trust is continuously evaluated rather than permanently granted, allowing delegations to respond to changing security conditions in real time.

Accountability is further strengthened through a cryptographically linked hash-chain audit log, in which each entry references the previous record to detect tampering. An entropy commitment-disclosure mechanism reduces the risk of hosting infrastructure manipulating probabilistic decision outcomes by cryptographically binding execution to previously committed randomness. Active containment is supported through policy revocation, as policies are immutable and must be replaced to tighten authority.

The framework maintains compatibility with ERC-4337 account abstraction wallets — smart-contract accounts that replace reliance on a single externally owned key with programmable validation logic — and traditional credential delegation. By embedding authorization at the cryptographic layer rather than relying solely on application logic, ERC-8196 enables what its authors describe as constrained autonomy: agents may operate independently within explicit, owner-defined boundaries, while user sovereignty over wallet assets remains preserved. As with any finalized ERC, the specification takes effect only where it is implemented, so its practical reach now depends on wallets, agent platforms, and account-abstraction infrastructure adding support for Agent Authenticated Wallets.