Technology Solutions

Decentralized Identity Management Approach

Decentralized identity is a way of managing your online identity that doesn't rely on centralized third parties such as social media platforms or government ID systems. Decentralized identity systems enable users to completely own and control their data.
A digital identity is the body of information about an individual, organization, or electronic device that exists online. Data that form a digital identity include:
  • Login information
  • Browsing history
  • Purchase history
The 3 main parties involved in a decentralized identity system are:
  1. 1.
    Issuer: An organization that has the authority to issue Verifiable Credentials such as a health and safety organization issuing a training credential or an online course platform issuing completion certificates
  2. 2.
    Holder: User who owns the credential and stores it in their digital wallet
  3. 3.
    Verifier: The party validating or authenticating the credential like an employer needing to check a candidate’s educational credentials or staff at a store that needs to verify that a customer is at least 18 to buy alcohol
A decentralized identity system has an issuer, holder, and verifier

Self-Sovereign Identity

Self-sovereign identity is made up of Verifiable Credentials, blockchain, and decentralized identifiers
Decentralized identity is often used interchangeably with the term Self-Sovereign Identity (SSI). Self-Sovereign Identity is an approach to digital identity that gives individuals control of their identities.
The three pillars of Self-Sovereign Identity are:
  • Blockchain: A decentralized digital database that is shared among computers in the blockchain network that records information in a way that makes it very difficult to change, hack, or cheat the system.
  • Verifiable Credentials: Digital cryptographically-secure versions that people can present to parties that need them for verification.
  • Decentralized Identifiers (DIDs): Verifiable identifiers created by the user, owned by the user, and independent of any organization. DIDs contain no personally identifiable information.


A blockchain is a decentralized digital record of transactions that is shared with every computer in the blockchain network. This chain of blocks is stored on every computer in the network, so everyone has a copy of the transaction history.
High security
What makes the blockchain so secure is that even if someone were to hack into one computer and view the blockchain, they wouldn't be able to read it or make any changes without the encryption key.
Each block contains a "hash" (like a unique digital fingerprint) of the previous block. So if anyone tries to tamper with a block, that would change its hash meaning that the block would no longer match up with the next block in the chain. As soon as someone tries to tamper with the blockchain, everyone else in the network would know immediately.
How blockchain is used in decentralized identity systems
With Dock, we only store DIDs on the blockchain needed for a verifier to validate the authenticity of a credential like an issuer’s cryptographic key (digital signature) that matches the one on the credential. The data on credentials are stored on the user's mobile devices only and the information is securely encrypted.

Decentralized Identifiers (DIDs)

Decentralized identifiers (DIDs) are globally unique identifiers made up of a string of letters and numbers that can be stored on the blockchain and doesn’t rely on a central authority to verify their authenticity. DIDs are used to give people and organizations a unique online identity that can be used to access services and conduct transactions. Unlike traditional identifiers, such as Social Security numbers or email addresses, DIDs cannot be centrally controlled or revoked.
Example of how someone can sign in with decentralized identifiers (DIDs)
Here’s an example of a Dock DID:
Example of a decentralized identifier (DID) created from Dock
Key features of DIDs:
  • Created, owned, and managed completely by the user (individual or organization) without depending on any third party
  • Allow the owner to securely prove control over them
  • Don’t contain any personal data or wallet information
  • Easily created with the Dock Wallet and Dock Certs platform
Users can create as many DIDs as they want for different purposes. For example, someone can use:
  • DID 1: To purchase things online
  • DID 2: To hold professional credentials like training certificates and their university degree
  • DID 3: To log into online gaming sites
  • DID 4: To log into trading and investment services
People can create as many decentralized identifiers (DIDs) as they want
Every DID that is created comes with a private and public key pair and DIDs can have multiple pairs. A key acts like a password and is also a string of letters and numbers that aren’t identifiable. A public key is visible to everyone on the network, while a private key is known only to the individual. This system ensures that only the intended recipient can read the data, even if it is intercepted by someone else.
Here is an example of an employer’s DID and its private and public keys:
Every decentralized identifier will come with a private and public key pair. DIDs can have multiple pairs.
Every decentralized identifier will come with a private and public key pair. DIDs can have multiple pairs.
Private key
It’s a piece of code that allows you to access data associated with the public key. You can think of a private key like a password where if someone has your private key, they can access all your valuable information. That’s why the private key should never be shared with anyone.
Public key
You can compare a public key like an email address where anyone can use it to send you information but only you can access the data.
The Role of DIDs In the Decentralized Identity System
  • Issuers use DIDs to create credentials that are tamper-proof and verifiable
  • Holders use their DIDs to securely store and manage their credentials
  • Verifiers use DIDs to verify the authenticity of credentials without relying on a third party
Whenever an organization issues someone a Verifiable Credential, their public DID is attached to that credential. Because the public DID (and issuer’s public key) is stored on the blockchain, whenever a party wants to verify the authenticity of the credentials, they can check the DID on the blockchain to see if it was really the issuer’s private key that signed the Credential.

Verifiable Credentials

Nursing license issued as a Verifiable Credential
Examples of documents that can be issued as Verifiable Credentials include university degrees, professional certifications, driver’s licenses, and identity documents.
Digital credentials that conform to the Verifiable Credentials Data Model 1.0 developed by the World Wide Web Consortium (W3C) can be referred to as Verifiable Credentials. This standard is a “specification [that] provides a standard way to express credentials on the Web in a way that is cryptographically secure, privacy-respecting, and machine-verifiable.”
Signing in with a Decentralized Identifier (DID) on the Dock Wallet
Here is an example of how a holder, issuer, and verifier interact together:
Example of how a Verifiable Credential works with an issuer, holder, and verifier
A government can issue a passport as a Verifiable Credential for the holder to securely store in their digital identity wallet.
Benefits of Verifiable Credentials:
  • Instantly verifiable within seconds compared to days, weeks, and months with conventional verification processes
  • Verifying organizations don’t need to waste time, money, and resources contacting the issuer
  • Data is tamper-resistant with the use of cryptography
  • Holder has full control of their data
  • Providers privacy for users
  • No personal or sensitive data is stored on the blockchain
How Verifiable Credentials technology works