FOLLOW THE MECHANISM
- 1Execute
- 2Publish
Required data and a state claim reach the base chain.
- 3Challenge
- 4Finalize exit
Accepted claims support withdrawals after the required process.
A conceptual sequence. Real implementations can add steps, intermediaries, and conditions.
A claim that can be challenged
An optimistic rollup executes transactions outside its settlement chain and posts commitments plus the data needed for verification. A proposed state update is treated as acceptable unless a valid challenge demonstrates an error within the protocol’s rules. This does not mean every user must personally recompute every transaction. It means the security argument depends on appropriate data access, an effective dispute mechanism and participants able to use it when needed.
Fraud proofs connect disagreement to enforcement
A challenger disputes a claimed state transition, and the system resolves the dispute through a defined proof process. Some designs narrow disagreement to a small computation that a base-layer contract can check. Bonds and penalties can discourage invalid claims or challenges. The exact implementation, permission model and settlement behavior differ across rollups and versions. A website describing a future permissionless proof system is not evidence that the currently deployed contracts already provide it.
Why withdrawal can take longer
A canonical withdrawal normally needs the relevant claim to survive the dispute process before the settlement-layer bridge releases funds. That introduces a protocol-specific waiting period; this atlas does not assign one universal duration to all optimistic rollups. A fast bridge can pay earlier using another party’s liquidity, but that is a separate service with its own price and risk. It does not remove the original dispute window from the underlying rollup.
Availability and censorship remain important
Watchers need data to identify invalid execution, and valid challenges must be includable before relevant deadlines. Sequencer downtime can delay local transactions even if finalized balances remain protected. Forced inclusion, fallback ordering and upgrades determine what users can do without operator cooperation. A rollup can have sound fraud-proof logic while an administrator can still replace critical contracts. Understanding the system requires examining both the proof mechanism and the permissions that surround it.
MAKE IT CONCRETE
Illustrative dispute
An operator claims that a balance became 90 after a valid transfer of 5 from 100. Re-execution produces 95. A working dispute mechanism identifies the mismatch and prevents that incorrect claim from becoming accepted settlement.
FAILURE PATHS & COMMON MISREADINGS
Where the model can break
- The word optimistic does not mean errors are merely ignored.
- Fast-liquidity exits add a different counterparty or contract path.
KEEP EXPLORING