"The most profound economic changes come not from replacing existing players, but from transforming their roles and incentives within the ecosystem." — Vitalik Buterin
One-Block Delay and Referencing Order-Invariant Actions in Based Rollups:
Based rollups can reference current Ethereum state, but they still face a simulation challenge regarding the next block's state. A based rollup builder constructing rollup block alongside Ethereum block does not know the exact state of Ethereum that will exist after Ethereum block is finalized.
This leads to a general one-block delay in referencing the host state because the rollup cannot reference the current, still-determining Ethereum state. However, a zero-block time lag on communication between Ethereum and a based rollup is possible in a specific scenario: if the rollup block references only the outcomes of order invariant actions on the host chain.
When a based rollup block is submitted atomically with such order invariant actions on Ethereum, the rollup's state transition function can confidently read the outcomes of those specific actions in the same block, maintaining simulatability. This mechanism allows for faster host-to-rollup communication by focusing on the subset of host chain outcomes that are predictable and non-contentious.
Gloated Rollups are a special case for zero-block communication L2' when referencing predictable, order-invariant actions included atomically on the host chain.