> For the complete documentation index, see [llms.txt](https://docs.ec-cube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ec-cube.io/tokenomic/5.-staking-reward/5.2-reward-distribution-based-on-staking-score.md).

# 5.2 Reward distribution based on Staking Score

**ing $ECT tokens and maintaining a PoS deposit will generate a staking score. During each round of staking reward distribution, the amount of $ECT tokens rewarded to a user will be determined based on their staking score.**

For example, in the 3rd round of staking reward distribution, a total of 20,000 $ECT tokens are rewarded, distributed to 2 users, with User A having a staking score of 400 and User B having a staking score of 100. Therefore, User A will receive 16,000 $ECT tokens as a reward, while User B will receive 4,000 $ECT tokens as a reward.

**For information on how the staking score is calculated, refer to section 5.4.**


---

# 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://docs.ec-cube.io/tokenomic/5.-staking-reward/5.2-reward-distribution-based-on-staking-score.md?ask=<question>&goal=<endgoal>
```

`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.