> For the complete documentation index, see [llms.txt](https://docs.slavi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slavi.io/products-ecosystem/decentralized-exchange/functionalities.md).

# Functionalities

### Swap

Swap tokens with fast finality and low transaction fees on multi-chain space

### Pool

Providing liquidity and earning a 0.25% swap fee on all trades proportional to the share of the pool.

### Leverage Swap

Leverage swap tokens with fast finality and low transaction fees on multi-chain space.

Leverage is coming soon

### Farm

Also known as liquidity mining, stake your LP tokens and earn SLV rewards.

Farming is coming soon.

### Stake

Single staking your SLV token to earn ETH, BNB, USDT and other incentives in the future.

### Launchpad

Staking and vesting your SLV or another token to participate in the initial DEX offering of new projects in the future.

Launchpad is coming soon.

### Analytics

Analytics for SlaviDEX with advanced charting tools.&#x20;


---

# 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.slavi.io/products-ecosystem/decentralized-exchange/functionalities.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.
