Data Integrity BBS Interoperability Report 1.0
Interoperability test suite for BBS Data Integrity cryptosuite.
bbs-2023 (verifiers) VC 2.0
| Test Name | Verifier | |||||
|---|---|---|---|---|---|---|
| Digital Bazaar | Grotto Networking | Netis | Procivis One Core | SpruceID | Trential | |
| If the proofValue string does not start with u (U+0075 LATIN SMALL LETTER U), indicating that it is a multibase-base64url-no-pad-encoded value, an error MUST be raised and SHOULD convey an error type of PROOF_VERIFICATION_ERROR. |
|
|
|
|
|
|
| If proofConfig.type is not set to DataIntegrityProof and/or proofConfig.cryptosuite is not set to bbs-2023, an error MUST be raised and SHOULD convey an error type of PROOF_GENERATION_ERROR. |
|
|
|
|
|
|
| Whenever this algorithm (base proof) encodes strings, it MUST use UTF-8 encoding. |
|
|
|
|
|
|
| The proof options MUST contain a type identifier for the cryptographic suite (type) and MUST contain a cryptosuite identifier (cryptosuite). A proof configuration object is produced as output. |
|
|
|
|
|
|
| CBOR-encode components per [RFC8949] where CBOR tagging MUST NOT be used on any of the components. Append the produced encoded value to proofValue. |
|
|
|
|
|
|
| If proofConfig.created is set and if the value is not a valid [XMLSCHEMA11-2] datetime, an error MUST be raised and SHOULD convey an error type of PROOF_GENERATION_ERROR. |
|
|
|
|
|
|
| Conforming processors MUST produce errors when non-conforming documents are consumed. |
|
|
|
|
|
|
| If the decodedProofValue starts with any other three byte sequence, an error MUST be raised and SHOULD convey an error type of PROOF_VERIFICATION_ERROR. |
|
|
|
|
|
|