Add POST beacon/bid endpoint

[eserilev]

Issue Addressed

This endpoint is needed for buildoor (and eventually our builder client once its implemented)

[chong-he]

Looks good overall, just some minor comments, mostly cosmetics.

[chong-he]

Looks great now!

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-30 08:59 UTC · Rule: default
• ✅ Checks started · on draft merge queue: embarking unstable (8396dc8) and #9347 together #9375
• ❌ Checks failed
• 🚫 Left the queue — 2026-05-30 09:21 UTC · at a3e2664c7f98dba0341c67b74284843bb0c23172

This pull request spent 21 minutes 39 seconds in the queue, including 19 minutes 35 seconds running CI.

Waiting for

• check-success=local-testnet-success
• check-success=test-suite-success

All conditions

• check-success=local-testnet-success
• check-success=test-suite-success
• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • Add POST beacon/bid endpoint #9347

Reason

The merge conditions cannot be satisfied due to failing checks

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[eserilev]

@mergify requeue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-06-01 09:40 UTC · Rule: default
• ✅ Checks started · on draft merge queue: embarking unstable (cf259e7) and #9347 together #9389
• ❌ Checks failed
• 🚫 Left the queue — 2026-06-01 10:05 UTC · at a3e2664c7f98dba0341c67b74284843bb0c23172

This pull request spent 25 minutes 7 seconds in the queue, including 22 minutes 8 seconds running CI.

Waiting for

• check-success=local-testnet-success
• check-success=test-suite-success

All conditions

• check-success=local-testnet-success
• check-success=test-suite-success
• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • Add POST beacon/bid endpoint #9347

Reason

The merge conditions cannot be satisfied due to failing checks

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[eserilev]

@mergify requeue

[mergify]

requeue

🛑 The pull request has been removed from the queue default

Details

The pull request #9347 has been manually updated.

You can take a look at Mergify Merge Queue check runs for more details about the failure.

[eserilev]

@mergify requeue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-06-01 11:41 UTC · Rule: default
• ✅ Checks passed · on draft merge queue: embarking unstable (cf259e7) and [#9347 + #9383] together #9390
• ✅ Merged — 2026-06-01 12:10 UTC · at e0d1f8198b98e49920d4e41f8615cdb5f850546b · squash

This pull request spent 29 minutes 18 seconds in the queue, including 27 minutes 34 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • Add POST beacon/bid endpoint #9347
  • Deprecate blob lookup sync #9383
• check-success=local-testnet-success
• check-success=test-suite-success