ERC-8196 primary sources — 2026-05-07

Project status in this pass

• No standalone ERC-8196 whitepaper or litepaper surfaced.
• The clearest current source of truth was the draft ERC itself, backed by the raw ERC markdown.
• The sources consistently frame ERC-8196 as the execution layer in a broader agent trust stack rather than as a standalone wallet product.

Primary-source snapshots

1) Canonical ERC page

• URL: https://eips.ethereum.org/EIPS/eip-8196
• Key excerpt/signals:
  • The abstract says agent-authenticated wallets should execute only when actions come with verifiable proof of policy compliance.
  • The standard explicitly calls itself Layer 3 (Execute) above ERC-8004 registration and ERC-8126 verification.
  • The motivation lists host key theft, blind delegation, host manipulation, malicious history, and replay or timing attacks as the target threat model.
• Why it mattered:
  • This is the clearest evidence that ERC-8196 belongs in the corpus as bounded-execution infrastructure for autonomous agents.

2) Raw ERC markdown / trust-stack integration

• URL: https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-8196.md
• Key excerpt/signals:
  • Implementations MUST verify ERC-8004 registration before policy use.
  • Implementations MUST perform ERC-8126 verification checks before action execution and enforce the policy’s verification threshold.
• Why it mattered:
  • These details show ERC-8196 is intentionally downstream of identity and verification layers, not a self-contained wallet standard.

3) Raw ERC markdown / policy schema

• URL: https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-8196.md
• Key excerpt/signals:
  • Policies include agent, owner, allowed actions, contract allowlists and blocklists, transaction value limits, optional daily limits, validity windows, and verification thresholds.
  • The action and delegation flow relies on EIP-712 typed data.
• Why it mattered:
  • This is strong evidence that ERC-8196 is about explicit capability bounding and auditable delegation rather than generic signing convenience.

4) Raw ERC markdown / audit and security model

• URL: https://raw.githubusercontent.com/ethereum/ERCs/master/ERCS/erc-8196.md
• Key excerpt/signals:
  • Audit entries must be hash-chained and may be anchored periodically through ERC-8004’s Validation Registry.
  • The security section emphasizes final user control, rejection or revocation on malicious verification results, and active containment where possible.
• Why it mattered:
  • These details show that accountability and constrained autonomy are first-class design goals rather than optional operational practices.

5) Discussion thread

• URL: https://ethereum-magicians.org/t/erc-8196-ai-agent-authenticated-wallet/27987
• Key excerpt/signals:
  • Only the discussion thread title surfaced cleanly in this pass; the thread content did not extract usefully.
• Why it mattered:
  • Even without useful body extraction, the linked discussion confirms the live standards-track venue for the draft.

Working conclusion

ERC-8196 is best cataloged as policy-bound autonomous execution infrastructure. The decisive evidence in this pass was its layered dependence on ERC-8004 and ERC-8126, its explicit capability-bounding policy schema, and its tamper-evident audit design for keeping agent action constrained, reviewable, and user-governed.