> For the complete documentation index, see [llms.txt](https://token.metasignals.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://token.metasignals.io/tokenomics/token-utilities/staking-rewards.md). # Staking Rewards MSIG staking is designed to align long‑term participants with the overall health and usage of the Meta Signals ecosystem, without granting any claim on company revenue, equity, or profits. Stakers contribute to network security and stability and, in return, receive protocol‑driven rewards that are determined by transparent rules encoded in the system. **How staking rewards work:** * Rewards are distributed according to a predefined on‑chain mechanism that can source funds from designated ecosystem treasuries and budgets (for example, from fees that have been allocated to the protocol treasury by governance), not from any contractual right to business revenue or profit share. * The effective reward rate depends on factors such as total staking participation, treasury parameters, and governance‑set configurations, rather than any promise of fixed yield or return. * Stakers can opt to auto‑compound their rewards, increasing their stake over time according to the same public, rules‑based logic. --- # 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://token.metasignals.io/tokenomics/token-utilities/staking-rewards.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.