fix: reorg detector and syncer issues on develop
#272
Merged
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
goran-ethernal
force-pushed
the
fix/reorg-detector-syncer-issues-cherry-pick
branch
5 times, most recently
from
434d530 to
80c6240
Compare
goran-ethernal
force-pushed
the
fix/reorg-detector-syncer-issues-cherry-pick
branch
from
80c6240 to
3de7f02
Compare
goran-ethernal
requested review from
arnaubennassar,
joanestebanr and
ToniRamirezM
goran-ethernal
changed the title
reorg detector and syncer issues cherry-pick to developreorg detector and syncer issues on develop
joanestebanr
requested changes
Jan 22, 2025
|
joanestebanr
approved these changes
Jan 23, 2025
ToniRamirezM
approved these changes
Jan 23, 2025
goran-ethernal
deleted the
fix/reorg-detector-syncer-issues-cherry-pick
branch
This was referenced Jan 29, 2025
Vui-Chee
added a commit
to okx/xlayer-cdk
that referenced
this pull request
Mar 11, 2025
* tag 'v0.6.0-rc3': (43 commits) chore: Update Go and go-ethereum version (0xPolygon#307) fix: golangci-lint and bump the versions of the golangci-lint (0xPolygon#301) feat: `aggkit` repo migration (0xPolygon#253) Disable the requirement of the config file (0xPolygon#299) feat: recover aggregator on l1 sync failure (0xPolygon#296) fix: witness loop (0xPolygon#293) (0xPolygon#294) fix: hash meddler error (0xPolygon#285) fix: chainID in aggOracle configs (0xPolygon#265) build(deps): bump google.golang.org/grpc from 1.64.0 to 1.64.1 (0xPolygon#68) chore(deps): bump golang.org/x/net from 0.29.0 to 0.33.0 (0xPolygon#280) feat: more logs for `l1infotreesyncer` `cherry-pick` (0xPolygon#283) feat: add Dependabot configuration for gomod updates (0xPolygon#279) chore(deps): bump github.com/golang-jwt/jwt/v4 from 4.5.0 to 4.5.1 (0xPolygon#164) chore(deps): bump golang.org/x/crypto from 0.27.0 to 0.31.0 (0xPolygon#242) fix: `reorg detector` and `syncer` issues on `develop` (0xPolygon#272) fix: case of eth_getBlockByHash response null or tstamp zero (0xPolygon#275) (0xPolygon#277) fix: seq-sender latestVirtualTime (0xPolygon#270) feat: do not print content on config error log (0xPolygon#268) fix: `reorg detector` removes `finalized` block (0xPolygon#266) fix: multi chains pessimistic proofs e2e tests (0xPolygon#267) ...
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.
Description
This PR fixes the issues found on the
l1infotreesyncerandreorg detector, when we might not be tracking a correct block hash in thereorg detector.It also fixes an issue when download channel is closing, it passes an empty block object (since it is passing objects by value and not by reference), with number 0, and empty hash, which processor passes to the
reorg detectorwhich is not correct.Important Note:
e2etests usesumulated clientas thel1 clientnode, which only knows ofSafeBlocks. That is why this PR expanded the constructor function of theEVMDownloaderto receivefinalizedBlockTypeparameter. When we run thecdknode or any syncer that syncs data fromL1, thefinalizedBlockTypeisFinalizedBlockas seen in therun.go.e2etests useSafeBlock.Also,
L2does not have a notion ofFinalizedBlock, sobridgeL2Syncerwill use theLatestBlockfor this parameter.Fixes # (issue)