> For the complete documentation index, see [llms.txt](https://docs.energyweb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.energyweb.org/ewx-ecosystem/staking-on-energy-web-x/staking-rewards-on-ewx.md).

# Staking Rewards on EWX

#### Reward Mechanism <a href="#reward-mechanism" id="reward-mechanism"></a>

* **Reward Source:** Annual inflation = **2.5M EWT** newly minted
  * **80% (2.0M EWT)** → Growth rewards for collators & delegators
  * **20% (0.5M EWT)** → Community Fund Treasury
* **Reward Calculation Flow:**
  1. **Performance-based allocation:** Rewards per era are distributed to collators proportional to their **points** (blocks authored, equivocation handling, etc.).
     * `total_reward_for_candidate = (collator_points / total_points) * total_staking_reward`
  2. **Stake-based subdivision:** Each collator’s allocation is split pro-rata between collator self-stake and delegator stake.
     * `candidate_reward = (candidate_stake / candidate_total_stake) * total_reward_for_candidate`
     * `nomination_reward = (nomination_stake / candidate_total_stake) * total_reward_for_candidate`
  3. **Collator commission (validator tax):** **10%** fee applied to delegator share.

#### Reward Timing <a href="#reward-timing" id="reward-timing"></a>

* **Era length:** **7,200 blocks** (\~24 hours).
* **Growth period length:** **28 eras** (\~28 days).
* **Reward payout delay:** **2 eras** after the end of reward period.
* **Unstaking delay: 2 eras**

#### Transaction Fees <a href="#transaction-fees" id="transaction-fees"></a>

* Collected fees form an additional reward pot.
* Distributed per era using the same **points → stake → commission** logic as growth rewards.

#### Validator / Collator Parameters <a href="#validator-collator-parameters" id="validator-collator-parameters"></a>

* **MaxCandidates:** 100 (max collators in the pool).
* **TotalSelected:** 20 active collators selected per era (configurable).
* **MaxTopNominationsPerCandidate:** 300 (top delegators by stake per collator are counted).
* **MaxNominationsPerNominator:** 100. Number of collators a delegator can nominate.
* **MinCollatorStake:** 5,000 EWT (self-bond requirement).
* **MinTotalStake:** 250,000 EWT (total stake, self-bond + delegated stake, needed to be in active set).

#### Validator Onboarding Token Requirements <a href="#validator-onboarding-token-requirements" id="validator-onboarding-token-requirements"></a>

* **EWX self-stake:** ≥5,000 EWT (+ \~10 EWT gas buffer).
* **EWC:** ≥1 EWT (to sync with Tier-1 chain).
* **Ethereum:** ≥0.15 ETH (to support bridge syncing ops)


---

# 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://docs.energyweb.org/ewx-ecosystem/staking-on-energy-web-x/staking-rewards-on-ewx.md?ask=<question>&goal=<user_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.
