Add `execution_payload` and `execution_payload_gossip` event by nflaig · Pull Request #588 · ethereum/beacon-APIs

nflaig · 2026-03-11T22:38:17Z

This adds execution_payload and execution_payload_gossip to the eventstream.

The events mirror the existing block and block_gossip events.

execution_payload_gossip is emitted when an execution payload passes gossip validation
execution_payload is emitted when an execution payload is successfully imported
execution_payload_available is emitted when an execution payload and all data are available for payload attestation without verifying the execution payload itself

These events enable measuring execution payload timings via sidecar software such as contributoor.

rolfyone · 2026-03-12T02:43:00Z

we should probably add versions to this too...

ensi321 · 2026-03-12T07:32:02Z

                event: data_column_sidecar
                data: {"block_root": "0xcf8e0d4e9587369b2301d0790347320302cc0943d5a1884560367e8208d920f2", "index": "1", "slot": "1"}
+            execution_payload:
+              description: The node has received a `SignedExecutionPayloadEnvelope` (from P2P or API) that is successfully imported on the fork-choice `on_execution_payload` handler


May I know the difference between this and execution_payload_available?
This one emits when the payload is fully imported, execution_payload_available emits when payload is available for PTC vote.
Is there a gap/delay between the occurrence of these two events?

~~I guess you are right, there shouldn't be much of a difference in the timing and would at most be minimal based on how the client specific import pipeline works.~~

~~We can probably remove it and only stick to execution_payload_gossip and execution_payload_available~~

execution_payload_available is emitted when the execution payload + all data (based on custody) is available, it does not require the execution payload to be valid, while execution_payload does since it is emitted after successful import into fork choice via on_execution_payload handler, so it includes the time it takes for the EL to execute and verify the execution payload

nflaig · 2026-03-12T09:21:55Z

we should probably add versions to this too...

was thinking about that, I am not that convinced that versioning here makes sense as the schema is not based on a spec container

rolfyone · 2026-03-16T01:14:12Z

was thinking about that, I am not that convinced that versioning here makes sense as the schema is not based on a spec container

still, we might be better off being consistent?

nflaig · 2026-03-16T10:07:23Z

still, we might be better off being consistent?

but that means not having the version/data container here? eg. block_gossip doesn't have that either because the event doesn't emit data based on a spec container while evens in #587 do, so having the version there makes sense

I am open to adding a version here too if that's really what we want

rolfyone · 2026-03-16T23:04:18Z

@michaelsproul thoughts?

dknopik · 2026-03-27T13:31:33Z

I'm not Michael, but implementing this in Lighthouse. I agree with @nflaig, let's version only the directly embedded consensus objects. Versioning the others by fork name as well would be inconsistent as noted above, and would be strange to use in cases where we e.g. want to add some field to an event outside of the fork lifecycle.

james-prysm · 2026-03-27T18:16:08Z

haven't started implementing this yet but looks good to me

Adds execution payload events from ethereum/beacon-APIs#588 --------- Co-authored-by: Matthew Keil <github@mail.matthewkeil.com>

Implement boilerplate for new SSE events as specified in - ethereum/beacon-APIs#588 While that one is not merged yet, I believe the SSE events might be utilized in Dora already. Implement the boilerplate, i.e. subscription tracking and publish queues. A PR to implement to fully implement already implementable events will follow. Co-Authored-By: Daniel Knopik <daniel@dknopik.de>

nflaig · 2026-04-16T21:34:22Z

applied changes due to ethereum/consensus-specs#5094, the events no longer emit the state_root

**What type of PR is this?** > Feature **What does this PR do? Why is it needed?** Adds event emission for `execution_payload_gossip` as per ethereum/beacon-APIs#588. **Which issues(s) does this PR fix?** N/A **Other notes for review** https://github.com/OffchainLabs/prysm/blob/e94d46b8c175530cac4deb5e0b082366ba9fb6be/beacon-chain/sync/validate_beacon_blocks.go#L276-L283 `execution_payload_gossip` mirrors `block_gossip` event, so you can see exactly same pattern as our implementation like above. **Testing** ``` ➜ kurtosis-config curl -X 'GET' \ 'http://<beacon-node-rpc-url>/eth/v1/events?topics=execution_payload_gossip' \ -H 'accept: text/event-stream' event: execution_payload_gossip data: {"slot":"65","builder_index":"18446744073709551615","block_hash":"0x36b193697ddff3ece883e04a554e108c280ff5cb1c101aed886cb15bd76515bb","block_root":"0x765c25b8e75955f3f1eabbe6ab9bebc3a05f5fb94dcbbef20b1ddde4192c5244"} ``` with this config: ```yaml participants: - el_type: ethrex el_image: ethpandaops/ethrex:glamsterdam-devnet-4 el_extra_params: - --http.api=eth,net,web3,admin cl_type: prysm cl_image: prysm-bn-custom-image:latest vc_image: prysm-vc-custom-image:latest supernode: true count: 3 cl_extra_params: - --subscribe-all-subnets - --verbosity=debug vc_extra_params: - --verbosity=debug network_params: fulu_fork_epoch: 0 gloas_fork_epoch: 2 seconds_per_slot: 6 genesis_delay: 40 additional_services: - dora global_log_level: debug ``` **Acknowledgements** - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).

When processing an execution payload envelope, the data availability (DA) check previously ran sequentially after consensus verification and EL validation had both completed. This moves the DA check into the same `errgroup` so it runs concurrently with payload verification and EL `newPayload` validation. - The DA check only runs when the latest bid carries blob KZG commitments (unchanged behavior). - Uses the group context (`gCtx`) so a failure in any of the three cancels the others. This enables ethereum/beacon-APIs#588 to emit `execution_payload_available`

**What type of PR is this?** > Feature **What does this PR do? Why is it needed?** Adds event emission for `execution_payload` as per ethereum/beacon-APIs#588. Refactors `ReceiveExecutionPayloadEnvelope` by decoupling EL validation from signature verification+DA check to satisfy the event emission timing for `execution_payload_available`. **Which issues(s) does this PR fix?** N/A **Other notes for review** - Renames the existing struct names clearly to indicate whether it is for `execution_payload` or `execution_payload_available`. **Testing** Kurtosis config file: ```yaml participants: - el_type: ethrex el_image: ethpandaops/ethrex:glamsterdam-devnet-4 el_extra_params: - --http.api=eth,net,web3,admin cl_type: prysm cl_image: prysm-bn-custom-image:latest vc_image: prysm-vc-custom-image:latest supernode: true count: 3 cl_extra_params: - --subscribe-all-subnets - --verbosity=debug vc_extra_params: - --verbosity=debug network_params: fulu_fork_epoch: 0 gloas_fork_epoch: 2 seconds_per_slot: 6 genesis_delay: 40 additional_services: - dora global_log_level: debug ``` You can receive **both** events with this command: ```bash ➜ prysm git:(feat/execution-payload-event) curl -X 'GET' \ 'http://127.0.0.1:32813/eth/v1/events?topics=execution_payload&topics=execution_payload_available' \ -H 'accept: text/event-stream' ``` Result: ``` event: execution_payload_available data: {"slot":"64","block_root":"0x0ef955bd61d0e402bc71d6b97f223fa9377683dce64561069c408c5c2e0d548d"} event: execution_payload data: {"slot":"64","builder_index":"18446744073709551615","block_hash":"0xbf648d1f316e6d8284ed74c97c4942af1daf052f7517c5fca8b00836151e1d3d","block_root":"0x0ef955bd61d0e402bc71d6b97f223fa9377683dce64561069c408c5c2e0d548d","execution_optimistic":false} event: execution_payload_available data: {"slot":"65","block_root":"0xfec09760c4bd83adcff905cb95b732bfcef7c00f529f5e2471ff34db512fbdbe"} event: execution_payload data: {"slot":"65","builder_index":"18446744073709551615","block_hash":"0x6c327ec9e4de925b28eb5e127fbfae8d6082590199d35423ea95f8f0300c0423","block_root":"0xfec09760c4bd83adcff905cb95b732bfcef7c00f529f5e2471ff34db512fbdbe","execution_optimistic":false} ``` **Acknowledgements** - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).

**What type of PR is this?** > Feature **What does this PR do? Why is it needed?** Adds event emission for `execution_payload_gossip` as per ethereum/beacon-APIs#588. **Which issues(s) does this PR fix?** N/A **Other notes for review** https://github.com/OffchainLabs/prysm/blob/e94d46b8c175530cac4deb5e0b082366ba9fb6be/beacon-chain/sync/validate_beacon_blocks.go#L276-L283 `execution_payload_gossip` mirrors `block_gossip` event, so you can see exactly same pattern as our implementation like above. **Testing** ``` ➜ kurtosis-config curl -X 'GET' \ 'http://<beacon-node-rpc-url>/eth/v1/events?topics=execution_payload_gossip' \ -H 'accept: text/event-stream' event: execution_payload_gossip data: {"slot":"65","builder_index":"18446744073709551615","block_hash":"0x36b193697ddff3ece883e04a554e108c280ff5cb1c101aed886cb15bd76515bb","block_root":"0x765c25b8e75955f3f1eabbe6ab9bebc3a05f5fb94dcbbef20b1ddde4192c5244"} ``` with this config: ```yaml participants: - el_type: ethrex el_image: ethpandaops/ethrex:glamsterdam-devnet-4 el_extra_params: - --http.api=eth,net,web3,admin cl_type: prysm cl_image: prysm-bn-custom-image:latest vc_image: prysm-vc-custom-image:latest supernode: true count: 3 cl_extra_params: - --subscribe-all-subnets - --verbosity=debug vc_extra_params: - --verbosity=debug network_params: fulu_fork_epoch: 0 gloas_fork_epoch: 2 seconds_per_slot: 6 genesis_delay: 40 additional_services: - dora global_log_level: debug ``` **Acknowledgements** - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).

When processing an execution payload envelope, the data availability (DA) check previously ran sequentially after consensus verification and EL validation had both completed. This moves the DA check into the same `errgroup` so it runs concurrently with payload verification and EL `newPayload` validation. - The DA check only runs when the latest bid carries blob KZG commitments (unchanged behavior). - Uses the group context (`gCtx`) so a failure in any of the three cancels the others. This enables ethereum/beacon-APIs#588 to emit `execution_payload_available`

**What type of PR is this?** > Feature **What does this PR do? Why is it needed?** Adds event emission for `execution_payload` as per ethereum/beacon-APIs#588. Refactors `ReceiveExecutionPayloadEnvelope` by decoupling EL validation from signature verification+DA check to satisfy the event emission timing for `execution_payload_available`. **Which issues(s) does this PR fix?** N/A **Other notes for review** - Renames the existing struct names clearly to indicate whether it is for `execution_payload` or `execution_payload_available`. **Testing** Kurtosis config file: ```yaml participants: - el_type: ethrex el_image: ethpandaops/ethrex:glamsterdam-devnet-4 el_extra_params: - --http.api=eth,net,web3,admin cl_type: prysm cl_image: prysm-bn-custom-image:latest vc_image: prysm-vc-custom-image:latest supernode: true count: 3 cl_extra_params: - --subscribe-all-subnets - --verbosity=debug vc_extra_params: - --verbosity=debug network_params: fulu_fork_epoch: 0 gloas_fork_epoch: 2 seconds_per_slot: 6 genesis_delay: 40 additional_services: - dora global_log_level: debug ``` You can receive **both** events with this command: ```bash ➜ prysm git:(feat/execution-payload-event) curl -X 'GET' \ 'http://127.0.0.1:32813/eth/v1/events?topics=execution_payload&topics=execution_payload_available' \ -H 'accept: text/event-stream' ``` Result: ``` event: execution_payload_available data: {"slot":"64","block_root":"0x0ef955bd61d0e402bc71d6b97f223fa9377683dce64561069c408c5c2e0d548d"} event: execution_payload data: {"slot":"64","builder_index":"18446744073709551615","block_hash":"0xbf648d1f316e6d8284ed74c97c4942af1daf052f7517c5fca8b00836151e1d3d","block_root":"0x0ef955bd61d0e402bc71d6b97f223fa9377683dce64561069c408c5c2e0d548d","execution_optimistic":false} event: execution_payload_available data: {"slot":"65","block_root":"0xfec09760c4bd83adcff905cb95b732bfcef7c00f529f5e2471ff34db512fbdbe"} event: execution_payload data: {"slot":"65","builder_index":"18446744073709551615","block_hash":"0x6c327ec9e4de925b28eb5e127fbfae8d6082590199d35423ea95f8f0300c0423","block_root":"0xfec09760c4bd83adcff905cb95b732bfcef7c00f529f5e2471ff34db512fbdbe","execution_optimistic":false} ``` **Acknowledgements** - [x] I have read [CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md). - [x] I have included a uniquely named [changelog fragment file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd). - [x] I have added a description with sufficient context for reviewers to understand this PR. - [x] I have tested that my changes work as expected and I added a testing plan to the PR description (if applicable).

Add execution_payload and execution_payload_gossip event

1ca43f2

nflaig added the Gloas api's needed in Gloas fork. label Mar 11, 2026

chong-he mentioned this pull request Mar 12, 2026

Update head event in backwards compatible way #589

Closed

ensi321 reviewed Mar 12, 2026

View reviewed changes

Remove execution_payload event

bdec428

nflaig changed the title ~~Add execution_payload and execution_payload_gossip event~~ Add execution_payload_gossip event Mar 12, 2026

nflaig commented Mar 12, 2026

View reviewed changes

Comment thread apis/eventstream/index.yaml

Apply suggestion from @nflaig

bdd749e

nflaig mentioned this pull request Mar 16, 2026

All Core Devs - Testing (ACDT) #74, March 16, 2026 ethereum/pm#1966

Closed

4 tasks

nflaig added 2 commits March 17, 2026 10:09

Merge branch 'master' into nflaig/payload-events

824bdb9

Re-add execution_payload event

5e2c69f

nflaig changed the title ~~Add execution_payload_gossip event~~ Add execution_payload and execution_payload_gossip event Mar 27, 2026

nflaig added 2 commits March 27, 2026 11:17

Merge branch 'master' into nflaig/payload-events

e86bd87

Align wording with block events

d16dbf1

dknopik mentioned this pull request Mar 27, 2026

Gloas get payload envelope beacon API sigp/lighthouse#9038

Merged

nflaig mentioned this pull request Mar 27, 2026

feat: add execution payload events ChainSafe/lodestar#9120

Merged

ahshum mentioned this pull request Mar 27, 2026

add execution_payload events status-im/nimbus-eth2#8183

Merged

dknopik mentioned this pull request Mar 30, 2026

Add Gloas SSE event boilerplate sigp/lighthouse#9053

Merged

matthewkeil added a commit to ChainSafe/lodestar that referenced this pull request Mar 30, 2026

feat: add execution payload events (#9120)

53cbf74

Adds execution payload events from ethereum/beacon-APIs#588 --------- Co-authored-by: Matthew Keil <github@mail.matthewkeil.com>

ensi321 mentioned this pull request Mar 30, 2026

feat: enhance NetworkProcessor for gloas ChainSafe/lodestar#9025

Merged

dknopik mentioned this pull request Mar 31, 2026

Emit SSE: execution_payload sigp/lighthouse#9065

Merged

nflaig added 3 commits April 5, 2026 14:46

align more with existing gloas events

c5e9019

remove state_root

75ad752

update handler name

c39885d

rolfyone approved these changes Apr 27, 2026

View reviewed changes

nflaig merged commit 31f7d04 into master Apr 27, 2026
3 checks passed

nflaig deleted the nflaig/payload-events branch April 27, 2026 09:26

tersec mentioned this pull request Apr 27, 2026

fix proposal execution head at genesis; rm non-spec SSE; ensure envelopse SSE has envelope in database status-im/nimbus-eth2#8340

Merged

chong-he mentioned this pull request Apr 28, 2026

Tracking issue for Beacon-APIs sigp/lighthouse#9045

Open

28 tasks

tersec mentioned this pull request May 7, 2026

Recover envelope sse events status-im/nimbus-eth2#8347

Merged

hangleang mentioned this pull request May 14, 2026

Add execution_payload and execution_payload_gossip event grandinetech/grandine#690

Closed

syjn99 mentioned this pull request Jun 4, 2026

Add execution_payload_gossip event topic support OffchainLabs/prysm#16893

Merged

4 tasks

syjn99 mentioned this pull request Jun 4, 2026

Add execution_payload event support OffchainLabs/prysm#16894

Merged

4 tasks

terencechain mentioned this pull request Jun 4, 2026

Run payload envelope DA check concurrently OffchainLabs/prysm#16899

Merged

danceratopz mentioned this pull request Jun 15, 2026

All Core Devs - Testing (ACDT) #83, June 15, 2026 ethereum/pm#2116

Closed

4 tasks

Navigation Menu

Uh oh!

Add `execution_payload` and `execution_payload_gossip` event - #588

Add `execution_payload` and `execution_payload_gossip` event#588
nflaig merged 10 commits into
masterfrom
nflaig/payload-events

nflaig commented Mar 11, 2026 •

edited

Loading

Uh oh!

rolfyone commented Mar 12, 2026

Uh oh!

ensi321 Mar 12, 2026

Uh oh!

nflaig Mar 12, 2026 •

edited

Loading

Uh oh!

nflaig commented Mar 12, 2026

Uh oh!

Uh oh!

rolfyone commented Mar 16, 2026

Uh oh!

nflaig commented Mar 16, 2026

Uh oh!

rolfyone commented Mar 16, 2026

Uh oh!

dknopik commented Mar 27, 2026

Uh oh!

james-prysm commented Mar 27, 2026

Uh oh!

nflaig commented Apr 16, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Conversation

nflaig commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rolfyone commented Mar 12, 2026

Uh oh!

ensi321 Mar 12, 2026

Choose a reason for hiding this comment

Uh oh!

nflaig Mar 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

nflaig commented Mar 12, 2026

Uh oh!

Uh oh!

rolfyone commented Mar 16, 2026

Uh oh!

nflaig commented Mar 16, 2026

Uh oh!

rolfyone commented Mar 16, 2026

Uh oh!

dknopik commented Mar 27, 2026

Uh oh!

james-prysm commented Mar 27, 2026

Uh oh!

nflaig commented Apr 16, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

nflaig commented Mar 11, 2026 •

edited

Loading

nflaig Mar 12, 2026 •

edited

Loading