The purpose of this test suite is to demonstrate a path to interoperability for the eddsa-rdfc-2022 and eddsa-jcs-2022 cryptosuites. The technologies explored in this test suite are experimental. This document contains the most recent interoperability report for a [DataIntegrityProof](https://www.w3.org/TR/vc-data-integrity/#dataintegrityproof) using the eddsa-rdfc-2022 and eddsa-jcs-2022 cryptosuites. This report is auto-generated.
Tests passed 248/271 91%
Tests failed 23/271 9%
Failures 23
Tests skipped 0
Total tests 271
These tests were run on
The results of the tests are shown below:
Issuer ⇒
⇓Test Name
|
apicatalog.com | Digital Bazaar | SpruceID | Trinsic | bovine |
---|---|---|---|---|---|
"proof" field MUST exist and MUST be either a single object or an unordered set of objects. |
✓
|
✓
|
✓
|
✓
|
✓
|
if "proof.id" field exists, it MUST be a valid URL. |
✓
|
✓
|
✓
|
✓
|
✓
|
"proof.type" field MUST exist and be a string. |
✓
|
✓
|
✓
|
✓
|
✓
|
"proof.type" field MUST be "DataIntegrityProof" and the associated document MUST include expected contexts. |
✓
|
✓
|
❌
|
❌
|
✓
|
"proof.cryptosuite" field MUST exist and be a string. |
✓
|
✓
|
✓
|
✓
|
✓
|
if "proof.created" field exists, it MUST be a valid XMLSCHEMA-11 dateTimeStamp value. |
✓
|
✓
|
✓
|
✓
|
✓
|
if "proof.expires" field exists, it MUST be a valid XMLSCHEMA-11 dateTimeStamp value. |
✓
|
✓
|
✓
|
✓
|
✓
|
"proof.verificationMethod" field MUST exist and be a valid URL. |
✓
|
✓
|
✓
|
✓
|
✓
|
"proof.proofPurpose" field MUST exist and be a string. |
✓
|
✓
|
✓
|
✓
|
✓
|
"proof.proofValue" field MUST exist and be a string. |
✓
|
✓
|
✓
|
✓
|
✓
|
The contents of the value ("proof.proofValue") MUST be expressed with a header and encoding as described in Section 2.4 Multibase. |
✓
|
✓
|
✓
|
✓
|
✓
|
if "proof.domain" field exists, it MUST be either a string, or an unordered set of strings. |
✓
|
✓
|
✓
|
✓
|
✓
|
if "proof.challenge" field exists, it MUST be a string. |
✓
|
✓
|
✓
|
✓
|
✓
|
if "proof.previousProof" field exists, it MUST be a string. |
✓
|
✓
|
✓
|
✓
|
✓
|
if "proof.nonce" field exists, it MUST be a string. |
✓
|
✓
|
✓
|
✓
|
✓
|
Implementation ⇒
⇓Test Name
|
apicatalog.com | Digital Bazaar | SpruceID | Trinsic | bovine |
---|---|---|---|---|---|
The field "cryptosuite" MUST be "eddsa-rdfc-2022". |
✓
|
✓
|
❌
|
❌
|
✓
|
Dereferencing the "verificationMethod" MUST result in an object containing a type property with the value set to "Multikey". |
✓
|
✓
|
✓
|
✓
|
✓
|
The "proof.proofPurpose" field MUST match the verification relationship expressed by the verification method controller. |
✓
|
✓
|
✓
|
✓
|
✓
|
The "publicKeyMultibase" value of the verification method MUST be 34 bytes in length and start with the base-58-btc prefix (z). |
✓
|
✓
|
✓
|
✓
|
✓
|
["publicKeyMultibase"] MUST consist of a binary value that startswith the two-byte prefix 0xed01 |
✓
|
✓
|
✓
|
✓
|
✓
|
"proofValue" field when decoded to raw bytes, MUST be 64 bytes in length if the associated public key is 32 bytes or 114 bytes in length if the public key is 57 bytes. |
✓
|
✓
|
❌
|
❌
|
✓
|
"proof" MUST verify when using a conformant verifier. |
✓
|
✓
|
✓
|
✓
|
✓
|
Verifier ⇒
⇓Test Name
|
apicatalog.com | Digital Bazaar | SpruceID | Trinsic | bovine |
---|---|---|---|---|---|
If the "proof" field is missing, an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
If the "proof" field is invalid, an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
If the "proof.type" field is missing, an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
If the "proof.type" field is not the string "DataIntegrityProof", an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
If the "proof.verificationMethod" field is missing, an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
If the "proof.verificationMethod" field is invalid, an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
If the "proof.proofPurpose" field is missing, an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
If the "proof.proofPurpose" field is invalid, an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
If the "proof.proofPurpose" value does not match "options.expectedProofPurpose", an error MUST be raised. |
✓
|
❌
|
✓
|
✓
|
✓
|
If the "proof.proofValue" field is missing, an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
If the "proof.proofValue" field is invalid, an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
If the "proof.created" field is invalid, an error MUST be raised. |
✓
|
❌
|
✓
|
✓
|
✓
|
If the "proof.proofValue" field is not multibase-encoded, an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
If the "options.domain" is set and it does not match "proof.domain", an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
If the "options.challenge" is set and it does not match "proof.challenge", an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
Verifier ⇒
⇓Test Name
|
apicatalog.com | Digital Bazaar | SpruceID | Trinsic | bovine |
---|---|---|---|---|---|
verifies a valid eddsa-rdfc-2022 proof. |
✓
|
✓
|
❌
|
❌
|
✓
|
If the "proofValue" field, when decoded to raw bytes, is not 64 bytes in length if the associated public key is 32 bytes in length, or 114 bytes in length if the public key is 57 bytes in length, an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
fails verification when credential is not canonicalized correctly. |
✓
|
✓
|
✓
|
✓
|
✓
|
If the "cryptosuite" field is not the string "eddsa-rdfc-2022", an error MUST be raised. |
✓
|
✓
|
✓
|
✓
|
✓
|
Verifier ⇒
⇓Issuer
|
apicatalog.com | Digital Bazaar | SpruceID | Trinsic | bovine |
---|---|---|---|---|---|
apicatalog.com |
✓
|
❌
|
❌
|
❌
|
✓
|
Digital Bazaar |
✓
|
✓
|
❌
|
❌
|
✓
|
SpruceID |
❌
|
✓
|
✓
|
✓
|
❌
|
Trinsic |
❌
|
✓
|
❌
|
✓
|
❌
|
bovine |
✓
|
❌
|
❌
|
❌
|
✓
|
Issuer ⇒
⇓Test Name
|
bovine |
---|---|
"proof" field MUST exist and MUST be either a single object or an unordered set of objects. |
✓
|
if "proof.id" field exists, it MUST be a valid URL. |
✓
|
"proof.type" field MUST exist and be a string. |
✓
|
"proof.type" field MUST be "DataIntegrityProof" and the associated document MUST include expected contexts. |
✓
|
"proof.cryptosuite" field MUST exist and be a string. |
✓
|
if "proof.created" field exists, it MUST be a valid XMLSCHEMA-11 dateTimeStamp value. |
✓
|
if "proof.expires" field exists, it MUST be a valid XMLSCHEMA-11 dateTimeStamp value. |
✓
|
"proof.verificationMethod" field MUST exist and be a valid URL. |
✓
|
"proof.proofPurpose" field MUST exist and be a string. |
✓
|
"proof.proofValue" field MUST exist and be a string. |
✓
|
The contents of the value ("proof.proofValue") MUST be expressed with a header and encoding as described in Section 2.4 Multibase. |
✓
|
if "proof.domain" field exists, it MUST be either a string, or an unordered set of strings. |
✓
|
if "proof.challenge" field exists, it MUST be a string. |
✓
|
if "proof.previousProof" field exists, it MUST be a string. |
✓
|
if "proof.nonce" field exists, it MUST be a string. |
✓
|
Implementation ⇒
⇓Test Name
|
bovine |
---|---|
The field "cryptosuite" MUST be "eddsa-jcs-2022". |
✓
|
Dereferencing the "verificationMethod" MUST result in an object containing a type property with "Multikey" value. |
✓
|
The "proof.proofPurpose" field MUST match the verification relationship expressed by the verification method controller. |
✓
|
The "publicKeyMultibase" value of the verification method MUST be 34 bytes in length and starts with the base-58-btc prefix (z). |
✓
|
"proofValue" field when decoded to raw bytes, MUST be 64 bytes in length if the associated public key is 32 bytes or 114 bytes in length if the public key is 57 bytes. |
✓
|
"proof" MUST verify when using a conformant verifier. |
✓
|
Verifier ⇒
⇓Test Name
|
bovine |
---|---|
If the "proof" field is missing, an error MUST be raised. |
✓
|
If the "proof" field is invalid, an error MUST be raised. |
✓
|
If the "proof.type" field is missing, an error MUST be raised. |
✓
|
If the "proof.type" field is not the string "DataIntegrityProof", an error MUST be raised. |
✓
|
If the "proof.verificationMethod" field is missing, an error MUST be raised. |
✓
|
If the "proof.verificationMethod" field is invalid, an error MUST be raised. |
✓
|
If the "proof.proofPurpose" field is missing, an error MUST be raised. |
✓
|
If the "proof.proofPurpose" field is invalid, an error MUST be raised. |
✓
|
If the "proof.proofPurpose" value does not match "options.expectedProofPurpose", an error MUST be raised. |
✓
|
If the "proof.proofValue" field is missing, an error MUST be raised. |
✓
|
If the "proof.proofValue" field is invalid, an error MUST be raised. |
✓
|
If the "proof.created" field is invalid, an error MUST be raised. |
✓
|
If the "proof.proofValue" field is not multibase-encoded, an error MUST be raised. |
✓
|
If the "options.domain" is set and it does not match "proof.domain", an error MUST be raised. |
✓
|
If the "options.challenge" is set and it does not match "proof.challenge", an error MUST be raised. |
✓
|
Verifier ⇒
⇓Test Name
|
bovine |
---|---|
verifies a valid eddsa-jcs-2022 proof. |
✓
|
If the "proofValue" field, when decoded to raw bytes, is not 64 bytes in length if the associated public key is 32 bytes in length, or 114 bytes in length if the public key is 57 bytes in length, an error MUST be raised. |
✓
|
fails verification when credential is not canonicalized correctly. |
✓
|
If the "cryptosuite" field is not the string "eddsa-jcs-2022", an error MUST be raised. |
✓
|
Verifier ⇒
⇓Issuer
|
bovine |
---|---|
bovine |
✓
|