What Are Fraud Proofs? How Optimistic Rollups Stay Secure

Fraud proofs are the mechanism optimistic layer 2 rollups use to catch and reverse invalid transaction batches, letting any participant challenge a submitted state update during a set window of time by proving, using the publicly posted transaction data, that the sequencer's claimed result was incorrect.

This mechanism is the reason optimistic rollups like Arbitrum and Optimism can offer strong security guarantees without generating a cryptographic proof for every single batch, but it's also the reason withdrawals from these networks take roughly a week by default.

The "optimistic" assumption

Optimistic rollups get their name from a core design choice: they assume every submitted batch of transactions is valid unless someone proves otherwise. This is far cheaper computationally than generating a cryptographic validity proof for every batch, the approach used by ZK rollups instead, but it requires a mechanism to catch and correct fraud after the fact, which is exactly what fraud proofs provide.

How the challenge process works

When a rollup's sequencer submits a batch, that batch enters a challenge window, typically about seven days on most major optimistic rollups.

• During this window, the transaction data behind the batch is publicly available (posted to Ethereum, as covered in our data availability guide), meaning anyone can independently re-execute the transactions and check whether the claimed result matches.
• If a participant, often called a "watcher" or "verifier," finds a discrepancy, they can submit a fraud proof to a smart contract on the base layer, essentially demonstrating step by step that the sequencer's claimed outcome doesn't match what honest re-execution produces.
• If the fraud proof is validated on-chain, the invalid state transition is reverted, and the party responsible for the fraudulent batch typically loses a bond they were required to post, which is used in part to reward the successful challenger.
• If no one successfully challenges the batch within the window, it's treated as final and immutable.

Why the challenge window takes about a week

The length of the challenge window is a deliberate security parameter, balancing user convenience (a shorter window means faster finality) against giving honest participants realistic time to detect fraud, construct a proof, and submit it on-chain, accounting for network delays, computational time, and simple human response time. A week has become the informal industry standard across most major optimistic rollups, though the specific number is a protocol design choice rather than a strict technical requirement.

Interactive vs. non-interactive fraud proofs

Different optimistic rollups implement fraud proofs somewhat differently. Some use a multi-round "interactive" dispute process, where the challenger and the original submitter narrow down their disagreement step by step until they identify the exact single computational step in dispute, which is then verified on-chain. Others use more direct, single-round fraud proof submissions. The interactive approach can reduce the on-chain computation needed to resolve a dispute, at the cost of a more complex multi-step process.

Practical implications for users

Withdrawal delay. The most tangible everyday impact is that natively withdrawing funds from an optimistic rollup back to Ethereum takes about as long as the challenge window, since the system needs that time to remain open to potential fraud proofs before treating a batch as final. Third-party liquidity providers commonly offer faster withdrawals for a fee, effectively fronting users the funds and assuming the waiting-period risk themselves.

Reliance on honest watchers. The fraud-proof system only works if at least one honest, capable party is actually watching for fraud and willing to submit a proof if they find it. In practice, this typically includes the rollup's own team, independent researchers, and sometimes bonded "watchtower" services, though this remains a real assumption rather than a guarantee baked into the cryptography itself, unlike the mathematical guarantees that back validity proofs.

Fraud proofs vs. validity proofs

Factor	Fraud proofs (optimistic rollups)	Validity proofs (ZK rollups)
Default assumption	Valid unless proven fraudulent	Proven correct before acceptance
Requires an active challenger	Yes	No
Withdrawal delay	~7 days (challenge window)	Much shorter
Computational cost	Lower ongoing cost	Higher, proof generation is intensive

Bottom line

Fraud proofs let optimistic rollups offer strong, Ethereum-anchored security without the computational overhead of generating a cryptographic proof for every batch, but the tradeoff is a built-in challenge window, typically about a week, during which withdrawals are delayed and the system depends on at least one honest party actively watching for fraud. Understanding this mechanism explains both why optimistic rollups have historically been easier to build with full EVM compatibility and why their withdrawal experience differs from the faster finality offered by validity rollups, covered in our optimistic vs. ZK rollups guide.