Some Ethereum Magicians’ proposal to mandate asset-driven spending suggests token-level control for delegated spend, including AI agent wallet activity.

TL;DR

• Ethereum developers discuss asset-level spending mandate for delegated wallets.
• The idea is to limit agent spending through limits, expirations, allowed tokens, and revocation rules.
• The proposal aims for more secure AI agents and delegated onchain payments.
• This is still an early draft for discussion and not a finalized ERC standard.

A proposal created with the idea of ​​delegating onchain expenses

Ethereum developers are starting to grapple with a practical problem that will only grow: What happens when autonomous agents, delegated wallets, or external scripts can move funds? In a normal wallet flow, the user signs each transaction. In an agent-driven flow, the user can grant permission once and expect the software to function within certain limits.

The asset-driven spending mandate proposal attempts to place these limits at the token level. Instead of relying solely on the wallet, session key, or application policies, the resource itself would consult the gateway before allowing transfers. This gateway could enforce rules such as transaction limits, expiration dates, allowed tokens, and revocation status.

Why the resource layer matters

The key idea behind the design is that the controls should travel with the token, not just with the specific wallet interface. If the AI ​​agent’s key is compromised or if a session goes wrong, the token may still reject transfers beyond the approved mandate. This is essential because many supply chain losses occur when approvals are too broad and users do not fully understand what they have authorized.

The proposal describes a tiny interface that can determine whether an address is gated and whether a transfer is allowed. More importantly, it introduces a machine-readable vocabulary of justification. Instead of restoring a failed transfer without context, the system could determine whether the request failed due to a missing mandate, the mandate has expired, the mandate has been revoked, the token has not been allowed, or the amount has exceeded the transaction limit.

AI agents raise the stakes

AI agent wallets are still in their early stages of development, but the direction is clear. If bots are expected to rebalance portfolios, pay invoices, manage treasury sub-accounts, or interact with DeFi protocols, users will need more than a straightforward yes or no consent. They will need boundaries that are clear, enforceable and revocable.

This puts this proposal in the same broad family as account abstraction, delegated signing, and regulated token pre-transfer checks. It does not attempt to solve identity, compatibility, or all possible permissions problems. Instead, it focuses on a narrow primitive aspect of security: how much the holder can spend, enforced by the asset rather than the good behavior of the agent.

Still early, but on time

The proposal is not a finalized version of the ERC and has not been incorporated into the Ethereum standards process. It’s being released for advance feedback, which means details may change or never make it to production. Still, the moment is noteworthy. Crypto is moving towards more automated wallets, more tokenized assets, and more delegated transaction flows. Without stronger eligibility controls, the convenience of agent financing could quickly become a recent attack surface.

For Ethereum developers, an essential question is whether spending limits should apply primarily to wallets, apps, or assets. This proposal argues that the token contract itself should play a role. If adopted in some form, it could make payments via AI agents more secure, without forcing each app to rebuild its own permissions system from scratch.

This article was written by the News Desk and edited by Samuel Rae.