Data Integrity ECDSA Cryptosuites Interoperability Report
Interoperability test suite for ECDSA Data Integrity cryptosuites.
Algorithms - Base Proof Transformation (ecdsa-sd-2023)
| Test Name | ||||||
|---|---|---|---|---|---|---|
| apicatalog.com | Digital Bazaar | Grotto Networking | MakoLab | SpruceID | Trential | |
| The transformation options MUST contain a type identifier for the cryptographic suite (type), a cryptosuite identifier (cryptosuite), and a verification method (verificationMethod). |
|
|
|
|
|
|
| The transformation options MUST contain an array of mandatory JSON pointers (mandatoryPointers) and MAY contain additional options, such as a JSON-LD document loader. |
|
|
|
|
|
|
| Whenever this algorithm encodes strings, it MUST use UTF-8 encoding. |
|
|
|
|
|
|
| Per the recommendations of [RFC2104], the HMAC key MUST be the same length as the digest size; for SHA-256, this is 256 bits or 32 bytes. |
|
|
|
|
|
|