-
Notifications
You must be signed in to change notification settings - Fork 975
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opti sync: how to apply latestValidHash
when payload is INVALID
#2954
Conversation
LGTM. This matches how Teku is interpreting things now. |
It would be great to get approvals/confirmations from Lighthouse (@paulhauner @michaelsproul), Lodestar (@dapplion @tuyennhv), and Nimbus (@etan-status @arnetheduck @tersec) too. 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor copy nits
Last call for approval from @paulhauner and @tersec, merging in 24 hours |
Clarifies on how to handle
latestValidHash
on CL side. This PR doesn't introduce any breaking changes but instead makes current CL behaviour into the spec and leaves recommendation on what to do whenlatestValidHash
can't be found in a block treeUPD
It's written in a way that uses
latestValidHash
to only invalidate blocks. No valid semantics oflatestValidHash
is leveraged by this PRcc @potuz @ajsutton @paulhauner