Skip to content

Align Gloas builder API request auth types and bid request headers with builder-specs - #17372

Merged
terencechain merged 1 commit into
developfrom
request-auth-spec-alignment
Aug 18, 2026
Merged

Align Gloas builder API request auth types and bid request headers with builder-specs#17372
terencechain merged 1 commit into
developfrom
request-auth-spec-alignment

Conversation

@terencechain

Copy link
Copy Markdown
Collaborator
  • Rename RequestAuthV1/SignedRequestAuthV1/BuilderPreferencesV1/BuilderPreferencesRequestV1 to their unversioned spec names, and validator_pubkey to proposer_pubkey, per builder-specs#165
  • The bid request now requires the signed request auth body and always sends the Date-Milliseconds and X-Timeout-Ms headers, both required by the spec
  • First of a small stack replacing Decouple signed builder auth data from the HTTP dial target #17124: next up is the block-request builder entries wire + auth/dial-target decoupling, then per-builder bid enforcement

@terencechain
terencechain force-pushed the request-auth-spec-alignment branch from 0d271fa to b4198e0 Compare August 18, 2026 18:26

@james-prysm james-prysm left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@terencechain
terencechain added this pull request to the merge queue Aug 18, 2026
Merged via the queue into develop with commit ad03bcf Aug 18, 2026
32 of 34 checks passed
@terencechain
terencechain deleted the request-auth-spec-alignment branch August 18, 2026 19:44
@github-project-automation github-project-automation Bot moved this from Unassigned to Done in Gloas Aug 18, 2026
pull Bot pushed a commit to All-Blockchains/prysm that referenced this pull request Aug 19, 2026
- Replace `builder_request_auths` on `BlockRequest` with a
`BuilderConfig` carrying resolved `BuilderEntry`s (`url`, `auth`,
`builder_pubkeys`, `max_execution_payment`, `min_bid`,
`builder_boost_factor`), shaped to beacon-APIs#630
- Request auths now sign the entry's auth data (default: the UTF-8 bytes
of its `url`) instead of the URL string, so the signed identity is
decoupled from the HTTP dial target and a sidecar/proxy can front a
builder
- The beacon node routes bid requests by entry `url` and forwards the
auth byte-for-byte; entries may share a `url` with distinct auth data,
one request per entry
- `SubmitBuilderPreferencesRequest` carries the dial `url` separately
from the opaque auth data
- The validator client resolves entries at propose time and signs on
cache miss, so proposals no longer depend on a prior preference push
- Per-entry limits ride the wire but are not yet enforced; the beacon
still applies the pushed per-pubkey `max_execution_payment` (enforcement
is the next PR in the stack)

Second of the stack replacing OffchainLabs#17124, on top of OffchainLabs#17372.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants