> 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/staking-event.md).

# DXR Staking Event

The DXR staking program is one of the largest allocations in the [DXR tokenomics](/dexrise-documentation/dxr-token/tokenomics.md#distribution): **300,000,000 DXR — 30% of the total supply — dedicated entirely to staking rewards**, released across a **10-year schedule**. The program opens **during the presale itself**, with its first round running at **100% APR**.

## Program parameters

| Parameter                    | Value                                             |
| ---------------------------- | ------------------------------------------------- |
| **Total staking allocation** | 300,000,000 DXR — 30% of max supply               |
| **Release schedule**         | Distributed across **10 years**                   |
| **First year release**       | 100,000,000 DXR                                   |
| **Subsequent rounds**        | Gradually decreasing in the rounds that follow    |
| **First round (Round 1)**    | November 3, 2026 → November 3, 2027 — a full year |
| **Round 1 APR**              | **100%**                                          |

## Round 1 — 100% APR

The first staking round runs for a **full year**, from **November 3, 2026 to November 3, 2027**, at an APR of **100%** — the strongest rate of the program:

* The first-year release of **100 million DXR** makes Round 1 the largest single-year reward pool of the entire 10-year schedule.
* After Round 1, subsequent rounds **decrease gradually**.
* Rewards follow the standard [APR mechanics](/dexrise-documentation/staking/apr-mechanics.md): annualized over 365 full days, calculated as simple interest on the deposited amount.

## Staking during the presale

The staking program is **fully functional while the** [**DXR Presale Event**](/dexrise-documentation/dxr-token/presale-event.md) **is running**:

* You can participate in staking **during the presale period** — with full functionality from day one.
* The contract type is [**Flexible**](/dexrise-documentation/staking/staking-types.md#flexible-staking) — you can **withdraw your deposit at any time**, with no restrictions.
* **Claim your rewards at any time** — or re-deposit them to keep growing your position while the presale runs.

This combination is what makes the presale especially attractive: participants can buy DXR at the fixed presale price and immediately put it to work at 100% APR. See [DXR Presale Event](/dexrise-documentation/dxr-token/presale-event.md#why-participate-in-the-presale) for the full participation picture.

## Where to go next

* New to DEXRise staking? Start with [Staking on DEXRise](/dexrise-documentation/staking/overview.md).
* Understand exactly how your rewards accrue: [APR Mechanics](/dexrise-documentation/staking/apr-mechanics.md).
* Compare contract types: [Staking Types](/dexrise-documentation/staking/staking-types.md).


---

# 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/staking-event.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.