[Topic] Lessons learned from the Digital Credentials Consortium

[PatStLouis]

I find the MIT DCC pilot and credential infrastructure whitepaper an interesting comparison in the model they have developed.

Some similarities I've observed:

Credentials publishing

• End users fetch a VC from a public URL. In the DCC pilot this was designed to pass a credential to a holder's wallet. In the UNTP design this would likely be for a verifier to verify a Conformity claim made by a DPP issuer. The verifierPlus project can be leveraged for verification purposes as it can verify a VC from a public URL.

Trust anchor/Trust registries

• The UNTP has the term of a trust anchor. The DCC has a simple discoverable concept for trust-registries. These trust registries could theoretically be maintained by trust anchors, providing discoverable trust for reputable issuers and did's.

The DCC system also comes with a functional out of the box mobile wallet application, which could host any amount of publicly hosted credentials. This is great to showcase proof of concepts.

Finally they provide a fully operational dashboard for managing credentials, conformant with the vc-api and chapi.

A fork of this infrastructure tailored to the UNTP could potentially lead to interesting discoveries.

[onthebreeze]

maybe summarise relevant lessons for us here ?

[nissimsan]

@PatStLouis , how do you see us getting to a point we can close this issue successfully?

[PatStLouis]

@nissimsan the only component I see worth including in future discussions is the issuer-registry model which could be useful for verifiers who want to benefit from its feature. I can suggest a PR mentioning this in the implementation guidance as a way to close this issue.