Decentralized Identifiers
Last updated
Last updated
Decentralized IDs
At its core, a DID, is a numeric ID that serves as proof of ownership. It’s akin to your digital ID card. DIDs contain a public key, and to prove ownership, you’ll require the corresponding private key.
A standout feature of DIDs is their lack of dependence on a central registration authority. Instead, you register them on a public or private blockchain. This unique approach guarantees the authenticity and ownership of your DIDs.
DID Example
DIDs adhere to a specific syntax and are generated following DID method specifications, which can vary based on the blockchain or distributed network in use.
Here’s an example of DID syntax:
In this example:
did: indicates that it’s a Decentralized Identifier. example is the method or DID scheme used (similar to a domain name). 123abc456def is the unique identifier portion of the DID, which can vary based on the method or scheme used.
Different DID methods may have variations in syntax, but they all adhere to the basic structure of did: followed by the method and unique identifier.
The Four Pillars of DIDs
DIDs possess four crucial properties that make them stand out:
Persistence: DIDs are permanent; once assigned, they never change, unlike mutable phone numbers or email addresses.
Resolvability: DIDs are resolvable, meaning you can retrieve metadata from a shared ledger by looking them up.
Cryptographic Verification: DIDs offer cryptographic verification, ensuring robust security and trustworthiness.
Decentralization: DIDs are decentralized, escaping the control of a single entity, which enhances security and reliability.
What are DID Method Specs?
DID method specifications are very important. They regulate how DIDs are read and written within specific blockchains or distributed networks.
Each method spec covers:
The syntax of the method-specific identifier.
Method-specific elements of a DID document.
Cryptographic operations for DIDs and DID documents in the system.
Unveiling the DID Document
DID Documents
A DID isn’t just a number; it’s part of a broader concept known as a DID document. This document is essentially a standard JSON-LD file with additional rules for linking data.
The DID Document provides metadata for authenticating a DID.
It includes:
DID: Self-description of the document.
Public Keys: A set of public keys for verification.
Auth Methods: A set of authentication methods for protocols.
Service Endpoints: A set of endpoints for interactions.
Timestamp: Records for audit history.
Signature: Ensures integrity.
DKMS
DKMS addresses the challenge of managing user DIDs (Decentralized Identifiers) and private keys securely. It’s based on the DID specification and aims to provide an open standard for user wallets.
The goal is to create a standardized approach to wallet development, ensuring user security, privacy, and avoiding vendor lock-in concerns.
