> For the complete documentation index, see [llms.txt](https://ionian.gitbook.io/mendi-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ionian.gitbook.io/mendi-finance/tokenomics/staking-and-revenue-sharing.md).
# Staking and Revenue Sharing
Mendi Finance is a real-yield protocol, which means that 100% of the revenue is shared within the Mendi DAO with the stakers. Unlike other protocols the core team is not taking a certain % of the protocol revenue for themselves rather than distributing it to all interested stakeholders. Additionally revenue from the POL in the form of oLYNX is also shared with the stakers.
## Staking Mechanism and Design
sMENDI and uMENDI represents the staked version of $MENDI. The main goal for staking is to distribute protocol revenue and oLYNX rewards with stakers.
Stakers will receive 80% of the protocol revenue and 80% of oLYNX rewards for the first 3 months. After team tokens start to get unlocked, stakers will begin receiving 100% of the protocol revenue.
Protocol revenue is generated by charging a fee based on reserve factors for different pools. The riskier the pool, the more fees will be generated this way.
There will be two different pools for staking. One of them will be sMENDI, where the rewards will be used to buy MENDI from the market and distribute it to sMENDI stakers. The other pool will be uMENDI, where the rewards will be used to buy USDC from the market and distribute it to uMENDI stakers.
Reward tokens are shared with stakers on a weekly basis due to Lynex epochs.
When you decide to unstake, there will be a one-week delay. For example, if you staked and wish to unstake on July 20th, 2023, you will be able to withdraw your tokens on July 27th, 2023. This precaution is in place for just-in-time stakers.
---
# 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://ionian.gitbook.io/mendi-finance/tokenomics/staking-and-revenue-sharing.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.