> For the complete documentation index, see [llms.txt](https://docs.cheqd.io/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cheqd.io/product/learning-docs/decentralized-id/dids/what-is-a-did-method.md).

# What is a DID method?

A DID method is defined by a DID method specification, which specifies the precise operations by which [DIDs](https://www.w3.org/TR/did-core/#dfn-decentralized-identifiers) and [DID documents](https://www.w3.org/TR/did-core/#dfn-did-documents) are created, resolved, updated, and deactivated.

There are currently **over 100 DID methods**, but only a few which should have working DID Resolvers and DID Registrars.&#x20;

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>cheqd DID Method</strong></mark></td><td>See cheqd's DID Method on our Product documentation.</td><td><a href="https://docs.cheqd.io/identity/architecture/adr-list/adr-001-cheqd-did-method">https://docs.cheqd.io/identity/architecture/adr-list/adr-001-cheqd-did-method</a></td></tr><tr><td><mark style="color:blue;"><strong>DID Spec Registries</strong></mark></td><td>Explore the registered DID Methods on the DID Spec registries.</td><td><a href="https://www.w3.org/TR/did-spec-registries/">https://www.w3.org/TR/did-spec-registries/</a></td></tr><tr><td><mark style="color:blue;"><strong>Universal Registrar</strong></mark></td><td>View the set of DID Methods that have a working DID Registrar.</td><td><a href="https://uniregistrar.io/">https://uniregistrar.io/</a></td></tr><tr><td><mark style="color:blue;"><strong>Universal Resolver</strong></mark></td><td>View the set of DID Methods that have a working DID Resolver.</td><td><a href="https://dev.uniresolver.io/">https://dev.uniresolver.io/</a></td></tr></tbody></table>

## Further reading

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>DID Core Spec</strong></mark></td><td>Dive into the W3C DID Core Recommendation to fully grasp the power of DIDs.</td><td><a href="https://www.w3.org/TR/did-core/">https://www.w3.org/TR/did-core/</a></td></tr><tr><td><mark style="color:blue;"><strong>DID Resolution Spec</strong></mark></td><td>Learn about how DIDs can be resolved or dereferenced from the W3C DID Resolution Spec.</td><td><a href="https://w3c-ccg.github.io/did-resolution/">https://w3c-ccg.github.io/did-resolution/</a></td></tr></tbody></table>


---

# 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.cheqd.io/product/learning-docs/decentralized-id/dids/what-is-a-did-method.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.
