ethereum-optimism / ethereum-optimism/optimism
Integrate ZK_DISPUTE_GAME dev feature flag into OPCM/OPD pipeline
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 134
Description
Summary
The ZK_DISPUTE_GAME dev feature flag has been registered across the stack (PR #19388), but is not yet used in the op-deployer pipeline.
Work needed
- Use
ZKDisputeGameDevFlaginop-deployer/pkg/deployer/pipeline/to conditionally deploy ZK dispute game contracts - Add OPCM integration for the ZK game type (implementation tracking,
_makeGameArgs()encoding,validGameTypesinclusion) - Wire up any necessary CLI flags or intent configuration for the ZK game type
Context
This follows the same pattern as OPCM_V2 (OPCMV2DevFlag in pipeline/opchain.go) and L2CM (L2CMDevFlag in pipeline/l2genesis.go).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in op-deployer/pkg/deployer/pipeline/ and compare the ZK_DISPUTE_GAME work with OPCM_V2DevFlag in pipeline/opchain.go and L2CMDevFlag in pipeline/l2genesis.go. Trace OPCM integration for implementation tracking, _makeGameArgs() encoding, validGameTypes, and the CLI or intent configuration. Done means the ZK game type is conditionally deployed through the OPCM/OPD pipeline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100