Skip to content

Conversation

@michaelsproul
Copy link
Member

Proposed Changes

  • Consensus changes for execution payload bids
  • EF tests for bids (and block_header -- no changes required).

@michaelsproul michaelsproul added ready-for-review The code is ready for review consensus An issue/PR that touches consensus code, such as state_processing or block verification. gloas labels Feb 11, 2026
Copy link
Member

@pawanjay176 pawanjay176 left a comment

Choose a reason for hiding this comment

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

LGTM, just nits

Copy link
Member

@eserilev eserilev left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Collaborator

@dapplion dapplion left a comment

Choose a reason for hiding this comment

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

Spec comparison review — compared against consensus-specs/specs/gloas/beacon-chain.md and potuz's annotated GLOAS spec.

@michaelsproul
Copy link
Member Author

All comments reviewed, thanks gang

@dapplion dapplion self-requested a review February 11, 2026 23:18
Comment on lines +28 to +35
impl Builder {
/// Check if a builder is active in a state with `finalized_epoch`.
///
/// This implements `is_active_builder` from the spec.
pub fn is_active_at_finalized_epoch(&self, finalized_epoch: Epoch, spec: &ChainSpec) -> bool {
self.deposit_epoch < finalized_epoch && self.withdrawable_epoch == spec.far_future_epoch
}
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Nit: the spec calls this is_active_builder. Would it be worth renaming to is_active_builder for easier cross-referencing? The method-on-Builder approach is fine to avoid a redundant list lookup.

Copy link
Member Author

Choose a reason for hiding this comment

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

I thought about this, but I figure including builder in the name is redundant when it's a method on builder, and putting finalized_epoch in the name makes it clear at the call site that you must pass the finalized epoch and not e.g. the current epoch

/// Check if a builder is active in a state with `finalized_epoch`.
///
/// This implements `is_active_builder` from the spec.
pub fn is_active_at_finalized_epoch(&self, finalized_epoch: Epoch, spec: &ChainSpec) -> bool {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should this be named is_active_builder to match spec naming?

Copy link
Member Author

Choose a reason for hiding this comment

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

Farming comment credits? Isn't this the same as your other comment? #8801 (comment)

@michaelsproul michaelsproul added ready-for-merge This PR is ready to merge. and removed ready-for-review The code is ready for review labels Feb 12, 2026
@mergify mergify bot added the queued label Feb 12, 2026
@mergify
Copy link

mergify bot commented Feb 12, 2026

Merge Queue Status

Rule: default


This pull request spent 29 minutes 45 seconds in the queue, including 27 minutes 36 seconds running CI.

Required conditions to merge
  • check-success=local-testnet-success
  • check-success=test-suite-success

mergify bot added a commit that referenced this pull request Feb 12, 2026
@mergify mergify bot merged commit b8072c5 into sigp:unstable Feb 12, 2026
36 checks passed
@mergify mergify bot removed the queued label Feb 12, 2026
@michaelsproul michaelsproul deleted the gloas-payload-bid-consensus branch February 12, 2026 05:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

consensus An issue/PR that touches consensus code, such as state_processing or block verification. gloas ready-for-merge This PR is ready to merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants