Ethereum's proposed transaction assertions still depend on who sets the financial limits
A draft upgrade could add safety checks to Ethereum transactions
Ethereum Foundation researchers published work on Oct. 5 showing how transaction assertions could enforce rules over the outcome of a trade. The draft standard, called EIP-7906, would let wallets and protocols check what happens after a transaction runs and block results that fall below a set limit.
The catch is that the proposal does not decide what that limit should be. A bad trade could still go through if the person or app building the transaction picks a weak limit.
Key numbers and dates
- EIP-7906 was created on Feb. 21, 2025 and remains a draft as of Oct. 9.
- It depends on EIP-8141's frame transaction system, which is scheduled for the Hegotá upgrade.
- EIP-7906 itself is listed as "considered" for Hegotá, not yet confirmed.
- The Ethereum Working Group announced the Clear Signing standard on May 12, 2026.
How current safeguards already work
Uniswap v3, a popular decentralized exchange, already rejects trades that do not meet a minimum output amount. If you request an exact-input swap, the router will fail the transaction if the tokens you receive fall below your set minimum. For exact-output swaps, it blocks the trade if the cost exceeds your maximum.
However, Uniswap's own developer guide warns that setting that minimum to zero is risky in production. The software does not choose the limit for you; it only enforces whatever value you supply.
Other tools exist alongside these limits. The Clear Signing standard gives wallets structured descriptions of what a transaction asks for. Safe smart accounts offer guards that check transaction parameters before execution and the account state after. Simulation tools can predict effects, though blockchain state can change before a transaction is processed.
What the new proposal would add
EIP-7906 builds on EIP-8141's ordered frame system, which separates validation steps from action steps. It adds read-only frames at the end of a transaction that let assertion code inspect the final state and reject results that break a rule.
Three main instructions would handle this: one would list net changes and events, another would retrieve values by key, and a third would make event data available. The scope covers ETH balances, storage changes, newly deployed contracts and code hashes. Token-balance checks would require interpreting contract storage.
The proposal could support policies beyond simple swap limits. An account could require its control configuration to stay intact, or a policy could restrict approvals and check effects across multiple contracts in a trade route.
Where the vulnerability lies
The security guidance for EIP-7906 calls for immutable, non-upgradeable assertion targets so a transaction cannot alter the enforcement contract after validation begins. It also recommends using reference values fixed at signing time or drawn from the transaction's starting state, preventing the execution body from rewriting the data used for comparison.
Even unchanged assertion code can read compromised data. Prices, registries, proxies and other state can be modified by the execution body before the assertion runs. If a trade shifts the price used to judge whether the result is acceptable, reading the real final state does not fix the comparison.
A failed assertion would revert the execution body, but consumed gas charges and validation-prefix changes would remain. The proposal does not require every transaction to include an assertion; an account relying on one must configure its validation logic to require the specific frame without a bypass path.
Why this matters for everyday users
The research highlights a gap between having a safety check and having a meaningful one. A check can measure a result and reject anything below a floor, but if the floor itself is set too low, the check provides little real protection. The financial limit must come from independent policy, not from the same transaction builder it is supposed to constrain.
What happens next
EIP-8141 is scheduled for inclusion in the Hegotá upgrade, while EIP-7906 remains only considered. The draft is not yet finalized, and its implementation details may change.
Sources
Newisty Editorial Team covers technology, cryptocurrency, digital products, online platforms, developer tools and the wider digital economy. Our content is researched from official sources, company announcements, public documentation, market data and other primary or reputable sources. Articles are reviewed and edited before publication for clarity, accuracy and useful context.