3E/ How to THINK and DID’s

From IIW

How to think about DIDs


Session Convener: Joe Andrieu

Notes-taker(s): Antonio Antonino

Tags / links to resources / technology discussed, related to this session:


Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:


Three different domains with three different trust models:


Verifiable Data Registry

Sovereign System State Management, e.g. Bitcoin, Ethereum, Mastercard. They do not care about anyone else, and do not want to depend on other systems for any of their functions


DIDs

Use resolver to communicate with the verifiable data registries Let applications access the state on the verifiable data registry


Applications

Use DIDs as identifier method

The wallet is the point of connection between all 3 domains.

Q: Where does the trust get established?

1st trust element is in the resolver to return the ACTUAL document for a DID

  • The app should run its own resolver, and the resolver should be public and inspectable

2nd trust element is what DID methods to trust in which application domain

  • The DID method Rubik can be used as an evaluation matrix depending on the use case requirements
Retrieved from "https://iiw.identitycommons.net/index.php?title=3E/_How_to_THINK_and_DID’s&oldid=24207"