Skip to main content
ZK proofs are experimental and under active development. Do not rely on them to secure a production chain yet.
ZK proofs are how OP Stack chains secure withdrawals without a trusted third party. Anyone can propose the state of the chain on Ethereum, and anyone can challenge a proposal they believe is wrong. A challenged proposal stands only if someone proves it with a zero-knowledge proof before its deadline, and the proof is verified on Ethereum in a single call. This page is the recommended reading order for the topic. Start with the explainer for the mental model, then read the pages on the game and the proof system to see how the pieces fit. Use the operator guides if you run a chain, and the spec for full depth.

Start here

  • ZK proofs explainer: proposals, challenges, proofs, fast finality, and the path from a resolved game to a withdrawal.

Go deeper

  • ZK dispute game: the game’s lifecycle, parent games, bonds, and per-chain configuration.
  • ZK proof system: what a proof attests to, the SP1 programs that produce it, the absolute prestate, and the verifier.
  • ZK proof system components: the L1 contracts and off-chain services, and who runs each.
  • ZK proofs security: soundness, completeness, the Guardian’s safeguards, and the trust assumptions.
  • ZK proofs reference: the game type, functions, parameters, and statuses.

Get hands-on

The normative spec

Audits and security