# Decentralized Identifiers (DIDs) and SSI

**Decentralized Identifiers (DIDs) and Their Role in SSI**

#### **What Are Decentralized Identifiers (DIDs)?**

DIDs are **unique, self-controlled identifiers** that allow individuals and organizations to **authenticate and verify themselves across digital platforms** without relying on centralized identity providers (such as Facebook, Google, or government agencies). Unlike traditional email-based or username-password authentication, **DIDs are cryptographically secure and interoperable across different identity systems**.

#### **How DIDs Work in Self-Sovereign Identity (SSI)**

* A **user generates a DID** through their digital wallet.
* The DID is **linked to a cryptographic key pair**.
* Users can **sign identity proofs** using their **private key** and share them with verifiers without revealing their private data.
* DIDs can be resolved and verified on **decentralized networks**, such as **Hyperledger, Ethereum, Cardano, and EBSI**.

#### **Privacy Control & Interoperability**

* **DIDs support Zero-Knowledge Proofs (ZKPs)** for privacy-preserving verification.
* **They enable user-controlled, self-sovereign identity solutions**.
* **Interoperable across blockchain networks and digital identity ecosystems.**

🔗 **Sources:**

* W3C Decentralized Identifiers Standard: <https://www.w3.org/TR/did-core/>
* Hyperledger Identity Solutions: <https://www.hyperledger.org/>

***

###


---

# Agent Instructions: 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:

```
GET https://docs.fairway.global/learn/introduction-to-digital-identity-and-verifiable-credentials/decentralized-identifiers-dids-and-ssi.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
