> For the complete documentation index, see [llms.txt](https://docs.leequid.io/leequid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.leequid.io/leequid/navigating-leequid/claiming/claim-queued-stake.md). # Claim queued stake Most of the times, staking will be an instant process. A user will initiate the staking action through the LEEQUID platform and receive the liquidity tokens (sLYX) in a single transaction. If, however, there is a surge in staking demand, new staking requests will be stuck in the [activation queue](/leequid/navigating-leequid/staking/potential-wait-times-while-staking.md), resulting from the Proof of Stake algorithm bottleneck. This bottleneck exists to keep the consensus process running smoothly, as the sudden entry of hundreds of validators would disrupt calculations and flood the network with a workload that could impact the creation of blocks. The LEEQUID protocol buffers LYX up to a certain threshold. It accepts a degree of dilution, resulting from rewards which spill to new stakers not yet generating income for the protocol. However, when this threshold of 10% is reached, the minting of sLYX is delayed and new stake requests are added to the [dilution queue](/leequid/navigating-leequid/staking/potential-wait-times-while-staking.md#dilution-queue). In such scenario, a user's LYX is transferred to the LEEQUID protocol, but the minting of the corresponding sLYX is delayed. The user will have to wait until the queue reaches his position, meaning that his stake is now activated and generating rewards in newly registered validators. At this moment, the staking request is fully processed, the sLYX tokens will leave the “Pending” state and the claim action will be available in the LEEQUID dashboard. --- # 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.leequid.io/leequid/navigating-leequid/claiming/claim-queued-stake.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.