#4451 - L1 head used for compression can be stale #2257
Closed
Conversation
This file contains 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.
Why this change is needed
L1 head used for compression can be stale; If the block is not in the canonical chain on the l1, the rollup should not be accepted by the management contract as nodes will not be able to decompress it. However if a block is too old, then its never going to be available in the EVM; This ensures we always use latest block in order to make rollups reconstructible.
What changes were made as part of this PR
Changed from using a block at a height to always using head cannon block
PR checks pre-merging
Please indicate below by ticking the checkbox that you have read and performed the required
PR checks