Skip to main content
ZK proofs are experimental and under active development. Do not rely on them to secure a production chain yet.
A ZK dispute game accepts proofs only from the program its absolutePrestate identifies: the verification key of the super-aggregation program, which in turn pins the super-range and log-commitment programs. See Absolute prestate for why. This guide shows how to find the prestate for a release, confirm it by rebuilding the programs yourself, build a prestate for a chain that is not in the superchain-registry, and serve the program files that op-zk-proposer needs.

Find the standard prestate

The ZK proof programs are released under the kona-sp1-program/vX.Y.Z tags in the Optimism monorepo. Each standard release’s prestate is recorded in the superchain-registry’s standard-prestates.toml, as an entry of type kona-sp1 under the release’s version. A standard prestate covers every chain whose configuration is in the superchain-registry at that release. Use it if your chain is in the registry.

Rebuild the prestate from source

The programs build reproducibly in Docker, so you can confirm a prestate without trusting the published value. You need a Linux amd64 machine with Docker and mise.
  1. Check out the release tag:
  2. Build the programs:
    This builds log-commitment, then super-range with the log-commitment key embedded, then super-aggregation with the super-range key embedded. It writes the binaries to elf/ and their verification keys to elf/vkeys.toml.
  3. Read the keys:
The super-aggregation value is the prestate. Confirm that it matches the registry entry, and that git_sha is the tagged commit with no -dirty or -custom suffix. Every build embeds the commit it was built from, so you must build from the exact tagged commit. A build of the same code from any other commit produces a different prestate.

Build a prestate for a custom chain

The programs only accept chains whose configuration is compiled into them. If your chain is not in the superchain-registry, build the programs with your chain’s configuration:
The directory must contain chainList.json, configs.json, and depsets.json in the superchain-registry’s format. The L1 must be Ethereum mainnet, Sepolia, or Holesky. The resulting prestate is specific to your configuration and the commit you built from, and the manifest’s git_sha ends in -custom. Anyone who wants to verify your chain’s prestate needs your configuration files and the commit, so publish both.

Publish the program files

op-zk-proposer loads each prestate’s programs from OP_ZK_PROPOSER_PRESTATES_URL, by verification key. The directory at that URL must serve, for every prestate in use: <vkey> is the lowercase, 0x-prefixed super-aggregation key. For standard releases, these files are published for every tag under https://storage.googleapis.com/oplabs-network-data/proofs/kona/sp1/, which you can use as the URL directly. For a custom build, compress the files from elf/ and serve them yourself:
Keep every prestate’s files published for as long as games created under it can be live. The proposer cannot defend, resolve, or claim bonds for a game whose program files it cannot load.

Next steps