Consider builder bids during block production

[StefanBratanov]

PR Description

Calling eth/v1/builder/execution_payload_bid/{slot}/{parent_hash}/{parent_root}/{proposer_pubkey} during block production with each configured builder and considering the bid (comparing it vs p2p bids and local bid)

Kurtosis config

participants_matrix:
  el:
    - el_type: nethermind
      el_image: ethpandaops/nethermind:glamsterdam-devnet-8
  cl:
    - cl_type: teku
      cl_image: consensys/teku:develop
      cl_extra_params:
        - "--Xbuilder-urls=http://buildoor:8080"
        - "--Xbuilder-circuit-breaker-enabled=false"
  count: 1

mev_type: buildoor
buildoor_params:
  image: ethpandaops/buildoor:main
  builder_api: true
  epbs_builder: true
  lifecycle: true
  extra_args:
    - --log-level=debug
    - --builder-api-require-auth

network_params:
  preset: minimal
  seconds_per_slot: 6
  gloas_fork_epoch: 0
  withdrawal_type: "0x01"
  validator_balance: 32
  builder_count: 1
  builder_balance: 100
  deploy_eip8282_contracts: true

additional_services:
  - dora

snooper_enabled: true
global_log_level: info

port_publisher:
  additional_services:
    enabled: true

dora_params:
  image: ethpandaops/dora:master

Fixed Issue(s)

fixes #10822

Documentation

• I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

• I thought about adding a changelog entry, and added one if I deemed necessary.

---

Note

High Risk
Changes core Gloas block production and bid economics (selection, scoring, caching) with new external builder HTTP calls on the hot path; mis-selection or auth/API mismatches could affect proposer revenue or block validity.

Overview
Adds builder API bid retrieval at proposal time for Gloas: configured builders are queried via eth/v1/builder/execution_payload_bid/... (auth always sent in the POST body), and those bids compete with gossip P2P bids and the local EL payload when choosing the signed execution payload bid.

Bid selection and metadata are refactored around new RemoteBid / BidForBlock records: builder bids are scored with on-chain value plus capped execution payment; P2P bids use collateral value only and respect min_bid; ties favor the builder API bid. The winning bid’s wei value and optional builder URL are written into per-slot SlotCaches during block body assembly (replacing validator-side value derivation from the bid message alone).

The builder REST client no longer supports unauthenticated empty POSTs for payload bids. ethereum:statetransition and beacon chain wiring gain BuilderBidFetcher + StakedBuilderClientProvider; module dependency rules allow :builder from statetransition.

^{Reviewed by Cursor Bugbot for commit fb6c723. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Reviewed by Cursor Bugbot for commit db761d6. Configure here.}

[cursor]

Builder bids skip parent matching

High Severity

selectBestRemoteBid filters P2P bids by parent root and parent hash, but builder bids only go through isBuilderAllowed. That skip assumes fetching already validated them, yet getBuilderBids does not. A mismatched builder bid can win on value and be included in the produced block, which peers will reject.

Additional Locations (1)

• ethereum/statetransition/src/main/java/tech/pegasys/teku/statetransition/execution/BuilderBidFetcher.java#L90-L94

 

^{Reviewed by Cursor Bugbot for commit db761d6. Configure here.}

[StefanBratanov]

this is covered in #11194