Troy Ronda

13. Verifier response must adhere to proof verification format for credential and presentation ✕ credential (187ms) ✓ presentation (667ms) ``` expect(received).toBe(expected) // Object.is equality Expected: 200 Received: 400 395 |...

Note - we should run all tests even if one of the thirdparty fails. (i.e., don't fail early).

See endpoints: https://github.com/w3c-ccg/vc-examples/commit/1ceb890182d7dab3e5e6b0cf02d00db2f70bc5b1

See https://github.com/w3c-ccg/vc-examples/issues/22

Support both specs: - https://transmute-industries.github.io/vc-http-api/ - https://w3c-ccg.github.io/vc-verifier-http-api/ - https://w3c-ccg.github.io/vc-issuer-http-api/ Endpoints: - /verifier/credentials == /verify/credentials - /verifier/presentations == /verify/presentations - /issue/credentials == /credentials/issueCredential

currently we support `checks` in the response. add `warnings` and `errors` to the response.

Element ordering in output

1

Note: our implementation appears to re-order the JSON-LD credential elements with lexical ordering. This seems like a different behaviour than other implementations.

couchdb namespacing

1

- allow for couchdb prefix - allow for separation of data by issuer.