Skip to content

merge queue: checking #9864 on unstable (d9caac7) - #10079

Closed
mergify[bot] wants to merge 18 commits into
unstablefrom
mergify/merge-queue/f6f33ecf73
Closed

mergify[bot] wants to merge 18 commits into
unstablefrom
mergify/merge-queue/f6f33ecf73

Conversation

@mergify

@mergify mergify Bot commented Sep 18, 2026 •

Copy link
Copy Markdown

🎉 This pull request has been checked successfully and will be merged soon. 🎉

#9864 is queued for merge on branch unstable (d9caac7).

This pull request has been created by Mergify to check the mergeability of #9864.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: d9caac710a9edbd5ca5251a39e58ed30e9b2adc2
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 9864
    scopes: []
scopes: []
...

ethDreamer and others added 18 commits August 26, 2026 14:12
…(Gloas builder API 3/5)

Third PR of the Gloas builder API stack:

- beacon_chain: direct builder bid verification (spawned on the blocking
  executor), gossip-bid refinements, wei-domain bid selection
  (`BidCandidate`/`BidSource`), and Gloas block production that assembles
  local, gossip, and direct-builder candidates
- network: process payload-bid and proposer-preference gossip, including the
  new `PayloadBidError` variants
- client: construct the `Builders` service when the Gloas fork is scheduled
  and wire it into the beacon chain

The HTTP API still serves `GET` produceBlockV4 at this point; the `POST`
conversion and the `Eth-Builder-Url` round-trip land in the next PR.

Change-Id: Ieccaee5db81bf871c19cef1b79fc48283be9dd51
…builder API 4/5)

Fourth PR of the Gloas builder API stack (beacon-APIs #630):

- convert `/eth/v4/validator/blocks/{slot}` to POST with an optional
  `BuilderConfig` body (min_bid, builder_boost_factor, direct builders)
- add `POST /eth/v1/validator/builder_preferences` for forwarding signed
  builder preferences
- set `Eth-Builder-Url` on produceBlockV4 responses when a direct-builder bid
  wins, accept it on `POST /eth/v2/beacon/blocks`, and forward the signed
  block to that builder

The validator client still uses the legacy GET methods at this point; it
migrates in the final PR of this stack.

Change-Id: I0ad30b8f36ad9b588ea1a0398220f92c9597bb95
…API 5/5)

Final PR of the Gloas builder API stack:

- sign builder request-auth and preferences (REQUEST_AUTH signing domain,
  web3signer message type)
- add the builder configuration store (`builder_definitions.yml`) and book
  documentation
- add the builder-preferences service and switch block production to
  `POST` produceBlockV4 with a `BuilderConfig` body, threading the
  `Eth-Builder-Url` header through block publication
- remove the now-unused legacy `GET` produceBlockV4 client methods

Change-Id: Iaeeaf6205a024e4fb9fd11aae6ac6a75978a8320
Changes:
Derive default auth data from the lowercase ASCII hostname.
Preserve explicit auth bytes across signing and keymanager configuration.
Cover URL spelling, IPv6, override and API response behavior.
Changes:
Use recognised wording in the builder configuration guide.
Add the specification term punycode to the spelling dictionary.
@cla-assistant

cla-assistant Bot commented Sep 18, 2026

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 3 committers have signed the CLA.

✅ ethDreamer
✅ jimmygchen
❌ mergify[bot]
You have signed the CLA already but the status is still pending? Let us recheck it.

@mergify mergify Bot closed this Sep 18, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/f6f33ecf73 branch September 18, 2026 12:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants