> For the complete documentation index, see [llms.txt](https://hyperlynx.gitbook.io/hyperlynx-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyperlynx.gitbook.io/hyperlynx-docs/lynx/ylynx-and-staking.md).

# yLYNX and Staking

Staking turns **$LYNX** into **yLYNX** — a position that earns the protocol's fee share and compounds it for you.

## How it works

1. Stake $LYNX and receive yLYNX.
2. yLYNX accrues the **69% staker share** of swap fees (see [The fee machine](broken://pages/963dfe997652672f82bd42aa0bf79d4466e42f7d)).
3. Rewards **auto-compound** into a HYPE-LST vault — you don't have to claim and re-stake manually.
4. Unstake back to $LYNX when you want.

## Why stake

* **Eat the fees.** Staking is how you receive the protocol's revenue share.
* **Hands-off.** Compounding is automatic.
* **Aligned.** Stakers are the holders the fee machine is built to reward.

## Claiming straight into yLYNX

At TGE you can claim your airdrop directly into yLYNX in one step, so you start earning the fee share immediately rather than claiming liquid and staking separately. See [Claiming](broken://pages/163cd9459abf56276653cd42a75ac7a2b84a7106).

{% hint style="warning" %}
Staking yields are variable — they depend on trading activity. Nothing here is financial advice.
{% endhint %}


---

# 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://hyperlynx.gitbook.io/hyperlynx-docs/lynx/ylynx-and-staking.md?ask=<question>&goal=<user_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.