-
Notifications
You must be signed in to change notification settings - Fork 27
Add NTN and Disk CDDLs #1422
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
base: js/newer-ledger
Are you sure you want to change the base?
Add NTN and Disk CDDLs #1422
Conversation
Very nice! See cardano-scaling/cardano-blueprint#25 for an issue that aims to use these to create an api reference. |
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.
Looks like a lot of work, but it's great that we finally have CDDLs for all these things. Also this module system looks quite good!
ouroboros-consensus-cardano/cddl/node-to-client/localstatequery/query.cddl
Outdated
Show resolved
Hide resolved
ouroboros-consensus-cardano/cddl/node-to-client/localstatequery/consensus/getInterpreter.cddl
Outdated
Show resolved
Hide resolved
ouroboros-consensus-cardano/cddl/node-to-client/localstatequery/consensus/getSystemStart.cddl
Outdated
Show resolved
Hide resolved
aafadd5
to
690e912
Compare
4ede539
to
0e37093
Compare
This PR is blocked on IntersectMBO/cardano-ledger#5056 so that we can integrate a newer ledger that contains: |
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.
Should we document somewhere where the CBOR specs for the ledger live, how we obtain them, and what is the testing strategy we now adopt to test CDDL conformance?
@@ -0,0 +1,25 @@ | |||
header |
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.
This a comment that applies to each file: do we want to state where the corresponding Haskell data definition lives? And conversely, when defining a CBOR instance, would it make sense to define where the CDDL a CBOR instance conforms to is located?
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.
do we want to state where the corresponding Haskell data definition lives?
I don't think so. Eventually these files will go to the blueprint so there is no need there for a Haskell link.
And conversely, when defining a CBOR instance, would it make sense to define where the CDDL a CBOR instance conforms to is located?
Perhaps?
ouroboros-consensus-cardano/src/unstable-cardano-testlib/Test/Consensus/Cardano/Generators.hs
Show resolved
Hide resolved
ouroboros-consensus-cardano/test/cardano-test/Test/Consensus/Cardano/GenCDDLs.hs
Show resolved
Hide resolved
ouroboros-consensus-cardano/test/cardano-test/Test/Consensus/Cardano/GenCDDLs.hs
Outdated
Show resolved
Hide resolved
ouroboros-consensus-cardano/test/cardano-test/Test/Consensus/Cardano/GenCDDLs.hs
Show resolved
Hide resolved
ouroboros-consensus/src/unstable-consensus-testlib/Test/Util/Serialisation/CDDL.hs
Show resolved
Hide resolved
e381346
to
a45003a
Compare
Description
Add CDDL definitions for types that Consensus emits.