An optimistic rollup is a Layer 2 scaling approach, commonly used on Ethereum, that executes transactions outside the base layer while using it for data availability and settlement. “Optimistic” means that proposed execution results are accepted provisionally, rather than requiring a validity proof for each update. Incorrect state claims can be disputed during a defined challenge period before they are finally accepted.
Execution, Data and Costs
An optimistic rollup typically uses a sequencer to order transactions, which are executed on Layer 2 and grouped into batches. Most computation and detailed state storage stay on the rollup. Transaction data is published to Ethereum, alongside state commitments that summarize the claimed results. A commitment, such as a state root, is not a substitute for the data: observers need the underlying transaction data to reconstruct and check execution. Ethereum does not routinely re-execute every rollup transaction.
Moving execution off the base layer increases processing capacity, while compression and shared data-posting and settlement costs generally reduce per-transaction fees. Batching does not require parallel execution or guarantee a particular saving; fees still depend on demand, data costs and the rollup’s design. Many systems also support smart contracts and Ethereum-compatible applications, although full Ethereum Virtual Machine (EVM) compatibility is not part of the definition.
Disputes, Confirmations and Withdrawals
Observers can independently check the published data and resulting state. Eligible challengers can dispute an incorrect state claim within the protocol’s challenge period using a fraud proof, also called a fault proof. The dispute mechanism resolves the contested computation under the protocol’s rules, and a successful challenge causes the incorrect claim to be rejected. This is targeted verification of disputed claims, not immediate base-layer verification of every batch’s execution.
A quick confirmation from an optimistic rollup is therefore different from final settlement. The challenge window delays final acceptance of state claims and can delay withdrawals through the protocol’s standard bridge. A transaction may appear completed on Layer 2 while its associated withdrawal is not yet available on Ethereum. Timing depends on the protocol and base-layer finality; there is no universal withdrawal period.
Looking for liquidity, exploring on-ramp/off-ramp services, or seeking expert guidance?
Get startedSecurity Conditions and Risks
An optimistic rollup depends on available transaction data, a functioning dispute mechanism and an honest participant who can submit a challenge in time. If data cannot be obtained, observers cannot independently reconstruct execution. If challenges are blocked or cannot be completed within the required window, incorrect claims may escape correction. Fraud proofs are therefore conditional safeguards, not an unconditional guarantee that every proposed result is valid.
Deployed systems can also retain smart-contract bugs and operator-control risks. Sequencer outages or censorship may affect transaction inclusion, while upgrade powers and challenger restrictions can change the practical trust assumptions. Readers should distinguish the intended protocol design from the protections actually enabled in a particular deployment.
Optimistic Rollups vs. Validity Rollups
- Execution Checks: An optimistic rollup relies on challenges to incorrect claims, whereas a validity rollup, often called a ZK-rollup, verifies execution proofs before accepting state updates. This changes how correctness is established, not whether settlement needs the base layer.
- Timing and Overhead: Validity rollups avoid the fraud-challenge window, but proof production, submission and base-layer finality still affect settlement. Proving work and dispute costs create different overheads, so neither approach is inherently more flexible or universally cheaper.