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

[Merged by Bors] - Add parent_block_number to payload SSE #4053

Closed

Conversation

michaelsproul
Copy link
Member

Issue Addressed

In #4027 I forgot to add the parent_block_number to the payload attributes SSE.

Proposed Changes

Compute the parent block number while computing the pre-payload attributes. Pass it on to the SSE stream.

Additional Info

Not essential for v3.5.1 as I suspect most builders don't need the parent_block_root. I would like to use it for my dummy no-op builder however.

@michaelsproul michaelsproul added ready-for-review The code is ready for review builder API v4.0.0 Mainnet Capella release expected late March 2023 labels Mar 6, 2023
Copy link
Member

@paulhauner paulhauner left a comment

Choose a reason for hiding this comment

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

LGTM!

@paulhauner paulhauner added ready-for-merge This PR is ready to merge. and removed ready-for-review The code is ready for review labels Mar 14, 2023
@@ -47,7 +47,7 @@ use types::{

mod block_hash;
mod engine_api;
mod engines;
pub mod engines;
Copy link
Member Author

Choose a reason for hiding this comment

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

This is a sneaky change to support eleel.

@paulhauner
Copy link
Member

bors r+

bors bot pushed a commit that referenced this pull request Mar 14, 2023
## Issue Addressed

In #4027 I forgot to add the `parent_block_number` to the payload attributes SSE.

## Proposed Changes

Compute the parent block number while computing the pre-payload attributes. Pass it on to the SSE stream.

## Additional Info

Not essential for v3.5.1 as I suspect most builders don't need the `parent_block_root`. I would like to use it for my dummy no-op builder however.
@bors
Copy link

bors bot commented Mar 14, 2023

Build failed (retrying...):

bors bot pushed a commit that referenced this pull request Mar 14, 2023
## Issue Addressed

In #4027 I forgot to add the `parent_block_number` to the payload attributes SSE.

## Proposed Changes

Compute the parent block number while computing the pre-payload attributes. Pass it on to the SSE stream.

## Additional Info

Not essential for v3.5.1 as I suspect most builders don't need the `parent_block_root`. I would like to use it for my dummy no-op builder however.
@bors
Copy link

bors bot commented Mar 14, 2023

Build failed (retrying...):

bors bot pushed a commit that referenced this pull request Mar 14, 2023
## Issue Addressed

In #4027 I forgot to add the `parent_block_number` to the payload attributes SSE.

## Proposed Changes

Compute the parent block number while computing the pre-payload attributes. Pass it on to the SSE stream.

## Additional Info

Not essential for v3.5.1 as I suspect most builders don't need the `parent_block_root`. I would like to use it for my dummy no-op builder however.
@bors bors bot changed the title Add parent_block_number to payload SSE [Merged by Bors] - Add parent_block_number to payload SSE Mar 14, 2023
@bors bors bot closed this Mar 14, 2023
Woodpile37 pushed a commit to Woodpile37/lighthouse that referenced this pull request Jan 6, 2024
In sigp#4027 I forgot to add the `parent_block_number` to the payload attributes SSE.

Compute the parent block number while computing the pre-payload attributes. Pass it on to the SSE stream.

Not essential for v3.5.1 as I suspect most builders don't need the `parent_block_root`. I would like to use it for my dummy no-op builder however.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
builder API ready-for-merge This PR is ready to merge. v4.0.0 Mainnet Capella release expected late March 2023
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants