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

# Tokenomics

DXR has a **fixed total supply of 1,000,000,000 DXR**. This maximum supply is **not inflatable** — it cannot be increased, so the token's supply is capped from day one.

## Distribution

The max supply is allocated across five purposes:

| Allocation            | Share | Amount          | Purpose                                                                                                                          |
| --------------------- | ----- | --------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Trading liquidity** | 50%   | 500,000,000 DXR | Backs DXR trading pairs on the platform, starting with the [DXR/USDT launch](/dexrise-documentation/dxr-token/trading-launch.md) |
| **Staking**           | 30%   | 300,000,000 DXR | Rewards for the [DXR staking program](/dexrise-documentation/dxr-token/staking-event.md), released across 10 years               |
| **Presale**           | 10%   | 100,000,000 DXR | Sold in the [DXR Presale Event](/dexrise-documentation/dxr-token/presale-event.md) at a fixed price                              |
| **Airdrops**          | 5%    | 50,000,000 DXR  | Funds [airdrop events](/dexrise-documentation/airdrop/overview.md) for the community                                             |
| **Team**              | 5%    | 50,000,000 DXR  | Allocated to the DEXRise team                                                                                                    |

## Reading the allocation

* **Half of the entire supply goes to trading liquidity** — the largest single allocation. This anchors the token's trading depth on the platform: the [DXR/USDT launch pool](/dexrise-documentation/dxr-token/trading-launch.md) alone starts with 500 million DXR.
* **Nearly a third funds staking rewards** — the 300 million DXR staking allocation is the engine of the [staking program](/dexrise-documentation/dxr-token/staking-event.md), deliberately released over a full 10-year schedule so that staking remains rewarding long after launch. The first year releases 100 million DXR, beginning with a 100% APR round.
* **The presale allocation is capped at 10%** — exactly 100 million DXR, sold at a fixed 0.001 USDT in the [presale event](/dexrise-documentation/dxr-token/presale-event.md), raising a target of 100,000 USDT.
* **The remainder is split evenly** — 5% for community [airdrop events](/dexrise-documentation/airdrop/overview.md) and 5% for the team.

{% hint style="info" %}
The on-chain addresses that hold each allocation are published and verifiable in [Official Addresses](/dexrise-documentation/dxr-token/official-addresses.md).
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dexrise.gitbook.io/dexrise-documentation/dxr-token/tokenomics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.