> For the complete documentation index, see [llms.txt](https://docs.rigoblock.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rigoblock.com/readme-2/grg-staking.md). # GRG Staking When a pool is registered in the Rigoblock staking system, it becomes eligible for receiving GRG rewards. The wallet registering the pool in the staking system is tagged as "staking pal" and receives 10% of the pool operator's rewards, unless it is the same wallet, which receives 100% of the rewards. GRG holders can stake to their preferred staking pool (or the staking pool which maximizes their ROS) and, as a return for helping the pool operator maximizing its rewards, receive a portion of the pool operator's reward. By default, a minimum of 30% of reward is shared with the pool's stakers. The pool operator can increase the percentage shared with the community in order to attracting more stake and increasing its rewards. Once increased, the percentage shared cannot be decreased, therefore the pool operator must carefully consider the tradeoff between attracting stake and maximizing profitability. During an epoch (2-weeks long initially) any wallet can credit the proof-of-performance reward for a said pool to the staking system, which is initially equal to the pool's locked staked GRG to itself. At the end of each epoch a pool's own stake competes with the other active pools' own stakes. In the same way, the total stake delegated to a pool competes with the total stake delegated to all active pools. The two metrics are weighted according to an Arrow-Pratt exponential weighting formula, which initial setting of 2/3 weight for the pool's own relative stake and 1/3 weight for the pool's overall relative delegated stake. GRG staking is available on Ethereum Mainnet, Arbitrum, Optimism, Base, Unichain, Polygon and BNB chain. --- # 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.rigoblock.com/readme-2/grg-staking.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.