op-node: change verifiedValidatorNum param of getFinalizedHeader API to -3 #254
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
redhdx
previously approved these changes
Jan 6, 2025
bnoieh
changed the title
|
we have released hotfix image for this, and will use another solution after BSC refactor the API. |
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
change verifiedValidatorNum to -3 to automatically adapt BSC network validators
Rationale
validators of BSC network may change, and BSC
getFinalizedHeaderAPI support a new feature to automatically adapt this change, you can refer to bnb-chain/bsc#2844we make this update to follow the new feature
Example
n/a
Changes
change verifiedValidatorNum to -3 to automatically adapt BSC network validators