Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Missing key 'higestBlock' in RPC responce system_syncState. #5860

Closed
base1217 opened this issue Aug 4, 2022 · 2 comments · Fixed by paritytech/substrate#11979
Closed

Missing key 'higestBlock' in RPC responce system_syncState. #5860

base1217 opened this issue Aug 4, 2022 · 2 comments · Fixed by paritytech/substrate#11979

Comments

@base1217
Copy link

base1217 commented Aug 4, 2022

Hello,

There is not highestBlock key in RPC response 'system_syncState' anymore.

Is it okay?
@base1217 base1217 changed the title Key 'higestBlock' missed in RPC method system_syncState. Missing key 'higestBlock' in RPC responce system_syncState. Aug 4, 2022
@stakeworld
Copy link
Contributor

Maybe related to #5771 ?

@bkchr bkchr mentioned this issue Aug 4, 2022
Merged
@bkchr
Copy link
Member

bkchr commented Aug 4, 2022

The missing key is a valid return. It just means that there is no block with a higher number than the best block of your local node in the network.

I created a pr to make this always return the highest block, which now defaults to your local node best block: paritytech/substrate#11979

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

system_syncState: Always return highest block paritytech/substrate
3 participants
@bkchr @base1217 @stakeworld