Cowrie Research

erc-8226-primary-sources-2026-05-08

3 min read

ERC-8226 primary sources — 2026-05-08

Project status in this pass

  • No standalone ERC-8226 whitepaper or litepaper surfaced.
  • The clearest source of truth was the Ethereum Magicians draft thread plus the ERC pull-request patch.
  • The materials consistently frame ERC-8226 as a regulated-asset compliance layer for AI agents rather than as a general-purpose agent-wallet standard.

Primary-source snapshots

1) Ethereum Magicians draft thread

  • URL: https://ethereum-magicians.org/t/erc-8226-regulated-agent-mandate/28208
  • Key excerpt/signals:
    • The thread says RAMS defines a compliance delegation layer for AI agents operating on tokenized regulated assets.
    • It says the standard is agnostic to the underlying agent registry and token compliance framework, pointing to ERC-8004, EIP-7943, and ERC-3643 as adjacent layers.
    • It highlights mandate delegation, dual compliance checks through the token’s pre-transfer hook, a unified compliance provider, and jurisdiction-scoped enforcement.
  • Why it mattered:
    • This is the clearest high-level evidence that ERC-8226 belongs in the corpus as compliance-delegation infrastructure for regulated token markets.

2) Draft ERC patch / abstract and motivation

  • URL: https://patch-diff.githubusercontent.com/raw/ethereum/ERCs/pull/1679.patch
  • Key excerpt/signals:
    • The abstract says a verified principal can delegate scoped, time-bounded, and financially capped authority to an agent and have RAMS-aware tokens verify mandate validity before regulated transfers.
    • The motivation says ERC-8004 alone cannot satisfy verified-principal identity, legally traceable power-of-attorney-like mandate scope, and atomic transfer-time compliance checks.
    • The draft explicitly frames the target market as tokenized regulated assets under frameworks like MiCA, VARA, and MiFID II.
  • Why it mattered:
    • These details show ERC-8226 is not just another agent standard; it is an institutional compliance overlay for agentic execution.

3) Draft ERC patch / interface and integration model

  • URL: https://patch-diff.githubusercontent.com/raw/ethereum/ERCs/pull/1679.patch
  • Key excerpt/signals:
    • RAMS defines two interfaces: IComplianceProvider and IAgentMandate.
    • The spec says RAMS-aware ERC-7943 token contracts consult the RAMS registry inside their existing canTransfer hook.
    • Agents continue using standard ERC-20 transfer and transferFrom rather than token-specific agent functions.
  • Why it mattered:
    • This reveals the core control architecture: token issuers keep their compliance gate, while RAMS adds a second mandate-validation layer without bloating the token interface.

4) Draft ERC patch / rationale and trust surfaces

  • URL: https://patch-diff.githubusercontent.com/raw/ethereum/ERCs/pull/1679.patch
  • Key excerpt/signals:
    • The rationale says RAMS is separate from ERC-8004 because regulated transactions need a narrower and more compliance-specific layer.
    • It defends a single IComplianceProvider interface because identity is treated as a subset of compliance checking.
    • It defends one active principal per agent on account-segregation grounds and keeps freeze authority inside the mandate registry.
  • Why it mattered:
    • This is the strongest evidence about where control centralizes in practice: compliance operators, segregated-account assumptions, and freeze-capable enforcers.

5) Draft thread / open topics

  • URL: https://ethereum-magicians.org/t/erc-8226-regulated-agent-mandate/28208
  • Key excerpt/signals:
    • The authors leave token custody model, receive-side compliance, and ERC-8004 regulatoryCompliance trust signaling open for community input.
    • They ask whether the standard should stay custody-model agnostic or prefer agent-custodied versus principal-custodied settlement.
  • Why it mattered:
    • These open questions identify the deepest unresolved control surfaces in regulated agent execution: who legally owns the asset, who passes compliance checks on incoming transfers, and how compliance status becomes legible to downstream systems.

Working conclusion

ERC-8226 is best cataloged as a mandate-and-compliance overlay for agent-driven transactions in regulated token markets. The decisive evidence in this pass was the dual-check model, the external compliance-provider interface, the one-active-principal segregation rule, and the explicit integration with ERC-8004 identity plus ERC-7943 or ERC-3643 token compliance.

Graph View