ERC-8226 Delegation standard for AI agents on regulated assets (Regulated Agent Mandate)

Draft · Accounts & wallets · created 2026-04-12

Defines a delegation framework for verifying onchain, when an AI agent trades regulated tokenized assets on behalf of an investor, everything from identity eligibility to the scope, duration, and amount limits of its authority.

Why it is needed

For an AI agent to trade a regulated tokenized asset on behalf of an investor, three conditions must be satisfied simultaneously. The person who granted authority to the agent must be a real legal identity that has passed KYC, that authority must be clearly recorded with scope, deadline, and amount like a power of attorney, and the asset contract must verify that delegation instantly at execution time without offchain coordination. Regulated token standards such as ERC-7943 or ERC-3643 define who can hold or trade tokens but not how authority is delegated to an agent, and agent identity standards such as ERC-8004 only signal that an agent exists and can be trusted, without addressing the scope or limits of delegation. Because of this gap, there was no standard to guarantee that an agent's authority to autonomously trade security-like tokens was legally traceable.

What to implement

In depth

Separation of the three roles

RAMS is divided into two interfaces: IComplianceProvider and IAgentMandate. IComplianceProvider is deployed by a compliance operator or platform and determines a principal's identity eligibility, while IAgentMandate is deployed by a registry operator and handles the issuance, extension, revocation, suspension, and lookup of mandates. Deploying the two as separate contracts allows each to be governed independently, but a single operator may also combine them.

Mandate keys and scope

A mandate is identified by three values, (agent, principal, asset), and only one active mandate exists per combination. A single agent can have separate mandates for multiple assets with the same principal. Allowed actions are signed as an array of bytes32 labels and recorded in the actionEnabled mapping when grantMandate is called; when a new mandate is issued, the previous mandate's action set is cleared first.

Amount limits and usage tracking

maxTransactionValue is the per-transaction limit, and maxCumulativeValue is the cumulative limit over the entire mandate period. type(uint256).max means unlimited. Each time recordExecution is called, cumulativeUsed increases by the amount, and extending the period with extendMandate does not reset cumulativeUsed. To refill the limit, an explicit revocation followed by issuing a new mandate is required.

Signature-based lifecycle management

grantMandate, revokeMandate, extendMandate, and setOperator can be called directly by the principal, or submitted by anyone carrying the principal's EIP-712 signature. Signatures are verified via the ERC-1271 method, so not only EOAs but also contract wallets such as multisigs can serve as the principal. All signed operations include a per-principal nonce and deadline to prevent replay.

canExecute's check order and reason codes

canExecute checks, in this order, whether the mandate exists, whether the agent is suspended, whether the principal is suspended, the start/expiration time, revocation status, action permission, and per-transaction/cumulative limits, and returns the earliest failing reason as a MandateReason. The actual evaluation order is this specified order, not the order listed in the enum, and suspension-related reasons are checked before other asset-specific checks.

Difference between suspension (freeze) and revocation (revoke)

A freeze is an action by an authorized enforcer to temporarily halt all related mandates at the agent or principal level; it is reversible and does not delete the mandate itself. A revoke can only be done by the principal (or an approved operator), is irreversible, and does not delete the record but only sets the revoked flag. An enforcer has no authority to permanently remove a mandate.

Token integration and three enforcement points

A regulated token gates every function that an agent can call on behalf of a holder, checking the mandate via canExecute and recording it via recordExecution. For cases where the token itself cannot be modified, such as an already-deployed asset, the same delegation can be applied through an EIP-7702 delegated account or a separate executor. A RAMS mandate does not replace ERC-20 allowances or ERC-721/1155 operator approvals, and a trade must pass both for it to succeed.

Proposal status

This proposal is still in Draft status, and its detailed rules or interfaces may change or be discontinued.

Things to watch out for

Original ERC · ← ERCs