# Staking

The goal of our protocol is to **maintain the largest possible percentage of the supply in staking** and to distribute rewards at every rebase. \
Rebases are spaced out every 8 hours, and to avoid speculation at each rebase approach, a 2 epochs lock is implemented for each staking.\
\
Example: The current epoch is at 4:30 out of 8. I deposit my $OMM into staking to take advantage of the APR, my tokens will be locked for 3.5 + 8 = 11.5 hours.\
\
The APY is variable and takes into account different metrics such as the treasury, bonds, liquidity pool size, and the number of tokens staked.\
Our goal is to find an attractive APY while limiting the daily token creation. In fact, the major problem with protocols offering staking rewards in the native token is the supply inflation. An elastic supply minting tokens to reward staking inevitably creates additional selling pressure. That's why we include a **warm-up of one epoch** before claiming rewards as well as a variable APY. \
The tokens are also automatically auto-compounded to prevent users from making multiple transactions and to limit sales related to mandatory manual claim.\
\
To counteract selling pressure related to token inflation, we introduced different mechanisms with the aim of buyback and burn tokens but also to increase the size of the LP to limit the price impact and allow large purchases/sales.\
\
One of the features we will implement in our protocol is a reward calculator to simulate the value of one's bag through the auto-compound of staking as well as the Δ of the $OMM price over time.\ <br>


---

# Agent Instructions: 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:

```
GET https://omium-protocol.gitbook.io/omium/protocol/staking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.