Ethereum Proposes Asset-Level Spending Limits for Wallets

An Ethereum Magicians forum post from June 18, 2026 proposes an "asset-enforced spend mandate," a draft standard that would let an ERC-20 token consult a small gate contract before allowing a transfer, rejecting it with a machine-readable reason (no mandate, expired, revoked, wrong asset, or over the per-transaction cap) if the transfer doesn't fit terms a token holder previously authorized. The design directly targets AI agents and delegated wallets moving funds without per-transaction human sign-off: because the constraint lives at the token contract rather than the wallet or session key, the proposal argues a transfer stays capped even if an agent's key is fully compromised.

The proposal, from Ethereum Magicians user VladKuzR, positions itself as the missing layer in an existing standards stack: ERC-20 defines what you hold, ERC-3643/ERC-7943 define who may hold it, ERC-4337/ERC-7702 define who may sign for it, and this proposal would define what a holder may spend, enforced by the asset itself. Forum commentary flagged a real trade-off: token-level enforcement only works for tokens that opt in to the new interface, so it doesn't help existing ERC-20s unless each one upgrades. An alternative, account-level approach, ERC-7710/ERC-7715 and MetaMask's Delegation Framework, enforces spending limits before a transaction is even submitted and works with any existing token, but only catches transfers that route through the delegation system in the first place, not a holder who controls their own balance directly.

Developers building AI agents that move onchain assets should read this as a signal, not yet a standard to implement: per-transaction caps, expiration windows, allow-lists, and instant revocation are becoming the expected baseline for agent wallet permissions, whether enforced at the token layer, the account/delegation layer, or both. The two approaches are complementary rather than competing; asset-level gates matter most for regulated or issuer-controlled tokens where compliance must live in the transfer path, while account-level delegation is the more practical default for general-purpose agent spending across existing tokens.

As of late June 2026, the proposal's author is coordinating with the authors of ERC-8226 (Regulated Agent Mandate), a closely related identity-and-compliance-focused standard, to see whether the two specifications should merge rather than compete; a working group and formal pull request are expected to follow. Worth tracking: whether the spend-mandate concept converges into ERC-8226 or ships as a separate standard, and whether any wallet providers or token issuers commit to implementing either approach.