> For the complete documentation index, see [llms.txt](https://docs-dapp.loopring.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-dapp.loopring.io/earn/overview/lrc-staking.md).

# LRC Staking

LRC staking has been newly released which enables users to lock their $LRC for a time period and gain protocol fees.

Protocol fees are the fees associated with every transaction in the Loopring ecosystem.

LRC Staking is one of the features where users can enjoy a share of these protocol fees!

<figure><img src="/files/EkCT9ghoHs1WFaeLwemD" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Did you know?**

Staking LRC is a <mark style="color:blue;">risk-free</mark> investment! Your locked assets can always be withdrawn at any time.&#x20;

Once the assets are withdrawn, the accrued rewards will be sent back to the protocol fee pool and redistributed to the remaining stakers.
{% 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 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-dapp.loopring.io/earn/overview/lrc-staking.md?ask=<question>&goal=<endgoal>
```

`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.