Skip to content

Deprecate pre electra attestation submissions#531

Closed
eserilev wants to merge 1 commit into
ethereum:masterfrom
eserilev:deprecate-pre-electra-attestation
Closed

Deprecate pre electra attestation submissions#531
eserilev wants to merge 1 commit into
ethereum:masterfrom
eserilev:deprecate-pre-electra-attestation

Conversation

@eserilev

@eserilev eserilev commented May 12, 2025

Copy link
Copy Markdown
Contributor

This PR aims to deprecate support for pre-electra Attestations in the submitPoolAttestationsV2 endpoint. Since we are post Electra it seems that there is no reason to support the pre-Electra variant. It also allows client teams to simplify the implementation of this endpoint (e.g. Lighthouse can remove 100-ish lines of code with this deprecation). To be spec compliant clients must already be submitting SingleAttestations to this endpoint, so unless there are non-spec compliant client implementations, this shouldn't cause any disruptions.

@nflaig

nflaig commented May 13, 2025

Copy link
Copy Markdown
Member

not really in favor of this on the spec side, so far all apis have been kept backward compatible, implementations can choose to stop supporting previous forks if they would like to

@eserilev

Copy link
Copy Markdown
Contributor Author

sounds good, I'll close this then

@eserilev eserilev closed this May 13, 2025
mergify Bot pushed a commit to sigp/lighthouse that referenced this pull request Jun 17, 2025
#6970


  This allows for us to receive `SingleAttestation` over gossip and process it without converting. There is still a conversion to `Attestation` as a final step in the attestation verification process, but by then the `SingleAttestation` is fully verified.

I've also fully removed the `submitPoolAttestationsV1` endpoint as its been deprecated

I've also pre-emptively deprecated supporting `Attestation` in `submitPoolAttestationsV2` endpoint. See here for more info: ethereum/beacon-APIs#531

I tried to the minimize the diff here by only making the "required" changes. There are some unnecessary complexities with the way we manage the different attestation verification wrapper types. We could probably consolidate this to one wrapper type and refactor this even further. We could leave that to a separate PR if we feel like cleaning things up in the future.

Note that I've also updated the test harness to always submit `SingleAttestation` regardless of fork variant. I don't see a problem in that approach and it allows us to delete more code :)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants