Sort active nodes by last uptime proof. #10
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.
Since HF19, there is no longer a concept of a per node reward height, so
we need a new sort criterion for active nodes. I believe the most
interesting sort is that by most recent uptime proof.
At the top of the list will appear nodes whose proof is overdue
(i.e. > 1:00:00 ago). This should never be more than a few seconds, so
one can see at a glance any nodes that are ripe for being moved to the
Inactive/Decommissioned Service Nodes section the next time they are
tested by the network. This also makes the list much more dynamic to
watch.
Since the Last Reward Height column is now redundant, we can replace it
with something more interesting, such as the Active Since Height.