Gloas local block building MVP#8754
Merged
mergify[bot] merged 80 commits intosigp:unstablefrom Feb 17, 2026
Merged
Conversation
…oas-block-and-bid-production
|
Some required checks have failed. Could you please take a look @eserilev? 🙏 |
mergify
bot
added
waiting-on-author
mergify
bot
added
ready-for-review
jimmygchen
reviewed
Feb 9, 2026
eserilev
added
ready-for-review
jimmygchen
reviewed
Feb 16, 2026
beacon_node/http_api/src/validator/execution_payload_envelope.rs
Outdated
Show resolved
Hide resolved
jimmygchen
reviewed
Feb 17, 2026
jimmygchen
approved these changes
Feb 17, 2026
Member
jimmygchen
left a comment
jimmygchen
left a comment
There was a problem hiding this comment.
I've reviewed this and I think it's in a good shape now 🎉
…lighthouse into fork/eserilev/gloas-block-and-bid-production
jimmygchen
added
ready-for-merge
Merge Queue StatusRule:
This pull request spent 34 minutes 7 seconds in the queue, including 31 minutes 55 seconds running CI. Required conditions to merge
|
6 tasks
mergify bot
pushed a commit
that referenced
this pull request
Feb 17, 2026
Continuation of #8754, some small cleanups and address TODOs Co-Authored-By: Jimmy Chen <jchen.tc@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue Addressed
The flow for local block building is
This PR adds the beacon block v4 flow , GET payload envelope and POST payload envelope (local block building only). The spec for these endpoints can be found here: ethereum/beacon-APIs#552 and is subject to change.
We needed a way to store the unsigned execution payload envelope associated to the execution payload bid that was included in the block. I introduced a new cache that stores these unsigned execution payload envelopes. the GET payload envelope queries this cache directly so that a proposer, after publishing a block, can fetch the payload envelope + sign and publish it.
I kept payload signing and publishing within the validators block service to keep things simple for now. The idea was to build out a block production MVP for devnet 0, try not to affect any non gloas code paths and build things out in such a way that it will be easy to deprecate pre-gloas code paths later on (for example block production v2 and v3).
We will eventually need to track which beacon node was queried for the block so that we can later query it for the payload. But thats not needed for the devnet.