A fraud proof is the mechanism that gives teeth to an optimistic rollup’s “assume it’s valid unless proven otherwise” model. During the challenge window after a batch is posted, anyone running a full node of the rollup can check the claimed state transition against what actually should have happened. If they disagree, they submit a fraud proof: evidence, verified by a contract on L1, demonstrating that the posted result was wrong.
A successful fraud proof causes the disputed state transition to be rolled back, and the party responsible for posting the incorrect batch typically forfeits a bond they had to post to participate — the economic deterrent that makes posting bad batches a losing bet.
Why it matters
Fraud proofs are what makes an optimistic rollup’s security “anyone can check and object,” rather than “trust the operator.” But that only holds if at least one honest, well-resourced party is actually watching and willing to submit a challenge within the window — which is why the health of an optimistic rollup’s challenger set matters as much as the mechanism’s existence on paper.
Example
A sequencer posts a batch that credits a user more tokens than their transactions justify. A watcher running the rollup’s software independently notices the discrepancy and submits a fraud proof before the challenge window closes, reverting the bad batch.
Related · Rollups
Not financial advice.