Add version to gloas events - #587
Merged
Merged
Conversation
michaelsproul
approved these changes
Mar 11, 2026
michaelsproul
left a comment
michaelsproul
left a comment
Contributor
There was a problem hiding this comment.
Looks good.
I've been meaning to open an issue about updating the head event in a backwards-compatible way. The dependent root fields are wrong since Fulu
rolfyone
added a commit
to rolfyone/teku
that referenced
this pull request
Mar 12, 2026
Implements change in ethereum/beacon-APIs#587 If any devnet0 watchers are looking at these, this is non-compatible.
2 tasks
This was referenced Mar 16, 2026
rolfyone
added a commit
to Consensys/teku
that referenced
this pull request
Mar 17, 2026
Implements change in ethereum/beacon-APIs#587 If any devnet0 watchers are looking at these, this is non-compatible.
hangleang
added a commit
to grandinetech/grandine
that referenced
this pull request
Apr 21, 2026
as per spec ethereum/beacon-APIs#587 to add version field to Gloas events, will do the same for `execution_payload_bid` event in following PR
hangleang
added a commit
to grandinetech/grandine
that referenced
this pull request
May 4, 2026
- Update payload attestation aggregation pool - Remove redundant PTC cache - Spawn own payload attestation task - Add version field to `payload_attestation_message` event as per spec ethereum/beacon-APIs#587 to add version field to Gloas events, will do the same for `execution_payload_bid` event in following PR - Add block payload attestation validations - Fix get_ptc
4 tasks
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
3 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.
All events that emit data based on spec containers should be wrapped by
{"version": "fork_name", "data": { ... }}so we can easily change them across forks and make it easier for consumers as they can just look at theversionfield and know the format/schema based on the spec container for that fork. This change overall makes the events more forward compatible.