Fraud Proof

What is a Fraud Proof?

A fraud proof is a cryptographic mechanism that allows anyone to challenge and prove that a state transition on an optimistic rollup was invalid. When a sequencer posts an incorrect state root to the main chain, verifiers can submit a fraud proof demonstrating the error, causing the invalid batch to be reverted and the malicious actor to be penalized.

Fraud proofs are the security backbone of optimistic rollups. While the system "optimistically" assumes all transactions are valid, fraud proofs ensure that any attempt to cheat can be detected and punished, making dishonest behavior economically irrational.

How it Works

The fraud proof mechanism operates through an interactive dispute resolution process:

1. State Assertion: Sequencer posts a state root claiming the result of executing a batch
2. Challenge Initiation: A verifier who disagrees stakes funds and challenges the assertion
3. Bisection Game: Challenger and defender iteratively narrow down the disputed step
4. Single-Step Verification: The dispute is reduced to one instruction verified on-chain
5. Resolution: The chain determines who was correct; the loser forfeits their stake

This bisection approach is efficient because only the disputed computation step executes on-chain, regardless of how many transactions were in the original batch. A batch of 10,000 transactions can be disputed by verifying just one instruction.

Modern fraud proof systems include:

• Interactive Proofs: Multi-round bisection games (Arbitrum Classic)
• Single-Round Proofs: One-shot proofs with more on-chain data (Optimism Cannon)

Practical Example

Suppose a malicious sequencer on Arbitrum submits a batch claiming Alice has 1,000 ETH when she actually has 100 ETH. Any node running the rollup software will detect this discrepancy. The node operator initiates a challenge, staking ETH as a bond. Through the bisection protocol, the dispute is narrowed to the exact instruction where the sequencer lied. On-chain verification proves the sequencer wrong, the fraudulent batch is reverted, and the sequencer loses their stake to the challenger.

Why it Matters

Fraud proofs enable optimistic rollups to achieve strong security guarantees with minimal on-chain computation:

• Economic Security: Attackers must stake significant funds that they lose if caught
• Permissionless Verification: Anyone can challenge, creating a robust security network
• Efficient Scaling: Valid batches require no on-chain proof generation
• EVM Compatibility: Easier to build than validity proof systems for complex VMs

The tradeoff is the challenge period (typically 7 days) required for finality, during which fraud proofs can be submitted. This affects withdrawal times but can be mitigated through liquidity bridges.