A validity proof is a cryptographic proof — in practice, a zk-SNARK or zk-STARK — that accompanies a rollup batch and mathematically demonstrates the claimed state transition is correct, according to the rollup’s own rules. A smart contract on L1 can check this proof directly and cheaply, without re-running every transaction in the batch and without waiting to see if anyone objects.
This is the mechanism behind ZK rollups, and it’s the structural counterpart to a fraud proof: instead of assuming correctness and giving a window to disprove it after the fact, a validity proof establishes correctness up front, before the batch is accepted.
Why it matters
Because the proof is checked, not trusted, withdrawals that depend on a validity-proven batch don’t need the multi-day challenge window an optimistic design requires. The practical cost sits earlier in the pipeline: generating these proofs for complex, general-purpose smart contract execution is computationally demanding, and the engineering required to make that fast and affordable has been one of the main fronts of rollup R&D.
Example
A rollup processes a batch of transfers and swaps, generates a succinct proof that every resulting balance change was computed correctly, and posts that proof with the batch; Ethereum’s verifier contract accepts the batch the moment the proof checks out.
Related · Rollups
Not financial advice.