Data Integrity ECDSA Cryptosuites Interoperability Report
Interoperability test suite for ECDSA Data Integrity cryptosuites.
ecdsa-rdfc-2019 (issuers) VC 1.1
| Test Name | Implementation | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| apicatalog.com: P-256 | apicatalog.com: P-384 | Digital Bazaar: P-256 | Digital Bazaar: P-384 | Grotto Networking: P-256 | Procivis One Core: P-256 | SpruceID: P-256 | SpruceID: P-384 | bovine: P-256 | |
| The (proof) type property MUST be DataIntegrityProof. |
|
|
|
|
|
🛑
|
|
|
|
| The cryptosuite property of the proof MUST be ecdsa-rdfc-2019 or ecdsa-jcs-2019. |
|
|
|
|
|
🛑
|
|
|
|
| the signature value (proofValue) MUST be expressed according to section 7 of [RFC4754] (sometimes referred to as the IEEE P1363 format) and encoded according to the specific cryptosuite proof generation algorithm. |
|
|
|
|
|
🛑
|
|
|
|
| The "proof" MUST verify with a conformant verifier. |
❌
|
❌
|
|
|
|
🛑
|
|
|
|
| The "proof.proofPurpose" field MUST match the verification relationship expressed by the verification method controller. |
|
|
|
|
|
🛑
|
|
|
|
| Dereferencing "verificationMethod" MUST result in an object containing a type property with "Multikey" value. |
|
|
|
|
|
🛑
|
|
|
|
| The "publicKeyMultibase" property of the verification method MUST be public key encoded according to MULTICODEC and formatted according to MULTIBASE. |
|
|
|
|
|
🛑
|
|
|
|