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
I’ve encountered a potential inconsistency with how Lodestar handles validator_balances requests.
According to the beacon-API specification, the id parameter can be a validator index represented as a string (e.g., "22710") or a hex-encoded public key. However, when making the following request:
curl -X GET http://localhost:4000/eth/v1/beacon/states/head/validator_balances?id=22710
The differential testing results show that only lodestar return error
Hello Lodestar team,
I’ve encountered a potential inconsistency with how Lodestar handles validator_balances requests.
According to the beacon-API specification, the id parameter can be a validator index represented as a string (e.g., "22710") or a hex-encoded public key. However, when making the following request:
The differential testing results show that only lodestar return error
Schema:
Related code implementation in lodestar:
lodestar/packages/beacon-node/src/api/impl/beacon/state/index.ts
Lines 203 to 212 in 33ca095
Thanks for your time!
The text was updated successfully, but these errors were encountered: