Update release branch to version tested on the sequencer during the final dry run #370
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
* saving progress * Fixes --------- Co-authored-by: Paul Lange <[email protected]> Co-authored-by: Paul Lange <[email protected]>
Prior to this change all migrations would use the L2 starting block time as the rollup l2_time but, alfajores and baklava were migratied using the l1 starting block time as the l2_time. So we need to select the time to use appropriately in order to be able to correctly reproduce the testnet migrations.
…#367) * Set L1 safe and finalized head at startup of op-node * Wrap initialization of L1 safe & finalized head in SyncStatus with if block * Fix comment * Fix commen * Fix comment * Fix codes based on feedback * Fix comment * Swap the order of fetching finalized and safe L1 block references * Move L1 safe and finalized head fetching to the beginning of OpNode::Start * Remove unnecessary empty line * Add log in finalized
…hereum-optimism#14062) (#368) This is a cherry picked PR from the upstream optimism repo, original commit message below ------------------------------------- * continue sequencing when L1TemporaryErrorEvent happens * add TestSequencerL1TemporaryErrorEvent * address comment * fix test Co-authored-by: zhiqiangxu <[email protected]>
palango
approved these changes
Mar 24, 2025
Author
|
I planned to do a merge-as-rebase here (which hopefully will just do a fast forward and keep the commit hashes), but only squashing is allowed. It doesn't really matter much either way. Should I just squash? |
ezdac
pushed a commit
that referenced
this pull request
Jun 16, 2025
* feat: add mul access lists test (#370) * feat: add mul access lists test * chore: polish * chore: pre pr * feat: add more tests * feat: wip to add more tests * fix: multiple msgs tests * fix: semgrep (#371) --------- Co-authored-by: Disco <[email protected]>
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.
We used ad644bc on the sequencer during the final dry run. We plan to run this in production, so we should make a proper release for it and to do that, we should move it to the release branch first. The changes are only required for the sequencer, other users can ignore the change.
We could limit this PR to bc42ea8 and ad644bc, but I prefer to use the exact same version as we tested in the dry run.