-
Notifications
You must be signed in to change notification settings - Fork 3
CIP-0137 | Fix protocol specifications #15
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
Conversation
In order to provide a simpler message invalidation mechanism.
The cold verification key is not strictly necessary in the operational certificate. This allows to simplify the Haskell DMQ implementation and reuse the existing KES signature verification of the Ouroboros consensus implementation.
a529d6d to
c0fcdfd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
7760ff5 to
f918f02
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should specify how the operational certificate is encoded.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @jpraynaud, it looks good to me.
|
Closing this PR which has been moved to cardano-foundation#1085 |
This PR includes updates of the CIP-0137:
blockNumberfieldttlexpiresAtfield (word32)coldVerificationKeyfield (word32)expiresAtfieldMsgServerDonemessage has been removed from then2c local message notificationmini-protocol(latest version of updated document)