Remove API restrictions for optimistic sync - #2869
Merged
Merged
Conversation
mkalinin
reviewed
Apr 8, 2022
Contributor
|
This looks good to me other than awaiting @paulhauner response to @mkalinin's inquiry |
3 tasks
Contributor
Author
|
To be safe, we probably shouldn't merge this until ethereum/beacon-APIs#216 is merged (or resolved). |
mkalinin
approved these changes
May 18, 2022
18 tasks
22 tasks
25 tasks
29 tasks
This file contains hidden or 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
4 participants
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.
The API restrictions for optimistic sync have become outdated since we decided to use the
is_execution_optimisticbool rather than fully disabling endpoints that are tainted by optimism.