beacon/types, beacon/light: use OptimisticUpdate instead of SignedHeader #29483
Conversation
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
zsfelfoldi
force-pushed
the
blsync-optimistic
branch
from
51e0204 to
01abe80
Compare
zsfelfoldi
force-pushed
the
blsync-optimistic
branch
from
01abe80 to
27618fc
Compare
Contributor
Author
|
Closed because #29567 includes this commit. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR introduces
types.OptimisticUpdatewhich represents the full information content of the optimistic updates, including theExecutionPayloadHeaderbelonging to the attested beacon header, proven by a Merkle proof. This change does not change the behavior of blsync but it is useful for the lightethclient(implemented by #29033 ) because it makes execution header info automatically available for the current head and recent blocks.