# About Avitus Labs

Avitus is the largest perpetual DEX built on the <mark style="color:yellow;">**Movement Chain**</mark> With **700K+ participants**, **$60M+ Total Value Locked (TVL)** on devnet, and a thriving community of over **400K+ users**, designed to combine top of the line performance with advanced trading tools for a seamless and secure trading experience. Our mission is to set new standards in decentralized finance by providing a platform that is fast, reliable, and packed with features for both traders and liquidity providers.

Avitus leverages the <mark style="color:yellow;">**Movement Chain**</mark>, a high-performance network capable of **160K transactions per second (TPS)** with low fees and near-instant transaction finality. This infrastructure allows us to support advanced trading mechanics, from **self-hedging automated market-making** to **100x leverage** and **customizable automated trading bots**.

The core innovation of Avitus is its **self-hedging liquidity pool**, which minimizes risk for liquidity providers while ensuring high APR returns through dynamic fee-sharing mechanisms. Traders benefit from real-time tools like **liquidity heatmaps**, **oracle deviation protection,** **on-the-go trading via Telegram mini-apps** and so much more.

Avitus isn’t just a trading platform—it’s an ecosystem built to scale. Future developments include expanded asset support, and new financial products, all while maintaining our commitment to security, transparency, and user empowerment.


---

# 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://avitus.gitbook.io/avitus-docs/readme.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.