feat(api): add executionPayloadBid SSE event#17
Closed
lodekeeper wants to merge 3 commits intounstablefrom
Closed
Conversation
Emits an execution_payload_bid SSE event when a SignedExecutionPayloadBid passes gossip validation. Follows the beacon-APIs v5.0.0-alpha.1 event stream spec. Changes: - events.ts: New EventType.executionPayloadBid with versioned data - gossipHandlers.ts: Emit event after bid pool insertion - events test data: Add fixture for round-trip test
nflaig
reviewed
Apr 4, 2026
| executionPayloadGossip = "execution_payload_gossip", | ||
| /** The node has verified that the execution payload and blobs for a block are available and ready for payload attestation */ | ||
| executionPayloadAvailable = "execution_payload_available", | ||
| /** The node has received a valid SignedExecutionPayloadBid (from P2P or API) that passes gossip validation on the execution_payload_bid topic */ |
Owner
Author
There was a problem hiding this comment.
Fixed — now matches the beacon-APIs spec verbatim: "The node has received a SignedExecutionPayloadBid (from P2P or API) that passes gossip validation on the execution_payload_bid topic"
nflaig
reviewed
Apr 4, 2026
| const executionPayloadBid = sszDeserialize(topic, serializedData); | ||
| await validateGossipExecutionPayloadBid(chain, executionPayloadBid); | ||
|
|
||
| // Emit SSE event for valid gossip-validated bid |
|
please make sure oapi spec tests are passing, and update to alpha.1, remove from ignore list |
Address review feedback: - JSDoc description now matches beacon-APIs spec verbatim - Remove useless comment above emitter call
- update beacon oapi spec test to v5.0.0-alpha.1 - remove execution_payload_bid and data_column_sidecar from ignored topics - align executionPayloadBid event fixture with the alpha.1 spec example
Owner
Author
|
Addressed.
Pushed in |
|
@lodekeeper you can close this, I ported this to lodestar myself, thanks |
Owner
Author
|
Closing as requested — thanks for porting this upstream! 🤖 |
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
2 participants
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.
Summary
Adds the
execution_payload_bidSSE event per beacon-APIs v5.0.0-alpha.1 event stream spec.What it does
Emits an
execution_payload_bidevent when aSignedExecutionPayloadBidpasses gossip validation on theexecution_payload_bidtopic. The event data follows the versioned wrapper pattern ({version, data}), consistent withpayloadAttributesand other versioned events.Changes
packages/api/src/beacon/routes/events.ts— NewEventType.executionPayloadBid, event data type, and versioned SSZ codecpackages/beacon-node/src/network/processor/gossipHandlers.ts— Emit event after gossip validation and bid pool insertionpackages/api/test/unit/beacon/testData/events.ts— Test fixture for round-trip serializationSpec reference
apis/eventstream/index.yaml