Gloas Builder-API spec updates - #161
Merged
Merged
Conversation
Contributor
Author
|
Will merge these changes to maintain one single branch |
bharath-123
added a commit
that referenced
this pull request
Jun 11, 2026
* initial builder-api for gloas * updates * pass in params while querying execution payload bid * introduce validator registrations v2 * run doctoc * update validator registration v2 * add more specs * run lint * updates * abstract execution_payment_accepted to a BuilderPreferences struct * minor fixes * run doctoc * use correct method to check if builder is active * save * updates * add information for bidding * update * add bid request auth * remove builder index from validator registration * add validator registration type * link to api calls * add some notes * fix return type of execution_payload_bid.yaml * use max_trusted_bid in builder preferences * run linter * fix spellchecker * update bid request auth according to feedback * minor updates * use a salt in the bid request auth * correctly render constants table * address feedback * update bid request auth to request auth * fix typo * use salt instead of url * use get-upcoming-proposal-slots * Update liveness failsafe section * update RequestAuth types * deprecate validator registrations in favour of proposer preferences * updates to api * run lint * remove description of proposer preferences * add validator pubkey in builder preferences and request auth * specify setting fee reicpient in execution payload bid * updates to epbs * updates * minor updates * address feedback * minor updates * add an error type for missing auth request * Endpoint to submit builder preferences (#160) * add api to submit builder preferences * add builder preferences type * add signed builder preference * updates * specify precedence and when to submit the preference * send preference based on epoch lookahead * send request auth with builder preferences * use builder pubkey in request auth * add validator pubkey to the query param * some updates * Gloas Builder-API spec updates (#161) * updates * remove header to communicate max_execution_payment * use proposer_pubkey instead of index * some spec updates * update is_eligible_for_bid * update error code * don't encapsulate the beacon block under a "data" field * add an identity api * reword sentence on block and payload decoupling * update request auth to use builder url * update error codes * add eth consensus version header * suffix containers with v1 * run make lint * fix spellcheck * minor spec updates * builder can choose to not serve bid if preferences not seen * address justins + AntiD2ta feedback * make the request auth more generic * rename MAX_URL_BYTES to MAX_DATA_BYTES * remove unecessary specification * update spec to use auth.data instead of auth.builder_url * address feedback and add examples * add ssz examples
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
1 participant
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.
The following changes made to the builder-api spec:
max_trusted_bidtomax_execution_paymentX-Eth-Max-Trusted-Bid. The max_execution_payment is only communicated via the builder preferences endpoint. If builder has not seen the max_execution_payment, they can either pay via a trustless payment or choose to not serve the bid.proposer_pubkeyinstead ofproposer_indexin query params to get the bid and send the builder preferences.is_eligible_for_bidto check if the validator corresponding toproposer_pubkeyis active and is the current proposer for the slot.