-
-
Notifications
You must be signed in to change notification settings - Fork 369
feat: add basic broadcast validation to the block publishing #5762
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
Conversation
Performance Report✔️ no performance regression detected Full benchmark results
|
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.
This PR changes current behaviour that ignores broadcastValidation, to rejecting calls with values != consensus. I'm not sure if it's an strictly improvement, but I can see the reasoning why. Do you think there value in merging a throw before the full actual implementation?
added a flag to enforce strictness (mostly for dev purposes) I agree will push follow up PRs on this tracking here: currently default broadCastValdaton requested by valdator s |
42867d5
to
880522a
Compare
@@ -44,6 +44,13 @@ export type BlockHeaderResponse = { | |||
header: phase0.SignedBeaconBlockHeader; | |||
}; | |||
|
|||
export enum BroadcastValidation { | |||
none = "none", |
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.
according to the beacon APIs this shouldn't exist
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.
none
is what our current case is, just added it for convenience and incase one doesn't want to actually do any validations before publishing... may be we can remove it later
} | ||
break; | ||
} | ||
case routes.beacon.BroadcastValidation.consensus: { |
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 think this PR should implement the different broadcast validations
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.
would prefer to do followups unless you feel strongly about this
🎉 This PR is included in v1.11.0 🎉 |
implement
broadcast_validation
to block publishing ethereum/beacon-APIs#317Part of - BroadcastValidations tracer #5761
TODO:
none
param as default (expose via a cli option), primarily to support block publishing via fallback beacon nodesconsensus
vals