Ethereum Explores Native Transaction Assertions to Guarantee Final Execution Outcomes
EIP-7906, niyet ve sonuç uyuşmazlıklarını önlemek için işlem sonrası durum farkı denetimi getiriyor.
1Limits of Cryptographic Signatures
Ethereum strictly executes authorized calldata without evaluating whether the net result matches user expectations. A valid signature commits to targets, values, and payloads, but execution outcomes depend entirely on runtime contract state and code. Changes in state or proxies can cause severe financial losses despite valid signatures.
2Intent Versus Outcome Mismatches
User transaction failures fall into intent or outcome mismatches. In the Bybit and BadgerDAO attacks, compromised frontends altered signed requests. Conversely, an Aave and CoW swap of 50.4 million dollars executed with extreme slippage, returning just 36,000 dollars because execution lacked independent state-level validation rules.
3Gaps in Current Defenses
Existing defenses like Clear Signing and pre-execution simulations fail against runtime state shifts and local malware. Furthermore, custom smart contract guards like Uniswap checks or Safe hooks require preconfigured functions. They cannot inspect comprehensive net state changes or directly read unexposed internal proxy implementation storage slots.
4Mechanism of Native Assertions
Native assertions allow onchain logic to inspect the complete set of net state changes and emitted events post-execution. Signed alongside transaction actions, read-only assertion rules verify initial versus final values. If these predefined rules fail, the entire execution body reverts, effectively protecting user balances and permissions.
5Architecture Under EIP-7906
EIP-7906 implements assertions using EIP-8141 frame transactions. It attaches a read-only POST_TX frame at the end of the transaction sequence as a static call. This frame evaluates state changes without altering state. If an assertion fails, execution reverts while charging the caller gas.
6Three Dedicated EVM Opcodes
EIP-7906 introduces three specific opcodes restricted to the POST_TX frame. TXTRACE enumerates net state differences and events, TXDIFF retrieves initial and final values for specific addresses or storage slots, and EVENTDATACOPY copies event data to memory. Intermediate writes reverting to original values are completely excluded.
7Enforcement and Integration Requirements
Because EIP-7906 does not mandate assertions protocol-wide, builders must actively configure them. Wallets must inject rules derived from simulation or standing account policies into frame transactions. Protocols must verify that incoming calls originate from frame transactions carrying valid assertions, creating compatibility hurdles for immutable deployed contracts.
8Expanding Delegation and Solvers
Beyond fundamental exploit protection, native assertions enhance programmatic delegation and solver architectures. Users can constrain automated agents by enforcing outcome thresholds rather than micro-managing calldata. Similarly, solver protocols can define exact settlement conditions within a single chain transaction, allowing solvers complete routing freedom.
9Trillion Dollar Security Initiative
Part of the Ethereum Foundation's Trillion Dollar Security initiative, EIP-7906 has reached Considered for Inclusion status alongside EIP-8141 for the Hegotá upgrade. The research team is actively collecting feedback from wallet and protocol developers to refine opcode design, state inspection models, and rule sources.