Fraud proofs and challenge periods

A dispute process needs evidence, access and time to work.

LET’S PICTURE IT

A published result can be contested only if someone can inspect the working and submit a challenge before the deadline.

SEE IT FOR YOURSELF

Link blocks, then see what an edit breaksStep 1 / 4

The first toy block records Maya sending Leo three units. A1 is an illustrative fingerprint label, not a real cryptographic digest.

Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.

A claim can be disputed

An optimistic design can define how participants identify and challenge an invalid execution claim. Different systems use different dispute protocols and proof formats.

Data is needed to find a problem

A challenger needs enough information to reconstruct or analyze the claimed transition. Hiding crucial inputs can undermine the intended accountability even if a challenge function exists.

The window is part of settlement

A withdrawal or state claim may remain provisional during a challenge period. Exact delays and exceptional paths come from the particular network’s implementation and rules.

Permission and liveness matter

Ask who can submit a valid challenge, whether required contracts are operational and who can change the system. A diagram of a dispute is an explanation, not an audit of a particular deployed rollup.

QUICK CHECK · NO PRESSURE

Is an available challenge function useful if nobody can obtain the required execution data?

Your progress stays in this browser.

Keep exploring the original referenceethereum.org ↗

Original explanations by EtherTools. Examples are educational and source-linked; this site is independent of the Ethereum Foundation. Our approach.