Rubrics for Decentralized Identifiers

Rubrics for Decentralized Identifiers

Tuesday 3M

Convener: Joe Andrieu

Notes-taker(s): Daniel Hardman

Tags for the session - technology discussed/ideas considered:

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

Permissioned: governed/operation vs. use/creation

Open source: multiple independent implementations

Open standard

Does the individual create and control?

Can the individual choose how keys are managed?

Does the issuer/controller have a fiduciary responsibility to DID Controller?

Does it support social recovery?

What does a single DID cost? TCO

Is resolution observable?

Are stealth DIDs supported?

Is deactivation publicly documented?

After control is lost can other people deactivate?

Possible confusion between implementations and DID methods

Does it support HD Keys?

Are transactions publicly cryptographically verifiable?

Are DIDs permanent (unremovable--still able to be deactivated but all traces can never vanish)?

Can you get the latest version and older versions? Provable order of versions?

Is the method published?

Is that method independently implementable?

did:web and the .onion TLD (truly decentralized) RFC 6761 and 7686

Is theere a centralized database?

Is its blockchain byzantine fault tolerant?

Does a single party control a majority of the source of truth? (Under what conditions can the DID controller lose capability?)

If you give control away, can you get it back?