> For the complete documentation index, see [llms.txt](https://docs.dexlab.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dexlab.space/products/staking.md).

# Staking

{% hint style="danger" %}
**DXL staking is closed.** The pages in this section describe a program that ran from January 2022 and are kept as a record. Reward distributions ended on 14 November 2022, and the staking interface and the wallet that signed for it have both been retired.

None of the benefits described below are available any more. If you still have DXL staked, it is safe and it is still yours. See [unstaking.md](/products/staking/unstaking.md).
{% endhint %}

![](https://4258708058-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MLgGUCteWrA9nM5I3ts-887967055%2Fuploads%2FPS100fWAy6XpoiTCoi5C%2F1_mSMfJW5fKZS5VVQCwkM02w.png?alt=media\&token=8d6e8fb2-5ddb-4ef2-9c32-76b6f39f24d0)

## **Greeting! Dexlab Community!**

As previously announced, on January 10th our Staking program will go live on Dexlab. We are delighted to clarify the details of our Staking program. Here is an easy-to-understand, step-by-step guide for everyone!

First and foremost, as we always set our mind to be a community-driven project, we have prepared various benefits for staking pool users. The details are as follows:

* <mark style="background-color:red;">**APY during staking**</mark>

-APY will differ every month. Rewards will be paid in relation to the fees incurred in Dexlab.

-Staking rewards will be paid weekly. (If you cancel staking before compensation, compensation will not be paid.)

-Staking is carried seasonally, and benefits for each season may vary also.

* <mark style="background-color:red;">**Guaranteed airdrop event allocation (100%)**</mark>

-There will be different types of airdrops, from even airdrop amounts or varying amounts according to the staking quantity of the user.

* <mark style="background-color:red;">**Dexlab IDO Ranking Pool Participation Ticket**</mark>

-If you are in the ranking according to the staked quantity, you will get a guaranteed part in IDO sales depending on your ranking. It follows the existing ranking system. If you do not stake, you will not be included in the ranking.

* <mark style="background-color:red;">**Increase the chance of Dexlab IDO sale Standard pool**</mark>

-If you did not stake DXL but participated in a standard pool, one ticket will be given. However, if you stake your DXL, you will get 1 ticket per 100 DXL. The winning rate increases with the number of tickets you have.

* <mark style="background-color:red;">**Pre-test privilege**</mark>

-Dexlab will draw a pre-test privilege lottery ticket for new services in the future. You never know what’s to come.

The original announcement is archived here: <https://medium.com/dexlab-official/dexlab-staking-a-to-z-b431f2bfe344>

Looking for the Staking tutorial? 👉🏻 Click 'Next.'


---

# 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://docs.dexlab.space/products/staking.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.
