> 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/exiting-the-protocol/matching-unstake-to-stake-requests.md).

# Matching unstake to stake requests

At the beginning of the exit process, the LEEQUID protocol opens a 24-hour window in which the unstake request can be matched to stake requests of new/onboarding users, cutting short the exit process and delivering reduced waiting times. During this period, one of three things can happen:

1. No stake is matched
2. Only a portion of the unstake value is matched
3. The unstake request is fully matched by incoming stake

Both scenarios 1 and 2 result in the unstake request advancing to the next stage, where validators are exited from the Proof of Stake protocol and withdrawn LYX returns from the LUKSO deposit contract to the LEEQUID protocol. The amount withdrawn will cover all the unmatched value and the unstake will be available to be claimed in a single action. This represents the longest path to unstaking in the LEEQUID platform:

<figure><img src="/files/sPJgPKM4ioYF9ASQvmdS" alt=""><figcaption><p>The unstake process. Notice the separation of flows after the "Match found" condition.</p></figcaption></figure>

Alternatively, scenario 3 can happen, where stake from users trying to enter the LEEQUID protocol ends up covering the amount another user was trying to unstake. In such scenario, there is a full match and the process terminates earlier, without the exit of any validators from the Proof of Stake protocol. The LYX will be available earlier and it can be claimed by the user in a single action. Scenarios like this represent the shortest path in the diagram above, which bypasses all the exit procedures in the Proof of Stake protocol.


---

# 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:

```
GET https://docs.leequid.io/leequid/navigating-leequid/exiting-the-protocol/matching-unstake-to-stake-requests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.