cl/beacon: add single_attestation event topic support (#18142) #18277
+3
−1
Conversation
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
This PR fixes the Beacon API events endpoint to publish SingleAttestation objects (introduced in Electra) under the `single_attestation` topic instead of `attestation`. Currently, Caplin publishes all attestations under the `attestation` topic, regardless of whether they are pre-Electra `Attestation` objects or post-Electra `SingleAttestation` objects. **References:** - https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/p2p-interface.md#beacon_attestation_subnet_id - https://github.com/ethereum/beacon-APIs/blob/master/apis/eventstream/index.yaml#L71 - https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md#singleattestation **For context:** We'd love to see this added. We have some contributoors pushing to the ethPandaOps Xatu dataset using Caplin - but we're not capturing attestations because of it. **For example:** https://lab.ethpandaops.io/xatu/contributors/abstractdrank74#attestation-latency
AskAlexSharov
approved these changes
Dec 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes the Beacon API events endpoint to publish SingleAttestation objects (introduced in Electra) under the
single_attestationtopic instead ofattestation.Currently, Caplin publishes all attestations under the
attestationtopic, regardless of whether they are pre-ElectraAttestationobjects or post-ElectraSingleAttestationobjects.References:
https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/p2p-interface.md#beacon_attestation_subnet_id -
https://github.com/ethereum/beacon-APIs/blob/master/apis/eventstream/index.yaml#L71 -
https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md#singleattestation
For context:
We'd love to see this added. We have some contributoors pushing to the ethPandaOps Xatu dataset using Caplin - but we're not capturing attestations because of it. For example:
https://lab.ethpandaops.io/xatu/contributors/abstractdrank74#attestation-latency