Skip to content

Added version field to gloas events#10481

Merged
rolfyone merged 3 commits intoConsensys:masterfrom
rolfyone:events-gloas
Mar 17, 2026
Merged

Added version field to gloas events#10481
rolfyone merged 3 commits intoConsensys:masterfrom
rolfyone:events-gloas

Conversation

@rolfyone
Copy link
Copy Markdown
Contributor

@rolfyone rolfyone commented Mar 12, 2026

Implements change in
ethereum/beacon-APIs#587

If any devnet0 watchers are looking at these, this is non-compatible.

Fixed Issue(s)

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

Medium Risk
Changes the JSON shape of execution_payload_bid and payload_attestation_message SSE payloads by wrapping existing data with a version field, which is a client-visible (potentially breaking) API change.

Overview
Adds a version field to Gloas-specific SSE events. The execution_payload_bid and payload_attestation_message event payloads are now emitted as an object containing {version, data} instead of the raw message/bid, using MILESTONE_TYPE and SpecMilestone.GLOAS.

Tests are updated to assert the serialized SSE output includes "version":"gloas" for both event types.

Written by Cursor Bugbot for commit eb6888a. This will update automatically on new commits. Configure here.

Implements change in
ethereum/beacon-APIs#587

If any devnet0 watchers are looking at these, this is non-compatible.
@rolfyone rolfyone enabled auto-merge (squash) March 17, 2026 01:15
@rolfyone rolfyone merged commit 6a0f928 into Consensys:master Mar 17, 2026
68 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Mar 17, 2026
@rolfyone rolfyone deleted the events-gloas branch March 17, 2026 01:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants