You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Did you face issues with that after updating the go http client? Same issue happens with the latest checkpointz version which also expects the Eth-Consensus-Version header to be set (#6124).
We are not following the spec here, this will be addressed by API rework done in #6080
Well, I was hitting this error, then I upgraded the attestantio http client so I could toggle the EnforceJson switch which sets Accept to exclude ssz, and then I hit the Invalid string length one.
I switched my holesky test environment to nimbus for now. Only 3300 validators were down while i migrated 😆
I switched my holesky test environment to nimbus for now. Only 3300 validators were down while i migrated 😆
Sorry to hear that, we have a fix ready for it and might already include that in a hotfix release. Our current API design is lacking a bit, with #6080 there will be a bunch of improvements and we will be able to verify that all headers required by spec are set correctly.
Describe the bug
Expected behavior
Eth-Consensus-Version
header should be set, as required by https://ethereum.github.io/beacon-APIs/#/Debug/getStateV2Steps to reproduce
No response
Additional context
No response
Operating system
Linux
Lodestar version or commit hash
v1.12.0
The text was updated successfully, but these errors were encountered: