> For the complete documentation index, see [llms.txt](https://fatexdao.gitbook.io/fatexdao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fatexdao.gitbook.io/fatexdao/fatexdao-dapps-and-tokens/fatexfi-faq/tokenomics-epoch-0.md).
# Tokenomics: Epoch 0
**The FATE reward schedule is designed to fix the issues most emissions/reward schedule schemes have: i.e. decreasing over time, major halving-events/cliffs etc**. ([Green Paper section](/fatexdao/the-green-paper-a-declaration-of-the-freedom-from-centralized-illiquidity/the-green-paper/dlt-crypto-theory/unstable-uses-of-tokens.md))
### FATE Rewards Schedules increase proportionally over time.
### FATE supply must be controlled to be less than demand.
* It is likely that we will need to adjust the rewards schedule 1-2 weeks after the launch.
* **One of the unique characteristics of our model is that we can adjust it with DAO approval.**
The below reward schedule is a very exact estimate (since we are allowing a limited pre-swap option for any member that holds Harmony issued FATE and fills out the application to request approval for participation in providing liquidity for the launch the current supply cannot be determined exactly)
#### To encourage long-term membership and manage supply release impact, which will have additional pressure caused by the release of FATE allocated to Harmony members: the reward rate of the emissions schedule is conservative and is the product of supply impact analysis.
***It is impossible to predict until after the launch of FATExFi.io what the demand will be - however, that will be a central focus in any CapEx available in the first fiscal quarter (3 months) after launch.*** \
\
***Treasury will have the option to adjust the rewards as needed to help keep the supply of FATE higher than the demand.***
We do not want to adjust the reward schedule regularly but will be able to increase/decrease the multiple between x0 - x4.
#### Any locked FATE rewards earned by members will be vested and distributed in future epochs.
**PLEASE CLICK ON THE IMAGE BELOW TO ENLARGE IT.** \
\
For record-keeping purposes you can scroll below it is pasted below as well.
### **EPOCH 0 Rewards Schedule:**
* **Designed for stability, conservation and flexibility:**
* Increases steadily at a rate of 0-2% (this does not show locked rewards and circulating supply) - the current rate is 0.8% per week.
* It does include the expected supply for launch.
* **Again: it will likely need to be adjusted. Conservative, stable APRs in the high double-digits for the first epoch is the ideal.**
### ORIGINAL REWARDS SCHEDULE:
Note: We use time-stamps instead of block-rate to ensure fees and rewards are calculated properly.
### MID-EPOCH CHANGES:
Rewards are dynamic to ensure DAO capital integrity, fair allocation, and sustainable use of member voting power rights via the DAO gov. token: FATE.
Per DAO approved proposal - the leadership team has the authorization to adjust the block rate rewards multiple between the x0-4.
The weekly increasing multiple will remain the same regardless of any changes until DAO votes differently.\
\
See the next page for a record of any reward schedule changes during Epoch 0.
---
# 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:
```
GET https://fatexdao.gitbook.io/fatexdao/fatexdao-dapps-and-tokens/fatexfi-faq/tokenomics-epoch-0.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.