-
Notifications
You must be signed in to change notification settings - Fork 784
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
Implement expected_withdrawals HTTP API #4029
Comments
When can this api implement? |
@marshalys Maybe for v4.1.0, what do you want it for? If you're doing builder stuff I'd reccommend the SSE |
OK, thank you! I'll see it. |
i'd like to pick this one up if its still relevant |
Thanks @eserilev, that would be great! |
## Issue Addressed [#4029](#4029) ## Proposed Changes implement expected_withdrawals HTTP API per the spec ethereum/beacon-APIs#304 ## Additional Info
## Issue Addressed [#4029](#4029) ## Proposed Changes implement expected_withdrawals HTTP API per the spec ethereum/beacon-APIs#304 ## Additional Info
## Issue Addressed [#4029](#4029) ## Proposed Changes implement expected_withdrawals HTTP API per the spec ethereum/beacon-APIs#304 ## Additional Info
[sigp#4029](sigp#4029) implement expected_withdrawals HTTP API per the spec ethereum/beacon-APIs#304
[sigp#4029](sigp#4029) implement expected_withdrawals HTTP API per the spec ethereum/beacon-APIs#304
Description
There's a new HTTP API on the block for builders: ethereum/beacon-APIs#301
I think @realbigsean might already have an implementation to support
mock-relay
, so we should probably base the standard impl on that. I'm happy to go hunting for the branch and porting it across next week, as Sean is on leave.The text was updated successfully, but these errors were encountered: