# Deposited LYX lifecycle

When a user stakes LYX through the LEEQUID staking pool, the coins are transferred to the Pool contract, where they will sit for a few minutes until LEEQUID’s oracles detect an amount larger than 32 LYX sitting on the Pool contract. This is the condition that triggers the Oracles to register a new validator, transferring the stake from the Pool to the LUKSO official deposit contract. From here, the tokens can either be burned in the case of slashing, or sent to the withdrawal address when the validator exits the protocol.

<figure><img src="/files/LGWU71g6L8wuW9lj6x1p" alt=""><figcaption><p>LYX flow from the LEEQUID protocol to the LUKSO deposit contract</p></figcaption></figure>

The diagram above illustrates the non-custodial flow of funds from the user address into the LEEQUID protocol and finally to the official deposit contract of LUKSO. Once in there, the LUKSO contract has control over the staked amounts and can use it to slash the validators in case of bad behavior or give it back, once an exit request successfully goes through.


---

# Agent Instructions: 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/staking/deposited-lyx-lifecycle.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.