Add timestamp to HostSettings
HostExternalSettings includes a
RevisionNumber field, which allows you to order all of the settings you have seen from a particular host. But it would be far more useful to have a precise timestamp instead. This would allow you to graph the
HostExternalSettings over time, which would reveal various interesting patterns.
Of course, you can already do this locally by recording the time when you initiate the scan. But there's no way to securely share these results with others, because the timestamp won't be signed by the host. If the timestamp were covered by the signature, then centralized services (e.g. siastats) could prove that they weren't manipulating the time that the settings were recorded.
I guess there is one complication here -- what should you do if the host's reported timestamp is significantly different from your local clock? I think the only option is to treat the settings as invalid if the timestamp is more than some delta away from
time.Now, like we do with blocks.