> For the complete documentation index, see [llms.txt](https://pijschain.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pijschain.gitbook.io/whitepaper/tokenomics/effective-staking-amount-and-concentration-control.md).

# Effective Staking Amount & Concentration Control

PIJSChain enforces participation through strict, contract-level staking rules applied to Hardware Operators.

To activate as a Hardware Operator, participants must commit a one-time activation stake of 10,000 PIJS. Once active, each Hardware Operator is subject to an effective staking cap of 200,000 PIJS.

Any PIJS staked above this effective limit does not generate additional rewards.

This design intentionally discourages stake concentration and prevents excessive dominance by large capital holders. Rather than rewarding sheer stake size, the protocol incentivizes:

* broader distribution of infrastructure responsibility,
* formation of multiple independent Hardware Operators,
* decentralization rooted in operational diversity.

Capital remains welcome, but control is structurally constrained.


---

# 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:

```
GET https://pijschain.gitbook.io/whitepaper/tokenomics/effective-staking-amount-and-concentration-control.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.