> For the complete documentation index, see [llms.txt](https://docs.syno.finance/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.syno.finance/documentation/tokenomics-and-rewards/syno-tokenomics/ssyno.md). # sSYNO SYNO staking allows users to deposit their SYNO tokens into a staking contract to gain governance power and earn additional SYNO rewards. It is a single-sided staked token unlike vlSYNO. The staking process includes a 0 warm-up period before tokens become fully active and a cooldown period of 3 days before tokens can be unstaked. This ensures stability and guards against governance attacks within the ecosystem. sSYNO is eligible for a percentage of emissions and fees: * 20% of Emissions allocated for vlSYNO & sSYNO * 20% of Money Market Fees allocated for vlSYNO & sSYNO * 20% of Optimistic Finality Fees allocated for vlSYNO & sSYNO All fees to be streamed & distributed via buyback and distribute in $SYNO to incentivize buying pressure on SYNO. --- # 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.syno.finance/documentation/tokenomics-and-rewards/syno-tokenomics/ssyno.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.