An optimistic rollup executes transactions outside a base blockchain while publishing the data needed to reconstruct its state on that chain. Proposed state claims are accepted provisionally rather than accompanied by a validity proof for every update. A challenge process allows incorrect claims to be disputed before they become usable for protected actions such as withdrawals.
Why challenges need data
Independent participants can replay published transactions and compare their result with a proposed state. If they disagree, a fault-proof or fraud-proof process resolves the disputed computation under the protocol's rules. A successful challenge invalidates the incorrect claim; it does not necessarily reorganize the rollup's transaction history.
This model depends on data availability, functioning dispute contracts and an honest participant able to challenge within the required time. Permission to propose or challenge, bonds and emergency controls vary by deployment.
Confirmation and withdrawal are different
A sequencer may provide a quick confirmation before the transaction data reaches the base chain. Finality of that data and the waiting period for a bridge withdrawal are separate milestones.
Native withdrawals commonly include a challenge-related delay. Faster liquidity-based exits introduce their own fees and dependencies. Optimistic design does not remove smart-contract, upgrade or operator risks, and “no challenge” is not itself a cryptographic proof that the computation was correct.