Skip to content
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

Remove deprecated produce block apis #466

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

nflaig
Copy link
Collaborator

@nflaig nflaig commented Aug 19, 2024

This removes previously deprecated produce blocks apis

  • GET /eth/v2/validator/blocks/{slot}
  • GET /eth/v1/validator/blinded_blocks/{slot}

Those were replaced / consolidated by GET /eth/v3/validator/blocks/{slot} during Capella and part of spec release for Deneb.

Implementations should be able to safely remove the apis after Electra fork.

rkapka
rkapka previously approved these changes Aug 19, 2024
@rolfyone
Copy link
Collaborator

I do agree with the sentiment, but we probably want to hold off merging this until electra or they'll no longer be listed...

I know at least teku is still calling v2 in several deneb releases, so if other clients are not publishing those endpoints that could be a potential problem.

I guess equally if we said 2.5.0 is what is expected in deneb, this would be able to be merged... We don't really have a great way of articulating that maybe?

@nflaig
Copy link
Collaborator Author

nflaig commented Aug 21, 2024

Removal of apis is a bit tricky and I would generally recommend implementations only remove those in their next release after the Electra fork as this is the only way to ensure everyone has updated their clients and no longer use v2.

As per merging this, we can hold off on it but I would say it depends on when we wanna cut the next stable release. If it is not before Electra it might be fine to merge it already, the apis being removed from dev explorer shouldn't be an issue?

In case of Lodestar, since we run api spec tests, we can only remove them after the spec has removed them, so it would be fine to wait until we cut the Electra release.

Maybe we cut a 2.6.0 release soon to get more visibility on new apis and before Electra we cut a 3.0.0 and remove the apis, which we might wanna consider as a breaking change.

@tersec
Copy link

tersec commented Sep 24, 2024

In favor of removing.

@rolfyone
Copy link
Collaborator

In favor of removing.

we can remove these, but not until after electra, so in an f* fork. They've been marked deprecated i believe for this release, but we can't just delete them until we've done the electra beacon-api release tag etc.

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.

4 participants