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
Nodes could publish their current block height in their state, i.e. {url}/state, and nodes can query each other for block heights, and they'd know whether each other are behind or not
Could query it from RPC endpoint too, and parse it from the json response. Then the node does not need to query other nodes, it knows how delayed it is and can publish is_stable based on comparison of its height v.s. rpc endpoint
ppca
linked a pull request
Oct 30, 2024
that will
close
this issue
If a node starts at a very early block height and has been syncing but is still way behind, is_stable will still show true
The text was updated successfully, but these errors were encountered: