You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
This change relaxes the ban logic in case of a backend that is syncing.
Our current default ban time is 5min, and sync may need only a few seconds.
On 2023-05-11 we observed a 1-block depth reorg which caused alchemy to get banned because it reported out of sync when fetching blocks.
{"backend":"alchemy","lvl":"warn","msg":"backend banned - not in sync","t":"2023-05-11T13:29:17.970613807Z"}
{"blockHash":"0x6e18493498040a4edc3d3fa755be422731124fc9d34f1f807ffcb229044413ae","blockNum":"0x890c41","lvl":"warn","msg":"backend broke consensus","name":"alchemy","proposedBlockHash":"0x159b0327000e4c7eec00aee78e548888a3b0187055a8cabd7b524c3d05053e94","proposedBlockNum":"0x890c41","t":"2023-05-11T13:23:29.424361286Z"}
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Merging #5694 (d7033e6) into develop (1382586) will increase coverage by 0.19%.
The diff coverage is n/a.
❗ Current head d7033e6 differs from pull request most recent head 25dd1ce. Consider uploading reports for the commit 25dd1ce to get more accurate results
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 change relaxes the ban logic in case of a backend that is syncing.
Our current default ban time is 5min, and sync may need only a few seconds.
On 2023-05-11 we observed a 1-block depth reorg which caused alchemy to get banned because it reported out of sync when fetching blocks.
Tests
Added ban checks.
Invariants
n/a
Additional context
This is part of the project Consensus Aware RPC Proxy: https://www.notion.so/oplabs/Consensus-Aware-RPC-Proxy-0138e029af814e4cbca2740c7888e02d
Metadata
TODOs