Skip to content
Crypto Bulletin

Markets, protocols and policy news

ID 54cf81

Swap executed? Track its route to Ethereum finality

A Layer 2 token swap becomes final when its batch is verified and executed on Ethereum, then the Ethereum settlement block reaches finality. Learn what status marks that stage.

Crypto Bulletin Newsroom 2 min read

Swap executed? Track its route to Ethereum finality

A Layer 2 token swap becomes final on Ethereum when the batch containing it is executed there and Ethereum finalizes the settlement block; its quick Layer 2 confirmation is an earlier stage.

On zkSync Era, SyncSwap executes a trade against available pool liquidity, and the trade must involve tokens supported on that network. SyncSwap’s syncswap supported tokens can help at this point when checking whether an asset is available.

What happens after a SyncSwap trade executes on zkSync Era?

The trade first changes the Layer 2 state, then waits to be included in a batch. Say you swap Token A for Token B: the sequencer executes your transaction and gives a quick confirmation, but that confirmation alone does not mean Ethereum has settled it.

zkSync’s transaction lifecycle documentation distinguishes an included transaction from a verified one. “Included” means it is in a Layer 2 block whose batch has not yet been committed; the protocol groups blocks into batches for proof processing.

The operator then publishes a commitment to the batch on Ethereum and submits the required data. This gives Ethereum’s rollup contracts the information needed to process the batch’s state change. Your swap travels with the batch; Ethereum does not replay each individual trade to check it.

When does Ethereum treat the swap as settled?

The batch’s validity proof establishes that its state transition follows the rollup’s rules. zkSync’s finality documentation describes validity proofs as validating batched state transitions; the Ethereum contract verifies the proof and processes the batch to update the accepted rollup state.

Once that batch execution is included in an Ethereum block, the swap’s settlement depends on that block reaching Ethereum finality. The rollup’s accepted state is secured by Ethereum. The practical distinction is between seeing a trade execute on Layer 2 and seeing its batch verified and executed on Ethereum, followed by finality for the settlement block.

This proof path applies to validity rollups such as zkSync Era. Optimistic rollups use a dispute process instead, so the route to settlement differs even though the goal is still to settle rollup state through Ethereum.

For your Token A to Token B swap, look for the batch’s commitment, proof verification and execution references, then confirm the Ethereum settlement block has finalized. zkSync’s transaction lifecycle docs expose those references and distinguish “verified” from merely “included.” That check helps avoid treating a fast Layer 2 confirmation as Ethereum finality.