> 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/slavi-wallet/earn.md).

# Earn

In the **Slavi DApp**, we offer to clients built-in and third-party earning offers by holding cryptocurrencies. Built-in decentralized applications involve earning on various liquidity providers, where **Slavi acts as a liquidity provider**.

Built-in earning mechanisms will include a set of smart contracts interconnected with native services to simplify access for ordinary users. We exclude intermediate steps and provide the client only the final step, *just stake it*. These methods may also include bridges between blockchains, which will affect fees in the staking currency on deposits and withdrawals.

Slavi Wallet  provides Staking, Liquidity Mining, Farming Pools, Cross-Chain USDT Pools, and more.


---

# 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/slavi-wallet/earn.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.
