> 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/leequid-in-depth/the-slyx-token/acquiring-slyx.md).

# Acquiring sLYX

Acquiring sLYX is equivalent to either:

* creating a new staking position by staking through the platform, which triggers the addition of new validators to the protocol.
* buying someone else’s staked position, through direct transfer of sLYX or through market makers like the [LEEQUID liquidity pool](/leequid/leequid-in-depth/the-liquidity-pool-dex/implementation.md).

The liquidity pool, deployed by the LEEQUID team on LUKSO, is the mechanism responsible for increasing the liquidity of the sLYX token. Users can deposit or withdraw LYX at any time by swapping its LSD (Liquid Staking Derivative), the sLYX token, in the liquidity pool.


---

# 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/leequid-in-depth/the-slyx-token/acquiring-slyx.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.