Ethereum's EIP-7906 assertions protect traders only when someone besides the app sets the floor

Ethereum already enforces some loss limits at execution time. Uniswap v3's swap router rejects an exact-input swap that returns less than amountOutMinimum, and an exact-output swap that spends more than amountInMaximum ^[5]. Uniswap's own single-swap guide sets the minimum output to zero in its simplified example, warns that this is risky in production and points developers to an SDK, a price oracle or another data source for a safer value ^[6]. The check runs the same way whatever the floor is. A floor derived from a quote that was already poor enforces the poor quote correctly, according to CryptoSlate's analysis ^[7].

EIP-7906 widens what a check can see. Its proposed instructions, TXTRACE, TXDIFF and EVENTDATACOPY, enumerate net changes and events, retrieve values by key and make event data available to the assertion ^[12]. Their scope covers native ETH balances, storage changes, newly deployed contracts and code hashes. Token balances take more work, because an assertion would have to interpret the token contract's storage before enforcing a limit ^[12]. The instructions measure the outcome (or rather the net outcome ^[13]), and someone still has to write the limit. CryptoSlate puts the question as who supplies the rules and whether the app assembling the transaction can weaken them ^[4].

Existing tools each cover a different piece. The Ethereum Working Group's Clear Signing standard, announced May 12, 2026, gives wallets structured descriptions to show a signer, backed by independent reviews and attestations ^[8]. It explains the request and imposes no minimum result ^[8]. Simulation predicts effects against one chain state, and that state can change before the transaction reaches a block ^[9]. Safe guards come closest, checking a transaction's parameters before execution and the Safe's final state afterward ^[10].

The upgrade record commits to frame transactions and keeps assertions as a candidate ^[2]. EIP-7906 has been a draft for 595 days, counting from Feb. 21, 2025 to the Oct. 9 status ^[1][19]. If it misses Hegotá, frames ship without post-transaction assertions, and guards like Safe's stay the main way to check a final state ^[10]. Should it ship with apps still writing the policies, users get exact enforcement of whatever floor the app picked ^[4]. The third case has wallets or account providers writing policies from inputs the app does not control. CryptoSlate's analysis says protection needs exactly that: independent policies, required checks and trustworthy inputs ^[18]. A protocol relying on assertions takes on a related obligation in its own protected function ^[16].

I think the first protection traders get from assertions will come from rules that need no price at all. An account might insist that its control settings come out of the transaction unchanged, or a policy might limit which approvals are granted and verify the effects on every contract a route touches ^[17]. Neither rule depends on a quote the builder hands over. The counter-case is that a loss floor is the rule traders most need, and it still requires a price input that someone other than the app can stand behind ^[18]. That view is wrong if the first wallets to support EIP-7906 ship loss floors built from their own price sources.