-
Notifications
You must be signed in to change notification settings - Fork 46
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
Proposal: The WG needs to agree to an interoperability profile that covers the suites #130
Comments
I'm just going to write this down so we don't lose track of it:
|
@tplooker is there another pairing friendly curve that we might use as a backup for bls12381 ? |
So to answer your question @msporny we could have BnBbsSignature2021 that would be functionally equivalent. |
+1 to having an alternative, no idea if BN should be the alternative (others that are qualified should make that decision). It's good to see CFRG working on this -- we may want to engage them more formally in the next couple of months, noting that we predict some sort of W3C WG that would like to have their input on a primary and backup pairing-friendly curve that wouldn't be susceptible to the same sorts of attacks. It might also be useful to chase down Barreto, Naehrig, Lynn, and Scott to see where their current thinking is wrt. "what would you choose today for the primary and backup?" |
Agreed this is important, but more appropriate for https://github.com/w3c-ccg/vc-api-test-suite ? Recommend we close this issue. |
Agreed. I'll also note that we have other test suites that we're working on that do not require an interop profile for all test suites... for example, the "soon to be moved to the CCG" VC API modular test suites don't test the actual signature, they just check to make sure the API exists and returns something that's well-formed:
... while the Ed25519 test suite uses the same API endpoints, but then checks the actual digital signature format: This approach allows us to test the shape of the VC API without requiring any particular cryptosuite... and then we also have cryptosuite test suites that do require very specific output (proper digital signatures). |
The text was updated successfully, but these errors were encountered: