Skip to content

Conversation

@shane-moore
Copy link

Issue Addressed

Closes #746

Proposed Changes

  • Remove the --builder-proposals CLI flag
  • Always create validator registrations
  • Change the log level for builder registration failures from warn to debug

Additional Info

Why this change:

In DVT, validator registrations require threshold signatures from multiple operators. If some operators had --builder-proposals disabled, they wouldn't participate in signing registrations, potentially causing the registration to fail for the entire committee

User impact:

Users who previously used --builder-proposals will see a CLI error when trying to use the flag

@cla-assistant
Copy link

cla-assistant bot commented Nov 26, 2025

CLA assistant check
All committers have signed the CLA.

@cla-assistant
Copy link

cla-assistant bot commented Nov 26, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Member

@dknopik dknopik left a comment

Choose a reason for hiding this comment

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

Hey Shane, thanks for the PR! Looks good, some notes below.

Comment on lines -444 to -453
#[clap(
long,
alias = "private-tx-proposals",
help = "If this flag is set, Anchor will query the Beacon Node for only block \
headers during proposals and will sign over headers. Useful for outsourcing \
execution payload construction during proposals.",
display_order = 0,
help_heading = FLAG_HEADER
)]
pub builder_proposals: bool,
Copy link
Member

Choose a reason for hiding this comment

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

To ensure that we do not break the CLI, we should (as a first step) only hide this option, and emit a warning on startup if it is supplied, notifying the user that it is deprecated.

Comment on lines +200 to +203
Err(err) => debug!(
%err,
"Unable to publish validator registrations to the builder network"
"Unable to publish validator registrations to the builder network. \
This is expected if no relay is configured in your Beacon Node."
Copy link
Member

Choose a reason for hiding this comment

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

Ideally, we only debug log this if the error is in fact caused by this (and keep the error log if it is not). I think it should be possible to check this. For reference, here is the log emitted currently:

2025-12-03T13:39:11.456556Z  WARN Unable to publish validator registrations to the builder network err=Some endpoints failed, num_failed: 1 http://localhost:5052/ => RequestFailed(ServerMessage(ErrorMessage { code: 500, message: "UNHANDLED_ERROR: BuilderMissing", stacktraces: [] }))

@dknopik dknopik removed the v1.2.0 label Dec 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deprecate --builder-proposals and always create validator registrations.

2 participants