> For the complete documentation index, see [llms.txt](https://university.elumicate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.elumicate.com/tokenomics/mining-rewards/mining-reward-distributions.md).
# Mining Reward Distributions
The total amount of tokens distributed for each 1hr epoch is dependent on the network's total number of workers. As the total number of workers increases, the rewards earned for each worker decreases.
#### Tokens distributed by mining are distributed as follows:
Operations/Enhancements/Ecosystem/Infrastructure - 20%
Network participants / Miners - 80%
The Mining Rewards rate begins at 50,000 ELUM yearly tokens per worker and halves every time the total combined network workers triples in size.
Total Network Workers Total Reward/Wrk/yr User Reward/Wkr/yr \
0 - 500 50,000 40,000\
501 - 1,500 25,000 20,000\
1,501 - 4,500 12,500 10,000 \
4,501 - 13,500 6,250 5,000\
13,501 - 40,500 3,125 2,500\
40,501 - 121,500 1562.5 1,250\
121,501 - 364,500 781.25 625\
364,501 - 1,093,500 390.63 312.5\
1,093,501 - 3,280,500 195.31 156.25 \
3,280,501 - 9,841,500 97.66 78.125\
9,841,501 - 29,524,500 48.83 39.0625\
29,524,501 - 88,573,500 24.41 19.53125
\*The total yearly mining reward distribution rate shall never exceed 25% of the total number of remaining tokens in the distribution pool. (For example, if there are 4 Billion remaining tokens in the mining pool, total distribution for each epoch will be calculated using 1 Billion tokens/yr as the maximum total distribution allowed (Total Hourly distribution = 1 Billion / 365 / 24))
---
# 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://university.elumicate.com/tokenomics/mining-rewards/mining-reward-distributions.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.