> 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/10.1-staking-model-and-role-alignment.md).
# 10.1 Staking Model and Role Alignment
In FreCx, staking is not a one-size-fits-all mechanism. Each node role has a defined staking structure, designed to balance accessibility with responsibility.
The staking requirements are structured as follows:
* Cluster Nodes require a fixed stake of 1,000,000 FreCx per node, with additional nodes requiring multiples of the same amount.
* Sync Nodes require staking in multiples of 2,500 FreCx, allowing flexible scaling of participation.
* Vault Nodes require staking in multiples of 1,000 FreCx, enabling broader participation across a larger validator set
### Node Capacity Configuration
The FreCx mainnet enforces the following maximum participation limits:
* The network supports up to **10 Cluster nodes**, which are responsible for block production and consensus coordination.
* The network supports up to **150 Sync nodes**, which perform full-state validation and transaction verification.
* The network supports up to **16,000 Vault nodes**, which provide distributed verification, redundancy, and data integrity assurance.
This structure ensures that high-impact roles (Cluster) require significant commitment, validation roles (Sync, Vault) remain accessible and scalable, and participation can increase incrementally without rigid constraints
From a user perspective, this means staking is both modular and extensible, allowing gradual participation based on available capital and intended involvement.
---
# 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/10.1-staking-model-and-role-alignment.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.
