JSAssassin
commented
1 year ago @tmarkovski Some of the verifier and interop tests are failing for Trinsic. The problem seems to be that the value for proof.verificationMethod in the Trinsic issued VC contains a distorted hash fragment. This is what it looks like:
{
"@context": [
"https://www.w3.org/2018/credentials/v1",
"https://w3id.org/security/data-integrity/v1"
],
"id": "urn:uuid:a97efacb-b22b-41a6-b6a6-09a653d1b477",
"type": [
"VerifiableCredential"
],
"issuer": "https://trinsic.id",
"issuanceDate": "2020-03-16T22:37:26.544Z",
"credentialSubject": {
"id": "did:key:z6MktKwz7Ge1Yxzr4JHavN33wiwa8y81QdcMRLXQsrH9T53b"
},
"proof": {
"type": "DataIntegrityProof",
"created": "2023-08-11T20:58:28.6438842Z",
"proofPurpose": "assertionMethod",
"verificationMethod": "did:key:z6MkqbpLSbqnY1pxVyhBCDYcFsv4ZgGgqP32kzNrf5deWVPU#0��A\u001a�]\u0012�u��`\u0003�8k���\ri��\t6L��P�",
"cryptosuite": "eddsa-2022",
"proofValue": "z2ocoVJhukv2UpAUHzHxH9jGPxtBBWoJgtw2cESssF5vzzHsvo8N9PvGRrfvhsDi9X9fvcUeDadHbF3CaqnEDFuFx"
}
}Also Trinsic verifier is failing to verify the following VC issued by SpruceID, not sure what the problem is though. This is what we're sending to the verifier:
{
"verifiableCredential": {
"@context": [
"https://www.w3.org/2018/credentials/v1"
],
"id": "urn:uuid:1f276d06-af06-431d-b021-d79d898c0293",
"type": [
"VerifiableCredential"
],
"credentialSubject": {
"id": "did:key:z6MktKwz7Ge1Yxzr4JHavN33wiwa8y81QdcMRLXQsrH9T53b"
},
"issuer": "did:key:z6MkgND5U5Kedizov5nxeh2ZCVUTDRSmAfbNqPhzCq8b72Ra",
"issuanceDate": "2020-03-16T22:37:26.544Z",
"proof": {
"@context": [
"https://w3id.org/security/data-integrity/v1"
],
"type": "DataIntegrityProof",
"proofPurpose": "assertionMethod",
"proofValue": "z2oC1eweiTgVYvY6tyeEFUQD6bFfYqLdBN55Rqnn6VUcHLCMjDrzBGtYfn4aSMixTABTHqk2XRgZP6YZxcSMGeB8K",
"verificationMethod": "did:key:z6MkgND5U5Kedizov5nxeh2ZCVUTDRSmAfbNqPhzCq8b72Ra#z6MkgND5U5Kedizov5nxeh2ZCVUTDRSmAfbNqPhzCq8b72Ra",
"created": "2023-08-11T21:21:49.896Z",
"cryptosuite": "eddsa-2022"
}
},
"options": {
"checks": [
"proof"
]
}
}
tmarkovski
msporny
aljones15
Adds implementation reference for Trinsic
Test Suite Results
``` eddsa-2022 (create) Data Integrity (issuer) Trinsic ✓ "proof" field MUST exist at top-level of data object. ✓ 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". ✓ "proof.cryptosuite" field MUST exist and be a string. ✓ "proof.created" field MUST exist and be a valid XMLSCHEMA-11 datetime 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 "proof.proofValue" field MUST be a multibase-encoded base58-btc encoded value. ✓ if "proof.domain" field exists, it MUST be a string. ✓ if "proof.challenge" field exists, it MUST be a string. ✓ if "proof.previousProof" field exists, it MUST be a string. eddsa-2022 (issuer) Trinsic ✓ The field "cryptosuite" MUST be `eddsa-2022` ✓ "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. eddsa-2022 (verify) Data Integrity (verifier) Trinsic ✓ If the "proof" field is missing, a "MALFORMED_PROOF_ERROR" MUST be raised. ✓ If the "proof" field is invalid, a "MALFORMED_PROOF_ERROR" MUST be raised. ✓ If the "proof.type" field is missing, a "MALFORMED_PROOF_ERROR" MUST be raised. ✓ If the "proof.type" field is not the string "DataIntegrityProof", an "INVALID_PROOF_CONFIGURATION" error MUST be raised. ✓ If the "proof.verificationMethod" field is missing, a "MALFORMED_PROOF_ERROR" MUST be raised. ✓ If the "proof.verificationMethod" field is invalid, a "MALFORMED_PROOF_ERROR" MUST be raised. ✓ If the "proof.proofPurpose" field is missing, a "MALFORMED_PROOF_ERROR" MUST be raised. ✓ If the "proof.proofPurpose" field is invalid, a "MALFORMED_PROOF_ERROR" MUST be raised. ✓ If the "proof.proofPurpose" value does not match "options.expectedProofPurpose", a "MISMATCHED_PROOF_PURPOSE_ERROR" MUST be raised. ✓ If the "proof.proofValue" field is missing, a "MALFORMED_PROOF_ERROR" MUST be raised. ✓ If the "proof.proofValue" field is invalid, a "MALFORMED_PROOF_ERROR" MUST be raised. ✓ If the "proof.created" field is missing, a "MALFORMED_PROOF_ERROR" MUST be raised. ✓ If the "proof.created" field is invalid, a "MALFORMED_PROOF_ERROR" MUST be raised. ✓ If the "proof.proofValue" field is not a multibase-encoded base58-btc value, an "INVALID_PROOF_VALUE" error MUST be raised. ✓ If the "options.domain" is set and it does not match "proof.domain", an "INVALID_DOMAIN_ERROR" MUST be raised. ✓ If the "options.challenge" is set and it does not match "proof.challenge", an "INVALID_CHALLENGE_ERROR" MUST be raised. eddsa-2022 cryptosuite (verifier) Trinsic ✓ MUST verify a valid VC with an eddsa-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 INVALID_PROOF_LENGTH error MUST be returned. ✓ If a canonicalization algorithm other than URDNA2015 is used, a INVALID_PROOF_VALUE error MUST be returned. ✓ If a canonicalization data hashing other than algorithm SHA-2-256 is used, a INVALID_PROOF_VALUE error MUST be returned. ✓ If the "cryptosuite" field is not the string "eddsa-2022", an INVALID_PROOF_CONFIGURATION error MUST be returned. eddsa-2022 (interop) ✓ Trinsic should verify Trinsic Tests passed 38/38 100% Tests failed 0/38 0% Failures 0 Tests skipped 0 Total tests 38 ```