feat: ZKDisputeGame Multi-chain Super Game Migration Paths

[ashitakah]

Summary

Adds the interop migration path (Path C): OPContractsManagerV2.setInteropDisputeGames(...), which re-points the shared dispute games of an already-interop set to a new respected super game in a single transaction covering all chains. Current use case is the post-migration transition from shared fault proofs to a shared super ZKDisputeGame. Reuses the migrator machinery; the standard upgrade() path can't be used since it re-inits per chain and would clobber the shared AnchorStateRegistry / ETHLockbox. Paths A and B (isolated chains) need no contract changes and go through upgrade(), since ZK is already in isSuperGame.

Changes

Contracts — src/L1/opcm/OPContractsManagerMigrator.sol

Area	Change
setInteropDisputeGames	New function. Validates the chain set, re-initializes the shared AnchorStateRegistry with the new respected game type + anchor root, then sets the dispute game impls on the shared DisputeGameFactory via the existing _getGameImpl / _makeGameArgs. Enabled configs register, disabled configs clear. No new infra deployed, per-chain portals untouched.
Guards	Gates on OPTIMISM_PORTAL_INTEROP + ZK_DISPUTE_GAME dev features (TODO to drop the ZK gate once finalized; the function is generic across super games). Requires startingRespectedGameType ∈ isSuperGame. Runtime check that all portals resolve to the same shared ASR.
Errors	OPContractsManagerMigrator_ZKDisputeGameNotEnabled, OPContractsManagerMigrator_NotSharedInteropSet.

Contracts — src/L1/opcm/OPContractsManagerV2.sol

Area	Change
setInteropDisputeGames	Thin entry point, _onlyDelegateCall + delegatecall to the migrator (mirrors migrate()). Transitional, removed once interop is native in OPCM.
Version	7.1.22 → 7.1.23.

Interfaces

File	Change
interfaces/L1/opcm/IOPContractsManagerMigrator.sol	Added setInteropDisputeGames + the two errors.
interfaces/L1/opcm/IOPContractsManagerV2.sol	Added setInteropDisputeGames.

Forge script — scripts/deploy/SetInteropDisputeGames.s.sol

Area	Change
Script	New Input / Output / run mirroring InteropMigration.s.sol. Etches DummyCaller to simulate the governance delegatecall. checkOutput asserts on chain: all portals share the DGF, respected game type updated, and each input config applied (enabled registered, disabled cleared).

Op-deployer (Go)

File	Change
op-deployer/pkg/deployer/manage/set_interop_dispute_games.go	SetInteropDisputeGames runner, encodeZKGameArgs (5-field ZK config), SetInteropDisputeGamesCLI. Validates all address flags with IsHexAddress. Default clears only SUPER_CANNON_KONA (9, the permissionless slot ZK replaces) and keeps SUPER_PERMISSIONED_CANNON (5) as the permissioned liveness backup.
op-deployer/pkg/deployer/manage/flags.go	New flags (--system-config-proxy-addresses, --source-game-types, --zk-verifier-address, --zk-max-challenge-duration, --zk-max-prove-duration) + set-interop-dispute-games command.

Tests

File	Change
test/L1/opcm/OPContractsManagerV2.t.sol	test_setInteropDisputeGames_succeeds (migrate to interop with SPDG + kona, swap to ZK, asserts SPDG kept, ZK registered + respected, kona cleared), _notDelegateCalled_reverts, _notSharedInteropSet_reverts.
op-deployer/pkg/deployer/manage/set_interop_dispute_games_test.go	TestEncodeZKGameArgs (encoder round-trip + validation), TestSetInteropDisputeGames (forked-Sepolia e2e: deploy with ZK impl, migrate to interop, swap, asserts the end shape on chain).

Snapshots

File	Change
snapshots/semver-lock.json, snapshots/abi/*	Regenerated for the OPCMv2 version bump and the new setInteropDisputeGames ABI.

Notes

• Target post-swap shape is SUPER_PERMISSIONED_CANNON (permissioned backup) + ZK_DISPUTE_GAME (permissionless, respected), mirroring today's permissioned + permissionless super shape.
• The script CLEARS retired games from the factory which can cause assertValidSuperRootDisputeGames in the StandardValidator to fail even though the migration will not be blocked since no on-chain validator covers the post-swap state. Executors should provide the correct configs or post-interop after all flag removals, reorder/modify those checks. Issue tacked here [SuperZKDG] Remove ZK_DISPUTE_GAME dev feature flag and address TODOs once ZK becomes the default game post-interop #21529
• Paths A and B (single-chain SPDG/SFDG → ZK) and full game-lifecycle / finalization tests are handled in a separate test PR here test: ZK Game Integration Test Coverage and E2E SuperGame Migration Tests #21128
• op-challenger ZK actor needs interop super-root handling + the invalid-parent challenge fix (op-challenger: should challenge ZK child games built on locally-invalid parent games #21445) before the games can be defended in production.

Closes #20759

[ashitakah]

/ci authorize 5b8667f

[Inphi]

@ashitakah Could you explain more about the issue of using upgrade for this migration? How are the ASR and EthlockBox clobbered if we go with that route?

[0xarktos]

@ashitakah Could you explain more about the issue of using upgrade for this migration? How are the ASR and EthlockBox clobbered if we go with that route?

Hey @Inphi, as we outlined in the document we shared here the regular upgrade flow touches state and re-initializes contracts for every chain regardless if it runs on shared infra (DelayedWETH, ASR) or not. This means that the only changes that would persist would be the configs of the last chain in the upgrade call. This generally increases operational complexity and increases margin or error since we don't want to be touching those shared parts just for a game flip so a separate flow felt safer/more isolated.

Additionally, initially IIRC we thought that the reinitializer guard in the shared ASR would block multiple inits and cause the upgrade to revert but looking at the proxy upgrade again this doesnt look like this is the case since StorageSetter clears the init version with each upgrade.

Lmk what you think and if you're open to converting it to a regular upgrade e2e test flow instead of adding this separate path. I'll be taking over this task now.

[0xarktos]

/ci authorize 57cb220