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
{{ message }}
This repository has been archived by the owner on Jul 15, 2020. It is now read-only.
We can read "We will use 0 for the KES period, since we are creating the first KES key."
The CLI definition for the KES period is : --kes-period NATURAL The start of the KES key validity period.
Therefore, it is unclear in the exercice if --kes-period 0 was selected because it was early days/hours in the blockchain or if it is because it is the first KES used.
Could you clarify if the start of the KES key validity period is actually the slot height we want to new op-cert to be valid at ? May be also in the CLI ?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We can read "We will use 0 for the KES period, since we are creating the first KES key."
The CLI definition for the KES period is :
--kes-period NATURAL The start of the KES key validity period.
Therefore, it is unclear in the exercice if
--kes-period 0
was selected because it was early days/hours in the blockchain or if it is because it is the first KES used.Could you clarify if the start of the KES key validity period is actually the slot height we want to new op-cert to be valid at ? May be also in the CLI ?
The text was updated successfully, but these errors were encountered: