Update: spec refinements and reference implementation now in PR #1844
We’ve opened PR #1844. Two sets of changes, one from the EIP review process and one from this thread.
Spec refinements
-
complianceProvideris now mandatory atgrantMandate. The optional path is removed. This closes a gap that was implicit in @TrendAdmin’s question on safeguards: with the provider optional, a mandate could be granted without principal eligibility verification ever running. Making it mandatory ensures the dual compliance check is always active. -
Cap denomination clarified, and enforcement is now explicitly venue-agnostic. The same mandate can be enforced at the token hook, in an EIP-7702 delegated account, or via a dedicated executor, with consistent semantics across all three.
Reference implementation (under assets/erc-8226/)
-
AgentMandateregistry -
ComplianceProviderreference -
Optional
AgentExecutor -
End-to-end integration with ERC-7943 (uRWA-20) showing the dual compliance check pattern in working code
Position on the custody model open question
After working through the reference implementation, the current PR keeps the spec custody-agnostic. Prescribing a default would constrain adoption across use cases with materially different operational needs (high-frequency strategies vs long-term investment vehicles, agent-direct vs principal-direct settlement). Both models are supported by the same interfaces. The reference implementation demonstrates the agent-custodied path with ExecutionRecorded events for traceability; principal-custodied works without any spec changes. We’ll revisit this position once we have production deployments to learn from.
Open for feedback
-
Does the venue-agnostic enforcement model hold up for EIP-7702 delegated accounts in your view, or are there account-abstraction edge cases that need explicit handling in the spec?
-
On composability: @Nicopat, your ERC-8240 integration note remains fully applicable.
IComplianceProvideris unchanged. Happy to coordinate on the composition note you mentioned.