> For the complete documentation index, see [llms.txt](https://docs.frequencychain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frequencychain.org/10.-staking-rewards-and-economic-participation.md).

# 10.	Staking, Rewards, and Economic Participation

The FreCx network enables economic participation through a role-based staking system, where token holders contribute to network operations by staking and optionally operating nodes. Unlike generalized staking models, FreCx ties staking directly to functional roles within the protocol, ensuring that rewards are aligned with real participation in validation, verification, and block production.

Participation is accessible through two approaches. Users may operate nodes directly by setting up infrastructure and staking tokens, or they may use the (<https://validator.frequencychain.org/>) staking platform, which abstracts infrastructure complexity and provides a guided interface for staking, activation, and reward tracking. In both cases, staking serves as the foundation for network security and reward eligibility.

<figure><img src="/files/w3csKfolSPyewVHdOniC" alt=""><figcaption></figcaption></figure>


---

# 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.frequencychain.org/10.-staking-rewards-and-economic-participation.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.