> 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/official-addresses.md).

# Official Addresses

This page lists the official on-chain addresses associated with DXR and the DEXRise platform. Each address corresponds to one of the [supply allocations](/dexrise-documentation/dxr-token/tokenomics.md#distribution).

## Token contract

|                        |                   |
| ---------------------- | ----------------- |
| **DXR token contract** | *To be announced* |

{% hint style="warning" %}
The DXR token contract address will be announced through DEXRise's official channels and published on this page. **Always verify the contract address against this page and official announcements before interacting with any DXR contract** — fake contracts and impersonated addresses are a common scam vector.
{% endhint %}

## Official wallet addresses

| # | Address role               | Address                                      |
| - | -------------------------- | -------------------------------------------- |
| 1 | **Trading liquidity pool** | `0xa1ca9a7c96f407af32c82d6b9bc848b3c2d97911` |
| 2 | **Staking**                | `0x1e81ecb83ddd8995d7fb4de6fed0f2ab8a09a22b` |
| 3 | **Presale**                | `0x0b3febf0a815a6c260d045a75ba7eda5b6482873` |
| 4 | **Airdrop**                | `0x0455EFF0b6df9726d065E46F2Cf27FF1a560FcB8` |
| 5 | **Team wallet**            | `0xF3b164648B6F4a6ae4a202270Da0772FD9b3Ad46` |

## What each address holds

Each address maps directly to a [tokenomics allocation](/dexrise-documentation/dxr-token/tokenomics.md#distribution):

| Address role               | Allocation it holds                                                       |
| -------------------------- | ------------------------------------------------------------------------- |
| **Trading liquidity pool** | 50% of supply — 500,000,000 DXR backing DXR trading pairs                 |
| **Staking**                | 30% of supply — 300,000,000 DXR funding the staking program over 10 years |
| **Presale**                | 10% of supply — 100,000,000 DXR allocated to the presale event            |
| **Airdrop**                | 5% of supply — 50,000,000 DXR for community airdrop events                |
| **Team wallet**            | 5% of supply — 50,000,000 DXR allocated to the team                       |

## Safety checklist

* ✅ Verify every address against **this page** before any interaction.
* ✅ Follow announcements only through the [official DEXRise channels](/dexrise-documentation/support/contact.md).
* ❌ Never trust addresses sent to you in private messages, even if they appear official.
* ❌ DEXRise will never ask for your private keys or seed phrase.


---

# 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/official-addresses.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.