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
Use relative KES periods for evolution and signing
Previously KES keys would be evolved to the _current_ KES period, and
would sign at that period. But this is incorrect; we should be caring
about the number of evolutions since the first period, defined by the
operational certificate.
As such, we now sign with the _relative_ KES period (e.g. the number of
evolutions), and evolve the keys accordingly.
0 commit comments