> For the complete documentation index, see [llms.txt](https://organic-1.gitbook.io/organic-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://organic-1.gitbook.io/organic-docs/staking/how-staking-boost-works.md). # How Staking Boost Works Right now, staking isn’t live yet, but it’s already on our roadmap. We see staking as a way to make growth more sustainable and to reward long-term commitment without breaking fairness. The plan is to let stakers earn a small boost on their task rewards, capped at a fair limit so no whale can dominate. The exact parameters, like how much boost and what the cap will be, will all be decided through community votes once the system is ready to roll out. How it Works * Staking increases your score with a cap * Formula: `B = min(1 + sqrt(staked_ORG) / K, 1.25)` * K will be proposed and voted by the community * Boost cap at 1.25 keeps it fair --- # 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://organic-1.gitbook.io/organic-docs/staking/how-staking-boost-works.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.