-
Notifications
You must be signed in to change notification settings - Fork 283
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
mark v1 block publishing deprecated #8520
Comments
Hi @rolfyone could I get this issue assigned :) |
Hey - That's correct, the two classes are If we search for the endpoint (eg. Often they don't have a |
Thanks for your help @rolfyone We just searched for instances of those classes previously. I just did the text search for those endpoints. They don't seem to be used anywhere else other than |
ethereum/beacon-APIs#467
In line with the beacon-apis PR, we should go ahead and mark our v1 block endpoints as deprecated.
This basically involves
/eth/v1/beacon/blinded_blocks
/eth/v1/beacon/blocks
Maybe a text search just to make sure we're not using the POST anywhere else but its unlikely. This is a pretty good first issue, it should show up in our integration tests as deprecated when they run and also need that change made (updating reference files appropriately)
The text was updated successfully, but these errors were encountered: