> For the complete documentation index, see [llms.txt](https://whitepaper.cryptofights.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.cryptofights.com/fyx-token/reward-schedule.md).
# Reward Schedule
Tokens distributed over time
Formula
* f(w) is the number of tokens distributed in week w;
* μ is the mean of the distribution, set at 130 week, this will coincide with the peek around year 3;
* $$σ$$is the standard deviation, set at 52 weeks, this is the spread or dispersion of the distribution. A smaller σ would give us a steeper peak;
* w is the week number
### Balanced Rewards for Early Adopters
It's important to note that while the distribution curve starts off low initially, early adopters have the opportunity to stake fragments ahead of time. This strategy enables them to capitalize early on tokens that will be issued in years 2 and 3, potentially simplifying the process of accumulating tokens.
---
# 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://whitepaper.cryptofights.com/fyx-token/reward-schedule.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.