Ethereum Transaction Inspection Proposal Faces Loose Standards Concerns

Ethereum (ETH) has seen a proposal to inspect transaction outcomes after execution, though loose inspection criteria risk allowing unwanted results. For EIP-7906 to serve as an effective safety measure, wallets and protocols must enforce strict standards and prevent transaction builders from lowering them.
The Ethereum Foundation published research on October 5 about post-execution checks for balance, storage changes, and events in transactions. The candidate implementation EIP-7906 proposes a read-only POST_TX framework that operates after transactions conclude. Still in draft form, it remains unclear if it will be included in the Hegotá upgrade.
Transaction signatures capture approved requests but not final outcomes; changes to code or blockchain state before execution can alter results. The Foundation cited sandwich attacks—where swap prices shift based on transaction order—as an example of outcome mismatches. EIP-7906 is designed to enumerate transactional changes via TXTRACE, verify storage values with TXDIFF, and read event data using EVENTDATACOPY.
However, the system does not record all intermediate storage changes—only initial and final values. The proposal does not automatically protect all transactions; wallets must include required assertions. For protocol-level protection, targeted functions should mandate POST_TX checks, rejecting transactions with missing or alternative validations. The Foundation warned that overly lenient rules could allow attacks if frontend components are compromised, similar to how setting minimum swap receive amounts to zero in Uniswap can be risky.
Even if assertions fail, transaction costs remain non-refundable. Per the EIP-7906 draft, failed POST_TX checks roll back execution but leave transactions marked as failed on-chain with gas fees paid. Verified changes stay intact. The Foundation stressed that protective logic should reside in reversible execution contexts and avoid untrusted code during verification.
Insufficient gas for assertions also triggers failure. Protection requires not only assertion logic but also a scope of reversibility. The proposal notes risks if referenced oracles or registries change mid-transaction, suggesting fixing values at signing time or referencing initial block states. However, price movements within the same block before transaction execution remain possible.
EIP-7906 builds on EIP-8141, which the Foundation classified as Hegotá-ready but remains in review for EIP-7906. Real-world wallet and protocol adoption is still undetermined. Earlier research explored post-execution state verification, with this draft highlighting that protection requires not just functional checks but also enforcement of user-approved standards to prevent transaction builders from weakening them.
Korean Source
This article is an English localization of a Korean-language crypto news report. Original headline: 이더리움 거래 검사 제안, 느슨한 기준은 못 걸러