Skip to content
Blockchain Post

News on how crypto works

How does a SyncSwap trade settle from Scroll to Ethereum?

How zero knowledge rollups support decentralized exchanges: they run swaps on a layer 2, batch them, and use validity proofs for Ethereum settlement.

The Blockchain Post Editors4 min read#d38a11

How does a SyncSwap trade settle from Scroll to Ethereum?

A zero-knowledge rollup executes swaps on a layer 2, then batches transactions for verification on Ethereum. That is how zero-knowledge rollups support decentralized exchanges: they move trade execution off Ethereum while using it to verify and settle the rollup’s state.

A Scroll swap executes before it settles on Ethereum

A swap starts as a signed transaction sent to Scroll’s sequencer. The sequencer orders it with other transactions and includes it in an L2 block, where the decentralized exchange’s contracts execute the trade against a liquidity pool. The resulting token balances update on Scroll.

For a SyncSwap trade on Scroll, think of the pool as the part that determines the swap’s state change: the signed request goes in, the pool contract executes, and updated balances come out. A receipt can show that the transaction was included and executed on Scroll. That is an L2 confirmation, not yet the same event as Ethereum finalizing the rollup’s state.

Scroll describes this lifecycle in three stages: confirmed after execution in an L2 block, committed after batch data is submitted to Ethereum, and finalized after the batch’s validity proof is verified on Ethereum. The distinction matters when reading a receipt: the visible L2 result comes first, while Ethereum settlement follows later. For a practical next step, SyncSwap gives you the DEX context for understanding where this kind of swap takes place.

Batching shares settlement work across swaps

After execution, rollup infrastructure groups transactions into batches. A validity proof verifies that the proposed state transition follows correctly from those transactions. Ethereum’s rollup contracts check the proof and accept the updated state when verification succeeds.

Batching spreads shared settlement overhead across many transactions. Instead of asking Ethereum to execute every swap individually, the rollup publishes batch data and a proof covering the state changes. This increases transaction capacity by shifting execution off Ethereum and makes each transaction share part of the work involved in posting data and verifying a proof.

The trade-off is that a swap’s progress has stages. Batching can reduce the settlement work allocated to each transaction, but a user waiting for Ethereum finality must wait for the batch to be committed and its proof verified. For someone making an occasional swap, it helps to distinguish the quick L2 receipt from the later settled state rather than treating them as one timestamp.

The published data also matters. It contains information needed to reconstruct the rollup’s state, so independent parties can check balances and state changes. The proof verifies the proposed transition; the data makes it possible to rebuild the state behind that transition. Both are part of how the rollup connects offchain execution to Ethereum settlement.

DEX users rely on several connected contracts and operators

A completed rollup swap depends on more than the pool contract. The DEX contract applies the trade to its liquidity pool, the sequencer orders and executes the transaction, and the rollup contracts on Ethereum handle batch commitments and proof verification. Each part plays a different role in producing the updated balances and settled state.

That chain explains why an L2 receipt is useful but does not tell the whole settlement story. It shows the trade executed on Scroll; the batch and proof steps establish the rollup’s state on Ethereum. For an occasional DEX user, the practical takeaway is simple: check which stage a transaction has reached when you need to know whether it has executed on the L2 or settled on Ethereum.

Related questions

Are zk rollup swaps private?

Generally, no. Transaction details are publicly inspectable, and rollups publish data that supports reconstruction of their state. A validity proof verifies computation; it does not by itself make a swap confidential.

How does zk rollup verification differ from optimistic rollup verification?

A zk rollup submits a validity proof for Ethereum to verify. An optimistic rollup uses a challenge-based verification model, where a proposed state can be contested during a challenge period. To understand a particular swap’s status, follow its L2 execution through batch commitment to proof verification, as described in Scroll’s transaction lifecycle and Ethereum’s zk rollup overview.