What Is a Fraud Proof in a Layer 2 Rollup?
A fraud proof is what actually enforces an optimistic rollup's assumption that transactions are valid — and it depends on someone actively watching.
Fraud proofs are the specific mechanism that makes optimistic rollups' underlying trust model actually work — without them, the "optimistic" assumption that transactions are valid by default would have no real enforcement behind it at all.
Why an Enforcement Mechanism Is Necessary at All
An optimistic rollup assumes submitted transactions are valid by default, processing them quickly without requiring immediate proof of correctness — this only remains secure if there's a genuine, working mechanism to catch and correct anything that turns out to actually be invalid.
What a Fraud Proof Actually Is
A fraud proof is a specific piece of evidence submitted to Layer 1, during the challenge period, demonstrating that a specific transaction or state transition on the rollup was invalid — essentially a formal, verifiable claim that says "this specific thing was processed incorrectly, and here's the proof."
Who Can Actually Submit a Fraud Proof
In most designs, submitting a fraud proof isn't restricted to any special, privileged party — anyone actively monitoring the rollup's activity who identifies an invalid transaction can submit the proof, meaning the security of the system depends on at least some participants actually watching and being willing to challenge invalid activity.
Why This Creates a Dependency on Active Monitoring
Because anyone can submit a fraud proof, but no one is specifically required to, the system's security in practice depends on the assumption that enough independent parties are actually watching closely enough to catch and challenge genuinely invalid transactions within the challenge window — a assumption worth understanding rather than taking entirely for granted.
Why an Unsubmitted Fraud Proof Means an Invalid Transaction Could Finalize
If no one submits a valid fraud proof during the challenge period — whether because no one caught the issue, or because monitoring simply wasn't happening closely enough — an actually invalid transaction could finalize as if it were valid, since the challenge period existing doesn't guarantee someone will actually use it.
Why This Isn't Purely Theoretical Concern
This dependency on active, willing challengers is a genuine, structural aspect of how optimistic rollups' security model works — it's part of why understanding the assumption matters, rather than treating the fraud proof mechanism as an automatic, guaranteed safeguard that requires no actual participation to function.
Why Some Newer Rollup Designs Avoid This Dependency Entirely
Rollups using validity proofs (sometimes called zero-knowledge proofs) instead of the optimistic-plus-fraud-proof model prove transaction correctness immediately and cryptographically, removing the dependency on someone actively monitoring and choosing to challenge — a different trade-off, generally with faster finality but different computational requirements.
What This Means for Evaluating a Specific Optimistic Rollup
Understanding that the rollup's security depends partly on an active ecosystem of participants actually willing and able to submit fraud proofs when needed — a rollup with minimal independent monitoring activity carries a somewhat different practical risk profile than one with a robust, active challenger ecosystem.
Check a rollup's underlying security model — optimistic with fraud proofs, or validity proofs — the two approaches carry different assumptions about who needs to actively participate for security to hold.