Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

operational certificate start #450

Closed
JaredCorduan opened this issue May 6, 2019 · 0 comments · Fixed by #457
Closed

operational certificate start #450

JaredCorduan opened this issue May 6, 2019 · 0 comments · Fixed by #457

Comments

@JaredCorduan
Copy link
Contributor

We need to decide how the operational certificate start times are determined, and adjust the spec accordingly.

In particular, is this a value specified in the certificate, or is it determined by the first slot that it is used for a valid block? If we want the certificate to store this value, then we need to add another mapping for this information to the ledger state.

In the design doc, it says that the start time is an epoch number. Should it instead be a KES period (which we can think of as ~1 day)?

Make sure to update the BHEAD rule. It currently has a predicate "hk |-> s_0 \in stpools". This is incorrect either way, as it is the start of the pool registration certificate.

nc6 pushed a commit that referenced this issue May 19, 2020
450: Hotfix for missing git reference in iohk-monitoring-framework r=ruhatch a=ruhatch



Co-authored-by: Rupert Horlick <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant