Skip to main content
ZK proofs are experimental and under active development. Do not rely on them to secure a production chain yet.
This page catalogues the contracts, functions, parameters, and statuses of the OP Stack ZK proof system. For the normative definitions, see the ZK dispute game specification.

Game type

Off-chain tools use the name zk for this game type, for example op-challenger --game-types zk.

Contracts

The SP1 PLONK verifier that SP1PlonkAdapter wraps is deployed by Succinct; see the sp1-contracts deployments. op-deployer selects the release-approved verifier for Ethereum mainnet and Sepolia (source), and needs --sp1-verifier-address on any other L1. See Bootstrap implementations.

ZKDisputeGame functions

Actions, callable by anyone: Reads:

Parameters

Each chain sets these when it registers the game through OPContractsManager: The game also uses the chain’s shared dispute delays: the OptimismPortal proof maturity delay, the AnchorStateRegistry finality delay, and the DelayedWETH withdrawal delay. See the standard values for these delays.

Statuses

GameStatus, the outcome read by the AnchorStateRegistry and OptimismPortal: ProposalStatus, the game’s internal progress, in claimData().status:

Release artifacts

Release the proposer and the programs together where possible: the proposer collects the data the programs read, and must be compatible with the program version it proves for. See Verifying a ZK absolute prestate for where the program binaries are published.

Next steps