State Overlay Consistency Checker

To check state visibility across transaction execution frames, you run a consistency checker against a transaction trace to verify cross-frame visibility, overlay inheritance, and gas propagation invariants for nested calls.

Gas mis-accounting happens during nested smart contract calls when state-visibility violations occur across execution contexts, causing silent gas under-charging because deployed code and storage changes are not properly visible to subsequent frames.

State overlay consistency in multi-frame transactions ensures that storage changes and deployed code from operations like CREATE or DELEGATECALL are visible to subsequent execution frames, preventing inconsistent state and gas under-charging within a single transaction.

To audit a CREATE and CALL sequence for write-read consistency, inspect the transaction trace's frame hierarchy, code visibility, storage overlays, and gas accounting to ensure deployed code and SSTORE changes are visible to subsequent frames.

You need to verify state overlay consistency when auditing complex contract deployments that use multi-frame patterns like CREATE2 followed by CALL or DELEGATECALL, ensuring deterministic behavior and preventing silent gas under-charging.

This consistency checker targets multi-frame patterns within a single transaction, so transactions without nested execution frames or complex contract deployments do not require cross-frame visibility checks for code, storage, or gas propagation.