-
Notifications
You must be signed in to change notification settings - Fork 338
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
CIP-0108 | Ensure "CIP-0008" is in capital letters #951
Conversation
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.
Can't think of any technical things that would fail because of this schema change but please @Ryun1 @Crypto2099 @perturbing @gitmachtl confirm if you can.
Great spot @palas |
@@ -34,7 +34,7 @@ Blake2b-256 hash digest of canonicalized body: `68d6fe27087457acf0164e65414238c4 | |||
### Motion of No-Confidence | |||
|
|||
Example metadata document file: [no-confidence.jsonld](./examples/no-confidence.jsonld). | |||
Blake2b-256 of the file content (to go onchain): `6c27e5bd0d7cdec7ddb30956be0b5eac892a8330e00689692d18f3815a71bf9f` | |||
Blake2b-256 of the file content (to go onchain): `87ba5c10c89484c52265b50d669b4acf116aaeb8a6fa35fbf06e5ec67cda9270` |
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.
I pushed this update, because of the change introduced in no-confidence example changed the hash digest
Spoke to a couple implementors, this change is all good to go. |
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.
Thanks @palas 💪
Why do we use the public key for CIP-0008 method here and not the Cose_Key? Is there a written definition on the parameters used for this signature? Because CIP0008 allows for different ones. I guess we're going with the
one? If so, that should be specified in CIP108 too imo. @Ryun1 ? |
@gitmachtl |
@Ryun1 yes adding CIP8 is totally fine! i am refering that there should be more detailed information in the CIP about which parameters should be used with CIP8. and normally we have a COSE_Sign1 signature cbor-structure/hex and a corresponding COSE_Key cbor-structure/hex, not only the publickey. for verification we need the parameters set as above, otherwise it would fail. but that information should be in the description of the CIPs imo. or we switch to use the COSE_Key in the publickey field of the signatures? |
@Ryun1 @palas the example file |
This PR addresses the issue #949, by ensuring
CIP-0008
is used in capital letters in thewitnessAlgorithm
field of thewitness
type in CIP-0108, updating the "no-confidence" example and the test vector Markdown documentation.Fixes #949.