> For the complete documentation index, see [llms.txt](https://docs.tuum.tech/identify/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tuum.tech/identify/basics/decentralized-identifiers.md).

# Decentralized Identifiers

## Overview

Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs) are important components of decentralized identity systems. They provide a way for individuals and organizations to establish and prove their identity without relying on centralized authorities or intermediaries.

## Decentralized Identifiers(DIDs)

DIDs are a new type of identifier that enables verifiable, decentralized digital identity. They are globally unique, persistent, and cryptographically verifiable. DIDs are typically associated with a DID Document, which contains the public keys, authentication methods, and service endpoints needed to interact securely with the entity the DID represents.

## Verifiable Credentials(VCs)

VCs are digital attestations of identity attributes that can be cryptographically signed by an issuer, such as a government or an organization, and securely shared with other entities. They enable the holder of the credential to prove their identity or qualifications without exposing sensitive information. VCs are based on the World Wide Web Consortium's (W3C) Verifiable Credentials Data Model standard.

## Use cases

1. Digital Identity: DIDs and VCs can be used to establish a digital identity for individuals, organizations, or IoT devices, allowing them to interact securely and privately online.
2. Access Control: DIDs and VCs can be used for authentication and authorization, enabling secure access to online services and resources.
3. Credential Verification: VCs can be used to verify qualifications, professional certifications, or memberships in various organizations, reducing fraud and improving trust.
4. KYC/AML Compliance: Financial institutions and other regulated entities can use VCs to streamline customer onboarding and compliance with anti-money laundering (AML) and know-your-customer (KYC) regulations.
5. Healthcare: Patients can use VCs to securely share their medical records with healthcare providers, ensuring data privacy and improving the quality of care.
6. Supply Chain Management: DIDs and VCs can be used to track and verify the provenance of goods, ensuring authenticity and reducing counterfeiting.

## Platforms and Implementations

1. **Sovrin Network**: The Sovrin Network is a decentralized, global public utility for self-sovereign identity based on the Hyperledger Indy platform. It allows individuals and organizations to create and manage DIDs and VCs.
2. **Microsoft's ION**: Microsoft's Identity Overlay Network (ION) is a decentralized identity system built on top of the Bitcoin blockchain. It uses the Sidetree protocol to enable scalable DID management and interaction.
3. **Veres One**: Veres One is a decentralized ledger for DIDs that is based on the W3C DID standard. It aims to provide a simple, secure, and privacy-preserving way to create and manage digital identifiers.

Decentralized Identifiers and Verifiable Credentials are essential components of a decentralized digital identity ecosystem, providing increased security, privacy, and control for users. As the technology matures and more platforms integrate DIDs and VCs, we can expect to see a growing number of use cases and applications across various industries.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tuum.tech/identify/basics/decentralized-identifiers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
