A rule for the transaction’s final outcome
Ethereum Foundation describes native transaction assertions as a proposed way for onchain code to inspect the net state changes after a transaction’s actions have run. Instead of checking only what actions were requested, an assertion would compare the starting and final values against a rule.
The rule would be included in the transaction and signed along with its actions. The assertion would use read-only logic to evaluate the result. If the rule failed, the actions would revert.
EIP-7906 is one possible route
The Ethereum Foundation presents EIP-7906 as one possible implementation. It builds on the frame transactions defined in EIP-8141. The Foundation says EIP-8141 is scheduled for Hegotá, while EIP-7906 has reached “Considered for Inclusion” but is not confirmed for the upgrade.
That status matters: EIP-7906 is a proposal under consideration, not a confirmed upgrade feature. The Foundation describes it as an approach to transaction assertions, rather than the only possible implementation.
A failed rule still has a cost
Under the EIP-7906 approach described by the Ethereum Foundation, if the rule is violated, the entire execution body would revert. The transaction would still remain in the block with a failed status, and the gas payer would be charged for the gas consumed.
EIP-7906 would not require every transaction to include an assertion. The Foundation notes that whoever builds the transaction could leave one out, so the check would not be automatic for all transactions.
The rule must reflect the user’s intent
An assertion is only protective if its rule actually rejects outcomes the user wants to prevent. The Ethereum Foundation warns that a compromised frontend could write a permissive assertion that allows an attack. It says a useful rule must instead come from independently approved user intent, a standing account policy, or protocol logic that the compromised component cannot change.