> For the complete documentation index, see [llms.txt](https://raifi-1.gitbook.io/raifi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://raifi-1.gitbook.io/raifi-docs/staking/rai-staking-mechanism.md). # RAI Staking Mechanism RAI staking forms the core of our yield generation system, designed to reward long-term holders while supporting ecosystem stability. When you deposit RAI tokens into our staking contract, you receive sRAI (staked RAI) tokens that automatically compound rewards every 8-hour epoch cycle. The Annual Percentage Yield ranges dynamically from 100% to 2,300%, managed by AI algorithms that analyze protocol health, market conditions, and revenue generation to determine sustainable reward rates. This isn't arbitrary - the AI continuously balances user rewards with long-term protocol viability. Reward funding comes from multiple sustainable sources rather than relying purely on token inflation. Protocol transaction fees provide steady baseline revenue, while RWA portfolio yields contribute returns from real-world asset management. Future lending platform profits and treasury investment returns will add additional revenue streams as the ecosystem expands. --- # 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://raifi-1.gitbook.io/raifi-docs/staking/rai-staking-mechanism.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.