Implementation

Questions to answer

Holder implementation

  • Where to store the holders credential data? - Device OR cloud agent?

  • How should the wallet deal with credential templates - custom inputs, pre-defined values, replacement values.

    • If all initial credentials are batch issued then this could potentially be delayed

Issuer implementation

  • How to store the DIDs temporarily before they are batch issued - MVP Just locally in a spreadsheet / list or instead commit more time for a database setup

  • How does the holder receive the signed issued credential without DIDComm? - MVP just to host it on a site that the holder can be directed to for importing into their wallet?

  • If issuers create credential templates how are they stored - On a website with a file link if that suffices?

  • For participation credentials think of a way to make it easier for hosts to prove participants stayed during event

  • Data structures for participation and completion credentials

Verifier implementation

  • How website will verify the holder owns the DID associated to the credential still not clear. It is already clear on how to verify whether a credential is signed by the issuer public DID just not whether the holder owns the DID used for the credential.

PreviousRequirementsNextResources

Last updated