feat(L1): pin proof games to their L2 activation schedule - #384
Merged
Conversation
Derive each AggregateVerifier game's schedule commitment from its ending L2 block using the configured genesis timestamp and fixed block time. This removes dependence on proof-generation and game-creation L1 timestamps, while checked timestamp arithmetic and deployment assertions keep the onchain calculation aligned with the rollup configuration. Co-authored-by: Codex <codex-noreply@coinbase.com>
Collaborator
✅ Heimdall Review Status
|
jackchuma
approved these changes
Jul 28, 2026
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
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.
Summary
Pins
AggregateVerifiergames to theProtocolVersionsschedule active at the claimed L2 block timestamp insteadof the schedule at L1 game creation time.
This makes proof verification independent of when the game is created on L1 and prevents newer schedule
registrations from changing the commitment expected by already-created games.
Changes
Add L2 timestamp anchoring to
AggregateVerifierL2_GENESIS_BLOCK_NUMBERL2_GENESIS_TIMESTAMPL2_BLOCK_TIMEProtocolVersions.activatedScheduleId(claimTimestamp)Flatten
AggregateVerifier.ScheduleConfigprotocolVersionsWire deployment config through
SystemDeployl2BlockTime,l2GenesisBlockNumber, andl2GenesisTimestampl2BlockTimeandl2GenesisTimestamponly when multiproof is enabledUpdate multiproof dev deploy scripts to require explicit timestamp config.
Add explicit timestamp anchors in deploy configs where relevant.
Add tests for:
Validation