Skip to main content
ZK proofs are experimental and under active development. Do not rely on them to secure a production chain yet.
op-zk-proposer is the OP Stack’s ZK proposer: the service that proposes the chain’s super root to L1 and proves its proposals with ZK proofs when they are challenged.

Overview

op-zk-proposer plays every role of the proposer side of the ZK dispute game:
  1. Create. On a fixed interval, it reads the canonical super root from its super root source and creates a game for it in the DisputeGameFactory, building on the previous game.
  2. Defend. When a game is challenged, it collects the data the proof reads, buys the proofs from the Succinct Prover Network or generates them on local GPUs, and submits the aggregation proof to the game. In fast finality mode, it also proves its own games before anyone challenges them.
  3. Resolve and claim. It resolves finished games and claims bonds, including the challenger bond it earns when it proves another proposer’s challenged game.
It defends every game whose prestate it has program files for, whoever created it. Before it creates a game on a prestate, it checks that it can generate proofs for that prestate and that the game’s verifier accepts proofs from its SP1 SDK, so it never posts a bond on a game it cannot defend. op-zk-proposer is written in Rust and lives with the ZK proof programs in the Kona workspace. It embeds kona-host to collect the data that the programs read. Who runs it: the chain operator, as one of the chain’s core services. Proposing and proving are permissionless, so anyone can run it, but the operator runs it so that proposals land regularly and challenged proposals are defended.

Get started

How-tos

Configuration reference