TBNGovernance
Asset-level spending limits and recovery: should rate limiting live in the asset rather than the account?
Publication: Ethereum Research - Latest topics
Author: dlebee
Source published: 01/11/2026, 17:15:34 UTC
Briefing created: 01/11/2026, 17:44:30 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 01/11/2026, 17:28:26 UTC.
Briefings
This briefing outlines a proposal to enforce spending limits at the token asset level rather than the account level, addressing gaps in current defenses like allowances and delegation. The core finding is that asset-level enforcement survives delegation changes and delegation replacement, whereas account-level limits fail. Key facts include a 14-day delay for security-strengthening changes and immediate activation for security-weakening changes. The proposal suggests a system contract for native ETH enforcement and a shared registry for ERC-20 tokens, though implementation costs and scalability remain open questions.
Key points
- Current key-compromise defenses enforce policy in the account's code, but allowances allow transfers without re-entering wallet validation logic, and delegation replacement can strip account-level policies.
- An asset-level check binds every balance-reducing path regardless of the initiating application, surviving delegation changes, whereas account-level limits fail under these conditions.
Context
The proposal addresses gaps in current defenses where account-level policy binds only while the account's code is in the transfer path, specifically failing against allowances and delegation replacement.
Limitations
Evidence is limited to a sketch of the proposed architecture; specific implementation costs, scalability constraints regarding mempool validation, and the feasibility of native ETH enforcement without consensus-layer changes remain unaddressed.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 01/11/2026, 17:44:30 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeibbo2i4tea6zr5x53zwdguqbs623yjbrhou2uis4d2e5apernadeu