# Ethereum Proposes Asset-Level Spending Limits for Wallets > Source: > Published: 2026-06-18 20:32:47.497883+00:00 # Ethereum Proposes Asset-Level Spending Limits for Wallets NewsBTC reports that Ethereum developers are discussing an **asset-enforced spend mandate** that would place spending limits at the token level for delegated wallets and AI-driven agents. The draft proposal, described by NewsBTC as an early discussion, would let a token consult a gate before transfers and enforce rules such as per-transaction caps, expirations, allowed tokens, and revocation status. The stated aim is to reduce onchain loss vectors when agents or session keys act without per-transaction user signatures. NewsBTC notes the proposal is not a finalized ERC standard and remains under early community discussion. ### What happened NewsBTC reports that Ethereum developers are discussing an **asset-enforced spend mandate**, a draft idea that would embed spending rules at the token layer rather than only at wallet or session-key layers. According to NewsBTC, the proposal would let an asset consult a gate before allowing transfers and could enforce per-transaction **caps**, **expiration** windows, allowed-token lists, and **revocation** status. NewsBTC characterizes the text as an early discussion draft and not a finalized ERC standard. ### Technical details Editorial analysis - technical context: The core design moves enforcement from wallets and offchain policy to the asset contract itself, which is technically feasible on Ethereum through token contract logic and hooks. Industry-pattern observations note that token-level checks add a defensive checkpoint that can limit the impact of broad approvals or compromised keys, but they also increase the complexity of token contracts and require careful gas and UX trade-offs. ### Context and significance As onchain integrations with autonomous software and delegated workflows grow, practitioners have repeatedly flagged excessive approvals and session-key misuse as common loss vectors. Embedding mandates at the asset layer addresses one vector by making controls portable with tokens, which could reduce the blast radius when session keys or agent keys are abused. ### What to watch - •Whether the discussion yields a formal ERC proposal and the specific interface semantics for mandates. - •Gas and composability implications if tokens must check external gates or maintain additional state. - •Wallet and dApp UX changes required to surface token-level mandates to end users. Observers should track community discussion threads and any formal repository or EIP/ERC issue that surfaces the draft into the standards process. NewsBTC has not reported any vendor or major token issuer endorsements in the draft, and the proposal remains in early community discussion. ## Scoring Rationale The proposal addresses a practical security gap for AI-driven and delegated onchain payments, which matters to engineers integrating agents with wallets. It is not yet a standard or broad industry shift, so the immediate impact is moderate. Practice with real Payments data 90 SQL & Python problems · 15 industry datasets 250 free problems · No credit card [See all Payments problems](/problems/datasets/payments)