ERC-8226: Regulated Agent Mandate

Дата публикации: 28-09-2026 02:52:01

I have a question about multi-asset delegation in ERC-8226.
As I understand it, an active mandate is keyed by (agent, principal), while each mandate specifies a single asset.
Does this mean the following two mandates cannot coexist in the same AgentMandate registry?
Principal P + Agent A → Token A
Principal P + Agent A → Token B
If so, what is the intended pattern for an agent managing multiple assets for the same principal?
Use a different agent address per asset?
Deploy separate AgentMandate registries per asset?
Or is supporting multiple mandates for the same (agent, principal) pair something being considered, e.g. (agent, principal, asset) or a mandateId?
I’m mainly curious whether the one-active-mandate-per-pair constraint is intentional, and what deployment pattern you would recommend for multi-asset use cases.

Схожие новости

#	Наименование новости	Тональность	Информативность	Дата публикации
1	Onchain IP Asset and License Registry	0	8	28-09-2026
2	ERC-8320: Regulated Asset Claim	0	7.2	28-09-2026
3	ERC-8392: Asset Status Interface for Tokenized Assets	0	8.06	28-09-2026
4	ERC-8427: Portable Spend Grants	0	10.76	28-09-2026
5	ERC-8183: Agentic Commerce	0	12.88	28-09-2026
6	ERC-8412: Preregistered Acceptance Criteria	0	6.62	28-09-2026
7	EIP-8425: Quantum Freeze and Account Recovery	0	4.76	28-09-2026
8	ERC-8415: Asynchronous Register Projection for NFTs	0	12.36	28-09-2026
9	RFC: Procedure Manifests - Mechanism for AI Agents to Resolve Contractual Disputes	0	9.98	28-09-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 9. Тональность: 0. Информативность: 5.76. Источник: ethereum-magicians.org.