> For the complete documentation index, see [llms.txt](https://wiki.blocklords.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.blocklords.com/economy/currencies/usdlrds/token-distribution.md).

# Token Distribution

<figure><img src="/files/i1sXGrpB9XD0xrqWafsg" alt=""><figcaption></figcaption></figure>

**In-Game Utility and Long-Term Value**:\
\
The $LRDS token in BLOCKLORDS is designed to offer true in-game utility within its ecosystem. Here's an overview of its utility, supply, and distribution:

* **Utility**: The $LRDS token is not just a digital asset; it plays a significant role in the game, providing tangible in-game benefits and functionalities.
* **Value Accrual**: The tokenomics of $LRDS are structured to reward active contributors and participants in the network, encouraging long-term engagement in the ecosystem.
* [**Vesting Cycles and Release Plan**:](/economy/currencies/usdlrds/tokenomics.md) To ensure stability and sustainability, $LRDS tokens have long vesting cycles and are subject to a 10-year release plan. This approach aligns with the goal of rewarding consistent and long-term contributors to the network.

**Supply of $LRDS**:

* **Maximum Total Supply**: The maximum total supply of $LRDS tokens will be capped at 100,000,000.&#x20;


---

# 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://wiki.blocklords.com/economy/currencies/usdlrds/token-distribution.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.