mirror of
https://github.com/oxen-io/oxen-observer.git
synced 2023-12-14 09:22:54 +01:00
3feca6d743
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.
1.7 KiB
1.7 KiB
{%for sn in (active_sns | sort(attribute='last_uptime_proof,service_node_pubkey'))[:limit_active]%}
{%include 'include/sn_kcf.html'%}
{%endfor%}
{%if limit_active and active_sns|length > limit_active%}
{%endif%}
| Public Key | Contributors | Operator Fee (%) | Staking Requirement | Active Since Height | Last Uptime Proof | Expiry Date UTC (Estimated) |
| {{sn.staking_requirement | oxen(tag=false, fixed=true)}} | {{sn.state_height}} | {{sn.last_uptime_proof | from_timestamp | ago if sn.last_uptime_proof > 0 else "Not Received"}} | {%if sn.requested_unlock_height%} 🔓 {{((sn.requested_unlock_height - info.height) * 120 + server.datetime.timestamp()) | from_timestamp | format_datetime('short')}} ({{((sn.requested_unlock_height - info.height) * 120) | reltime}}) {%else%} Staking Infinitely {%endif%} | |||
| + {{active_sns|length - limit_active}} more ↪ | ||||||