Ensure light client optimistic_header
to be at head
#2814
Merged
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.
When a light client updates its
finalized_header
using a forced updatebecause of the timeout, and the new header was not signed by enough sync
committee participants to pass
get_safety_threshold(store)
, it mayoccur that
store.finalized_header.slot > store.optimistic_header.slot
.This patch ensures that the
optimistic_header
is updated to the latestfinalized_header
if that happens, so that it always indicates thelatest known and accepted head.