Meaning
A cryptographic assertion submitted to a parent blockchain proves that a specific state transition proposed by a layer-two network is invalid. Utilizing a fraud proof allows the base network to secure off-chain transactions without executing every single one of them by default. This mechanism forms the foundation of optimistic rollup designs, where updates are assumed correct unless a validator shows otherwise.
Execution Method
Generating the assertion requires executing the disputed transaction step by step on the base chain virtual machine. The challenger provides a pre-state, the specific transaction, and a post-state, along with a Merkle proof showing the data is correct. If the base contract finds a mismatch during execution, it slashes the original sequencer and reverts the state.
Network Protection
Security in these decentralized rollups depends on at least one honest validator remaining active to monitor the state. This party compiles a fraud proof whenever they detect a dishonest transition, ensuring that a single honest node can protect the entire ecosystem from corruption. The system remains secure as long as the dispute window does not close before the challenge is submitted.
Furthermore, the protocol compensates the challenger using the slashed security deposit of the faulty sequencer, which covers their execution costs and incentivizes continuous observation.
Protocol Balance
While this approach lowers transaction costs and raises speed on layer two, it forces users to wait during the withdrawal period. The necessity of a potential fraud proof creates an inherent delay that affects immediate capital mobility. However, alternative liquidity providers often offer fast withdrawals for a small fee, bridging the temporal gap.