Unexpected amount of results of state_getKeysPaged JSON RPC request (staking.validators)
#2946
Comments
mergify bot
pushed a commit
that referenced
this issue
Oct 31, 2022
Fix #2946 The behavior of `prefix_proof` is currently buggy. When a node isn't found in the proof that the remote sent us, we simply discard it instead of adding it to the list of keys to query at the next iteration. The consequence is that `state_getKeysPaged` was wrong most the time. In order to fix this, I had to reorganize the entire function. There's still an issue because we're asking for too much data, which leads the remote to shutdown the connection, so queries still occasionally fail. But this other issue is not the fault of the `prefix_proof` module, and this PR is only about fixing `prefix_proof`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to request the
validatorslist from both light client and polkadotJS the responses' length is different (light client: 2, while polkadotJS; 996).In order to replicate the following method can be called (unfortunately it is truncated in the logs):
PolkadotJS Apps:
Light Client Apps:
Logs from the replication are attached: state_getKeysPaged.txt
Initiated by this issue on Polkadot Staking Dashboard. Based on it, this seems to impact eraStakers, validators, bondedPools and poolMembers entries requests.
The text was updated successfully, but these errors were encountered: