> For the complete documentation index, see [llms.txt](https://whitepaper.didit.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.didit.me/didit-components/didit-token.md).

# Didit Token

The **Didit token** is an essential component of the Didit ecosystem, as it promotes network growth through incentivizing user participation. Knowing that Didit Protocol's solutions can be integrated by any service provider, expanding the Didit ID network is crucial for unlocking the full potential of the ecosystem.

To address the cold start problem and stimulate sustainable growth, **Didit will utilize token distribution** as the primary method for sharing value creation with network participants. By distributing tokens, Didit aligns the incentives of users and service providers, promoting active engagement and network expansion.

This approach ensures a robust and dynamic growth trajectory until network effects naturally take hold, creating a **self-sustaining ecosystem**.

{% hint style="info" %}
The Didit token has yet to be released. Additional information about its distribution mechanisms and dynamics will be revealed soon.
{% endhint %}


---

# 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://whitepaper.didit.me/didit-components/didit-token.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.