Skip to content
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

[MEV boost] improve blinded block validator options and flow handling #5341

Merged
merged 2 commits into from
Apr 14, 2022

Conversation

tbenr
Copy link
Contributor

@tbenr tbenr commented Apr 13, 2022

PR Description

I renamed --Xvalidators-blinded-blocks-api-enabled to --Xvalidators-proposer-blinded-blocks-enabled and moved in ValidatorProposerOptions

The flag now is used in BlockDutyFactory and BlockProductionDuty, no more in the OkHttpValidatorRestApiClient which now choose the right endpoint based on blinded flag at runtime.

Enabling --Xvalidators-proposer-mev-boost-enabled automatically enables --Xvalidators-proposer-blinded-blocks-enabled

Add a signer test for blinded block

Fixed Issue(s)

fixes #5260

Documentation

  • I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

  • I thought about adding a changelog entry, and added one if I deemed necessary.

Copy link
Contributor

@ajsutton ajsutton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Would just suggest automatically enabling blinded blocks rather than making the user specify two flags.

@@ -82,7 +85,7 @@ private SafeFuture<DutyResult> sendBlock(final SignedBeaconBlock signedBlock) {

public SafeFuture<Optional<BeaconBlock>> createUnsignedBlock(final BLSSignature randaoReveal) {
return validatorApiChannel.createUnsignedBlock(
slot, randaoReveal, validator.getGraffiti(), false);
slot, randaoReveal, validator.getGraffiti(), useBlindedBlock);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This definitely makes more sense - nice clean up.

@tbenr tbenr force-pushed the improve_vc_blinded_block_handling branch from 059c9de to bf01053 Compare April 14, 2022 06:30
@tbenr tbenr merged commit 9e8fe0d into Consensys:master Apr 14, 2022
@tbenr tbenr deleted the improve_vc_blinded_block_handling branch April 14, 2022 06:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[MEV Boost] Blinded block support - update on VC when performing block production duties
2 participants