Fraud Proof
Pronunciation: FRAWD PROOF
Definition
A fraud proof is evidence showing that a claimed state transition or computation violated protocol rules and should be rejected or corrected. Controls for Fraud Proof combine identity and device evidence, velocity and value rules, behavioral models, step-up review, merchant procedures, and post-payment monitoring.
Overview
Meaning and scope
A fraud proof is evidence showing that a claimed state transition or computation violated protocol rules and should be rejected or corrected. Controls for Fraud Proof combine identity and device evidence, velocity and value rules, behavioral models, step-up review, merchant procedures, and post-payment monitoring.
Mechanism and operation
A fraud proof allows a participant to demonstrate that an asserted result was computed incorrectly. Optimistic systems may accept results provisionally, then permit challengers to submit evidence during a defined period before settlement becomes final. Proof design varies by protocol and may verify an entire step directly or narrow a dispute through interactive rounds. Operators should understand who can challenge, what data must remain available, how bonds and deadlines work, and what happens after a successful proof. A fraud alert for Fraud Proof is a reason to investigate, not proof of intent, so decisions require explainable evidence, documented thresholds, and a fair exception path.
Practical payment example
A rollup participant submits a challenge to an invalid state claim within the permitted window; operators track that challenge process separately from ordinary payment confirmation.
Operational checks
Fraud proofs make incorrect claims contestable, but safety still depends on data availability, active challengers, verification logic, and challenge access. Operational review of Fraud Proof should reconstruct evidence showing that a claimed state transition or computation violated protocol rules and should be rejected or corrected using the identities, communications, devices, and transaction records available for the affected case.
Distinctions and limits
Security depends on available transaction data, honest monitoring, correct verification logic, accessible challenge submission, and sufficient economic incentives. Fraud proofs cannot protect users when all challengers are offline, censored, or unable to reconstruct the disputed execution.
Related reading
Related definitions: fraud, transaction data.
Example
A rollup participant submits a challenge to an invalid state claim within the permitted window; operators track that challenge process separately from ordinary payment confirmation.
Comparison
Security depends on available transaction data, honest monitoring, correct verification logic, accessible challenge submission, and sufficient economic incentives. Fraud proofs cannot protect users when all challengers are offline, censored, or unable to reconstruct the disputed execution.
Key Takeaway
Fraud proofs make incorrect claims contestable, but safety still depends on data availability, active challengers, verification logic, and challenge access.
Sources
- NIST Documentation: Cyberframework — NIST (2026-07-30)
- FATF Documentation: Virtual Assets — FATF (2026-07-30)