fix(taiko-client): dont check l1heightInAnchor vs l1Height when detecting reorg #18110
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
davidtaikocha
approved these changes
Sep 17, 2024
RogerLamTd
approved these changes
Sep 17, 2024
dantaik
pushed a commit
that referenced
this pull request
Sep 18, 2024
…ting reorg (#18110) Co-authored-by: David <[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.
Now that any block 64 blocks or older can be passed in to
proposeBlockvia theanchorBlockIdparameter, this check is no longer valid or necessary, and will break the taiko-client on a reorg loop if a manual anchor block is passed in that isntlatest, post-ontake fork.