> For the complete documentation index, see [llms.txt](https://docs.liquity.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liquity.org/liquity-v1/faq/staking.md). # LQTY Staking All of the revenue the protocol makes is diverted to LQTY stakers. By staking LQTY you are entitled to a pro-rate share of it. ### How does staking work in Liquity? To start staking all you need to do is deposit your LQTY token to the Liquity staking contract. Once done you will start earning a pro rata share of the borrowing and redemption fees in LUSD and ETH. For more details watch this step-by-step [video](https://youtu.be/hlUoHh_5Jn8). ### How much will my staked LQTY earn? Your LQTY stake will earn a share of the fees equal to your share of the total LQTY staked, at the instant the fee occurred. ### Is there a lock-up period? No, you can withdraw your staked funds at any time. ### Can I stake LUSD? You can only stake LQTY tokens. LUSD can be deposited into the [Stability Pool](/liquity-v1/faq/stability-pool-and-liquidations.md#what-is-the-stability-pool) instead. ### Are staked LQTY tokens used to backstop the system (like Maker) or for governance? No, staked LQTY are not used to backstop the Liquity system and are not used for governance as there is no Liquity governance. --- # 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.liquity.org/liquity-v1/faq/staking.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.