> For the complete documentation index, see [llms.txt](https://delegates.iotex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://delegates.iotex.io/addendum/profits-projections.md).
# Profits Projections
#### Average rewards (per epoch)
| % of Network Votes | Block Rewards (1) | IoTeX Foundation Bonus (2) | Epoch Rewards (3) | Est. total IOTX/year | | |
|---|
| 5.0% | 160 IOTX | 80 IOTX (suspended) | 937.50 IOTX | 10,314,900 IOTX | | null |
| 2.0% | 160 IOTX | 80 IOTX (suspended) | 375,00 IOTX | 5,387,400 IOTX | | null |
| 0.5% | N/A (4) | N/A (4) | 93.75 IOTX | 821,250 IOTX | | null |
*(1) Calculated on average, taking into account that for every epoch 2/3 of the consensus, delegates get randomly selected to produce blocks.*
*(2) Extra 80 IOTX/epoch provided by the IoTeX foundation to the top 36 delegates. Voted on a yearly basis by the community on* [*gov.iotex.io*](https://gov.iotex.io)
*(3) The share of the epoch bonus equals the delegate share of the network votes. For example, a delegate with 2% of the total votes in the network will receive 2% of the epoch reward every epoch.*
*(4) Delegates with less than 1% of network votes will likely not be a consensus delegate*
#### Yearly projections
| % of Network Votes | Est. total IOTX/year | Block Rewards | IoTeX Foundation Bonus | Epoch Rewards | | |
|---|
| 5.0% | 10,314,900 IOTX | 160 IOTX | 80 IOTX | 937.50 IOTX | | null |
| 2.0% | 5,387,400 IOTX | 160 IOTX | 80 IOTX | 375,00 IOTX | | null |
| 0.5% | 821,250 IOTX | N/A(*) | N/A(*) | 93.75 IOTX | | null |
#### Profit calculator tools
You can use profit calculator tools provided by our delegates to estimate your annual profit:
{% hint style="warning" %}
Estimates from these tools are based on assumptions - please do your own analysis.
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://delegates.iotex.io/addendum/profits-projections.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.