DIDs
This page explains technical aspects of DIDs, if you want to know more about Decentralized Identifiers you can go to the "What is SSI?" page.
Dernière mise à jour
This page explains technical aspects of DIDs, if you want to know more about Decentralized Identifiers you can go to the "What is SSI?" page.
Dernière mise à jour
Decentralized identifiers (DIDs) are a type of globally unique identifier that enables an entity to be identified in a manner that is verifiable, persistent, and does not require the use of a centralized registry. DIDs enable a new model of decentralized digital identity that is often referred to as self-sovereign identity or decentralized identity.
A DID and its corresponding DID document by nature do not contain personal data.
A decentralized identifier resolves to a DID document, a set of data describing the DID subject, including mechanisms, such as cryptographic public keys, that the DID subject or a DID delegate can use to authenticate itself and prove its association with the DID
The DID Scheme refers to the structured format of a decentralized identifier. It initiates with the prefix "did:". Every DID method specification establishes a distinct DID method scheme tailored for its respective DID method.
A DID method outlines the approach for implementers to actualize the functionalities detailed in this specification. Typically, DID methods are linked with a specific verifiable data registry. To ensure compatibility among various implementations of the same DID method, new DID methods are articulated in their respective specifications.
In essence, the connection between this specification and a DID method specification mirrors the relationship between the IETF's generic URI specification [RFC3986] and a specific URI scheme [IANA-URI-SCHEMES], like the http scheme [RFC7230]. Apart from delineating a specific DID scheme, a DID method specification also elucidates the procedures for generating, resolving, updating, and deactivating DIDs and DID documents using a particular verifiable data registry type. Furthermore, it comprehensively documents all implementation considerations regarding DIDs, along with Security and Privacy Considerations.
If a DID document includes a service designed for authenticating or authorizing the DID subject, it becomes the obligation of the service endpoint provider, the subject of the DID, or the requesting party to adhere to the authentication protocols mandated by that service endpoint.
did:web
Dynamic
The first benefit of did:web lies in its reliance on the well-established and extensively utilized web infrastructure and its standards. This simplifies the adoption and implementation process significantly for companies.
