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

Use v3 beacon API to get block #1314

Open
y0sher opened this issue Feb 13, 2024 · 0 comments
Open

Use v3 beacon API to get block #1314

y0sher opened this issue Feb 13, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@y0sher
Copy link
Contributor

y0sher commented Feb 13, 2024

Description

Currently there are two different beacon routes to get blocks, under v2 for unblinded blocks - [/eth/v2/validator/blocks/{slot}](https://ethereum.github.io/beacon-APIs/#/Validator/produceBlockV2)
and under v1 for blinded blocks - /eth/v1/validator/blinded_blocks/{slot}.

This results in code where we have to request from different API endpoints and do different handling based on the builderProposal settings in the SSV node, also blinded blocks might be turned off in the beacon node and the route won't work, even more, the MEV relay/boost might still fail to create a blinded block and we'll need to request again a non-blinded block as a fallback.

Solution

/eth/v3/validator/blocks/{slot} was introduce to return a valid blinded or non-blinded block in all cases, without need for special handling. change our proposals code to use this route.

@y0sher y0sher added the enhancement New feature or request label Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant