Decentralized Identifier (DID)
Let's explore Decentralized Identifiers (DIDs), a unique identifier system introduced by the World Wide Web Consortium (W3C). This document will serve as your compass, helping you navigate through the fundamental concepts of DIDs, the architecture and components of zk DIDs, their storage and retrieval methods, and the encryption and decryption techniques involved. It's a good idea to familiarize yourself with this guide before you dive into the VC Specification.
Core Concept
DIDs serve as a foundation for creating and managing decentralized digital identities. These identifiers can represent a wide range of entities, be it individuals, organizations, or machines. zCloak, in accordance with W3C's guidelines, has developed its own set of DIDs known as zk DID.
DID Architecture Overview
Let's take a closer look at the architecture of a DID. It's made up of several key components:
- DIDs and DID URLs: A DID is a type of Uniform Resource Identifier (URI) that consists of three components: the 'did:' scheme, a method identifier, and a unique identifier that is specific to the DID method. DIDs can be resolved to their corresponding DID documents, which contain the information associated with the DID.
- DID Subjects/Holders/Identifier: The entity that a DID represents is referred to as the DID subject or holder. This entity can also assume the role of the DID controller, which is the entity that has the authority to make changes to the DID document.
- DID Controllers: A DID controller is an entity that has the authority to make changes to a DID document. The process for authorizing these changes is determined by the specific DID method being used.
- DID Documents: DID documents are data records that contain information associated with a DID. They typically include verification methods, such as cryptographic public keys, and services that are relevant to interactions with the DID subject.
The picture below shows how these parts connect with each other. As we go on, we'll look closer at each of these parts and how they work together. So, let's get started!
- Click to see narrative description
To delve deeper into our DID specifications, please explore the following resources:
DID Method
DID Document
DID Keys
DID Storage and Query
Best Practice