> For the complete documentation index, see [llms.txt](https://docs.kyte.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyte.sh/guides/stake.md).
# Stake $KYTE
Stake $KYTE and receive 30% of protocol fees in WETH every epoch.
Page: [kyte.sh/stake](https://kyte.sh/stake)
Stakers receive **30% of protocol fees**, paid in **WETH** once per epoch. The share is set by the timelock and can never go below 20%.
{% stepper %}
{% step %}
### Stake
Approve `$KYTE` to the StakingPool, then `stake(amount)`. Your stake is **pending** until the current epoch ends (00:00 UTC).
{% endstep %}
{% step %}
### Earn
From the next epoch, your stake is **active** and earns a share of every fee split.
{% endstep %}
{% step %}
### Claim
`claim()` sends your accrued WETH to your wallet at any time.
{% endstep %}
{% step %}
### Unstake
`unstake(amount)` is immediate. It takes pending stake first, then active stake that is no longer locked.
{% endstep %}
{% endstepper %}
## The activation lock
Stake that has just become active is locked for the epoch it activates in. Here is what staking in epoch *N* means.
How new stake activates, earns and unlocks
| Epoch | Your stake |
| -------------------- | ---------------------------------------------------------------- |
| *N* (when you stake) | Pending. Can be withdrawn at any time. Earns nothing yet. |
| *N + 1* | Active and earning. **Locked**: it can't be unstaked this epoch. |
| *N + 2* onward | Active, earning, and free to unstake. |
{% hint style="info" %}
This blocks "stake one second before the split, collect, leave". Every reward is earned by stake that stayed through a full epoch. The page shows your active, pending, locked and claimable amounts, plus a countdown to the next epoch.
{% endhint %}
Deeper detail: [Staking mechanics](/protocol/staking.md).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.kyte.sh/guides/stake.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
