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
Currently the /info endpoint reports the current epoch and the timestamp of the next rotation along with the ZK public keys. It would also be nice to report the epoch rotation interval directly, instead of clients having to estimate from multiple samples. Or make assumptions.
I originally suggested we unpack the public key blob and annotate each epoch with timestamps, since that gives the server maximum flexibility. But that's an API revision, so maybe just adding an epochDuration key is good enough.
The text was updated successfully, but these errors were encountered:
Currently the
/info
endpoint reports the current epoch and the timestamp of the next rotation along with the ZK public keys. It would also be nice to report the epoch rotation interval directly, instead of clients having to estimate from multiple samples. Or make assumptions.I originally suggested we unpack the public key blob and annotate each epoch with timestamps, since that gives the server maximum flexibility. But that's an API revision, so maybe just adding an
epochDuration
key is good enough.The text was updated successfully, but these errors were encountered: