Update to an op-geth with superchain config without gingerbread block#428
Merged
piersy merged 1 commit intocelo-rebase-16from Mar 4, 2026
Merged
Conversation
…lock Instead of relying on the suprechain config to provide the gingerbread block, it is now hardcoded in op-geth in params/superchain.go which means the handling of the gingerbread hardfork is consistent with all other pre bedrock eth forks.
palango
approved these changes
Mar 3, 2026
piersy
deleted the
piersy/move-gingerbread-block-out-of-superchain-config
branch
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
2 participants
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.
Instead of relying on the suprechain config to provide the gingerbread block, it is now hardcoded in op-geth in params/superchain.go which means the handling of the gingerbread hardfork is consistent with all other pre bedrock eth forks.