-
-
Notifications
You must be signed in to change notification settings - Fork 369
Post-electra cleanup #7682
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
spec-electra 🦒
Issues targeting the Electra spec version
Comments
those are bit different imo, it's not clean up related but rather remaining todos, but sure can list them here to have broader overview |
This was referenced Apr 28, 2025
nflaig
added a commit
that referenced
this issue
Apr 28, 2025
**Motivation** There is no reason to use v1 attestation apis other than clients not implementing them yet but after Pectra hard fork on mainnet we know that all node operators have updated their software and v2 attestation apis are available, and since those are fork-aware / backward compatible we can even use them pre-electra (although there isn't really a network that runs on Deneb after May 7th). **Description** Use v2 attestation apis even pre-electra Part of #7412 and #7682
nflaig
added a commit
that referenced
this issue
Apr 28, 2025
**Motivation** Part of #7682, we can safely remove these workarounds in our next release as we can be sure all dependent software has been updated after Pectra hard fork on mainnet. **Description** - Remove workaround for go-eth2-client, reverts #6953 - Remove workaround fetching state from checkpointz, partially reverts #6874
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just listing out some items that can be cleaned up post-electra since we know that all clients / other software will have to be updated to be compatible with the fork (feel free to extend the list)
The text was updated successfully, but these errors were encountered: