Optimism just shipped ZK dispute game contracts in a release candidate. The multi-prover roadmap finally has real plumbing, for now.
The contract code for Optimism's ZK dispute game exists. That's not the same as a mainnet launch, but it's the first time this roadmap has had concrete plumbing instead of diagrams.
CryptoVibe Desk · optimism · op-stack · zk-proofs
- →Optimism published op-contracts v7.0.0-rc.4, a pre-release that adds a ZK dispute game contract, an SP1Adapter, and ZK root support in OPContractsManager.
- →This release shows the ZK contract plumbing finally exists, which is the first concrete step in Optimism's multi-prover security model.
- →The next milestone: v7.0.0 drops the rc label and a ZK dispute game goes live on an OP Stack chain before Q3 2026.
- ZK dispute game → A contract that uses zero-knowledge proofs to settle disagreements about whether a rollup block was correct, instead of replaying the transaction computation on-chain.
- SP1Adapter → A contract that translates proofs from the SP1 proving system into the format Optimism's dispute game contract expects to receive.
- multi-prover → A security model where multiple independent proof systems must all agree before a rollup state is accepted, so no single prover is a single point of failure.
- FCU (fork choice update) → A signal the execution layer of a blockchain node receives from the consensus layer, telling it which block is the current head of the chain.
Optimism just published op-contracts v7.0.0-rc.4. It's a pre-release, but it ships three things that matter: a ZK dispute game, an SP1Adapter, and ZK root support in OPContractsManager. None of this is on mainnet. All of it is concrete code that wasn't there before.
The ZK dispute game is a parallel dispute resolution path. The existing system uses fraud proofs: an on-chain contract re-executes a disputed computation step to check it. The ZK game skips re-execution and verifies a cryptographic proof instead. If the proof checks out, the claim stands.
That's the tradeoff Optimism made. ZK proofs are faster to verify on-chain than replaying execution, but they require a working prover. If the prover is slow, unavailable, or wrong, the game stalls. Fraud proofs have the opposite failure mode: always available, but they depend on honest challengers watching and reacting.
The SP1Adapter sits between the dispute contract and the SP1 proving system. At the contract level, it translates a proof from SP1 into the format the dispute game expects. Think of it as a protocol adapter. The game doesn't care which prover generated the proof, only whether the adapter hands it over in the right shape.
OPContractsManager now includes ZK roots. That's the deployment and upgrade manager for the whole OP Stack contract system. Adding ZK roots means the manager can deploy and track ZK dispute game contracts the same way it handles fraud-proof ones. For any OP Stack chain, this puts ZK games in the first-class deploy path, not a bolt-on.
The monitoring side shipped separately. op-dispute-mon v1.5.2 adds support for ZKDisputeGameType, which Optimism labels game type 10. The release marks it optional for all users. If you're running dispute monitoring and want visibility into the ZK game, you need this version.
The two game types coexist on any chain that deploys both. Watching only one is a partial security picture. That's the catch for operators who configured their monitoring for fraud proofs and haven't updated yet.
op-reth v2.2.5 is the routine item in this week's batch. It bumps the reth dependency and picks up an FCU backfill-target fix. An FCU backfill bug can cause a node to misidentify the chain head after a restart. Not a security issue, but worth patching if you're running op-reth in production.
The pre-release label on v7.0.0-rc.4 is the key qualifier. Release candidates exist to catch problems before they become mainnet problems. Optimism has been public about the multi-prover roadmap for over a year. The contract code now exists, and the monitoring system has a type identifier for it.
ZK dispute games are coming to your deploy path. This release candidate makes that concrete for every OP Stack chain. The monitoring update is optional today. It won't be optional when ZK games go live on your chain. Read the rc.4 diff, not the roadmap post.
Optimism shipped a new dispute game type and labeled the monitoring upgrade 'optional.' For now, that's pre-release math. When v7.0.0 ships, operators who skip the update will be running half-blind on live security infrastructure. Calling that optional is technically correct and operationally wrong.
If op-contracts v7.0.0 still carries a pre-release label by the end of Q3 2026, the multi-prover timeline has slipped and the gap between roadmap and contract code is back to where it started.
Primary links and supporting reads used by the desk for this story.
Forward this.
