# DIDs in a nutshell

In our context, Digital identifiers are an arbitrage way to leverage an already created profile to get secure access to a third-party application. Digital identities involve cryptography and are stored on a ledger.

{% hint style="info" %}
**Example:** If you have a GitHub, Facebook or Google profile you are able to create an account with GitBook. You do not need to re-create a new profile nor do you need to create a new password. Creating or re-using passwords always comes with a new security risk. 
{% endhint %}

As the example already shows the keepers (and owners) of your Digital Identity are usually the leading tech platforms. Which increasingly raises the concerns of privacy advocates, as these platforms are able to connect the dots of your logins.

[Decentralized identifiers](https://www.w3.org/TR/2022/REC-did-core-20220719/#dfn-decentralized-identifiers) (DIDs) are trying to fix this by making the enduser the keepers and owners of their digital profiles by using decentralized ledger technology (DLT). 

{% hint style="info" %}
**Hint:** No private data will be ever stored on a public blockchain.
{% endhint %}

{% content-ref url="/pages/FiCfOBEbhrTte1dIWn5M" %}
[Decentralized Identifiers (DID)](/open-directory-for-all/fundamentals/scientific-foundation/tasks.md)
{% endcontent-ref %}

{% content-ref url="/pages/1mCr0BDube2IlBCZKKg3" %}
[W3C SOFTWARE AND DOCUMENT NOTICE AND LICENSE](/open-directory-for-all/licenses/w3c-software-and-document-notice-and-license.md)
{% endcontent-ref %}


---

# 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://ssi-did-directory.gitbook.io/open-directory-for-all/fundamentals/did-in-a-nutshell.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.