Notes

Notes

In this Masterclass, we delve into Decentralized Identifiers (DIDs) and the selection of DID methods, highlighting their importance in the context of digital identity. As a summary, the main points covered in the class include:

  1. Definition and characteristics of DIDs: A DID is a unique identifier that the user creates and controls throughout its lifecycle, without the intervention of third parties. This contrasts with traditional identifiers such as document numbers or driver’s licenses, which are issued and controlled by institutions.
  2. Associated cryptographic material: DIDs are associated with cryptographic material, such as a pair of public and private keys, allowing the holder to demonstrate control over the DID. This is fundamental for authentication and digital signing, enabling complex signing schemes and the designation of authorized signatories.
  3. DID documents: Each DID is associated with a DID document, which is a standard file containing the DID controller’s public key, other possibly associated keys, and relevant metadata. This document is crucial for resolving the DID to verifiable information.
  4. Storage of the DID document: The standards do not specify a single method for storing DID documents, allowing for a variety of implementations from databases to blockchains. This leads to the DID methods, which are specific implementations that follow the W3C standard but vary in functionality and infrastructure requirements.
  5. Choice of DID methods: When choosing a DID method, several aspects should be considered, including the DID subject (person, organization, or thing), the applicable legal and regulatory framework, the required functionality, and the balance between technical complexity and infrastructure requirements. For example, personal data protection regulations may influence the choice of DID method for individuals.
  6. Evolution and diversity of DID methods: There are over 2000 DID methods in development, reflecting a diversity of approaches and solutions tailored to different needs and contexts. This underscores the importance of carefully evaluating the specific requirements of an application before selecting a DID method. We will explore more in the following section.