-
-
Notifications
You must be signed in to change notification settings - Fork 306
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
BlockV3 API does not return Eth-Consensus-Version
#6202
Comments
Ok so I think I worked out that Lodestar doesn't support the SSZ endpoints. But even the JSON v3 endpoint does not return this header. |
Thanks for pointing this out. As far as I know, Just curious why you specifically mention |
Yeah, I'm reworking the blockV3 HTTP client in LH (and consequently blockdreamer) and getting it to read the consensus header to work out how to to parse the response. I'm now re-reworking it to get it to read the JSON values instead/as well. This will hopefully enable blockdreamer to start working with Lodestar immediately, which may detect other issues. I also found a Lighthouse bug in the process (we weren't returning the metadata fields in the JSON response, just the headers). |
yeah, we are not setting proper headers right now and ssz responses are also not supported for all required apis. We are working on a refactoring that will address both those issues #6080. Recently added a fix to add consensus version header to get state and block apis (#6152, it's not pretty), could add a quick hotfix to do the same for produceBlockV3 if it that helps out. |
Describe the bug
Lodestar doesn't return the mandatory
Eth-Consensus-Version
header for/eth/v3/validator/blocks/{slot}
. I'm using the SSZ version of the endpoint.Expected behavior
Lodestar should include all mandatory headers.
Steps to reproduce
I'm running blockdreamer against Lodestar with
v3 = true
.Additional context
No response
Operating system
Linux
Lodestar version or commit hash
v1.13.0-rc.0
The text was updated successfully, but these errors were encountered: