fix(op-challenger): advance anchors for super permissioned games#21811
Open
ajsutton wants to merge 21 commits into
Open
fix(op-challenger): advance anchors for super permissioned games#21811ajsutton wants to merge 21 commits into
ajsutton wants to merge 21 commits into
Conversation
ajsutton
force-pushed
the
aj/chore/type5-anchor-design
branch
from
July 16, 2026 02:43
8d580a8 to
9d76479
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds lifecycle-only handling for
SuperPermissionedDisputeGamegames so finalized games can advance theirAnchorStateRegistrywithout making game type 5 playable.Separates lifecycle support from trace playability, registers lifecycle bindings independently of configured players, routes supported games through post-game handling, and simulates
setAnchorState(game)against the game-selected registry before submission. Extends the shared single-chain withdrawal scenario to wait for the covering game and verify its anchor after finalization, then reuses it for type 5 with the default dispute-game finality delay and for type 9 with a valid starting super root.Closes #21708
Closes #21712
Tested with the focused SuperPermissioned, SuperCannonKona, and permissioned withdrawal scenarios, the relevant challenger/devstack Go package suites, and
just lint-go.