> For the complete documentation index, see [llms.txt](https://dechat.gitbook.io/dechat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dechat.gitbook.io/dechat/dechat-token/token-economics/staking-for-rewards.md).
# Staking for rewards
Income method: Return of principal and interest/interest first
Revenue currency: $DECHAT
Financial product limit: 50,000$DECHAT
Number of days for financial management: 365 days
Maximum personal purchase quantity: 1,000$DECHAT
Annual rate of return: 3000%
Annual income = principal \* annual yield / 365 \* number of staking days
Dechat will release multiple financial products. The annual yield of financial products will be different depending on different pledge cycles and products. The early rate of return is very impressive, each financial product has a limit, and there is a quota limit for each user.This part of the output will be allocated to “chat to earn” and later credit card profits.
---
# 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://dechat.gitbook.io/dechat/dechat-token/token-economics/staking-for-rewards.md?ask=&goal=
```
`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.