feat: add latest_block_height and is_stable to /state; only stable nodes can partake in signature generation #710
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds in the
latest_block_height
andis_stable
values toStateView
so a node can keep track whether a connection is stable or not. A node will only consider another node to be able to generate a signature if and only if it is stable, such as when it is caught up with indexed blocks. This only affects signature generation, so things like triples, presginatures, resharing are still fine even if a node is not stable.This fixes #680 partially but only handles the honest node portion.