-
Notifications
You must be signed in to change notification settings - Fork 745
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
fully validate a block before publishing #4168
Conversation
This reverts commit 23c804e.
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.
Just a quick fly-by review on my phone. I'm still not fully across the ObservedProposers
concept though.
The |
I think we could replace lighthouse/beacon_node/beacon_chain/src/block_verification.rs Lines 724 to 730 in a53830f
|
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.
I've had another look over this and I'm feeling good about it. Not necessarily for merging it into unstable
, but it looks good for a hot-fix for the relays. Nice work!
I think returning an error on the HTTP API if a conflicting/slashable block has been observed (like you have implemented) is good. This should prevent the relays from revealing their payloads if the proposer has started some sort of nefarious double-proposal work already.
Closing this now that #4293 is resolved. |
Issue Addressed
Which issue # does this PR address?
Proposed Changes
Please list or describe the changes introduced by this PR.
Additional Info
Please provide any additional information. For example, future considerations
or information useful for reviewers.