Move DisputeGame creation to Creator Contracts #466
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
emhane
added
C-perf
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Introduces a Creator pattern for dispute games that decouples chain-specific configuration from game implementations, allowing multiple chains to share the same implementation contracts while maintaining their unique configurations. The change moves immutable variables into creator contract storage and adds a new abstraction layer between the factory and game implementations. This simplifies deployment workflows, reduces gas costs for new chain onboarding, and provides better upgrade paths for chain-specific configurations.
Tests
No additional tests needed
Additional context
Continues on work towards fixing #12421, and reflects the design doc 153