> For the complete documentation index, see [llms.txt](https://docs.native.org/aqua/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.native.org/aqua/introduction.md).

# Introduction

<figure><img src="https://lh7-us.googleusercontent.com/dWTj6Ah9m2SKostksK-qkJZee7w8QZ56aGu173OKLngUvilP457PEnBsZT3aA_mqa216GiQwNzhrTNrVhy0zjw6efwxTgDz7ooWWxIxj__23x7V9KnJtJvLeex44LtTgDBNSQ-5Lzg8zA4TjvtTnMfc" alt=""><figcaption><p>Aqua overview</p></figcaption></figure>

\
Aqua introduces an innovative solution that empowers market makers to offer pricing capabilities without the burden of managing inventory availability. This functionality allows market makers to facilitate leveraged trading, contingent upon maintaining robust credit.

By delegating price risk-taking from Liquidity Providers (LPs) to professional market participants, Aqua addresses the issue of "impermanent loss" for LPs. This setup allows LPs to stake capital on a per-asset basis, ensuring predictable passive income.

In essence, market makers can seamlessly borrow the 'buy token' (quote token) to facilitate user swaps as short positions, while returning the 'sell token' (base token) from users to Aqua as long positions. Closing positions entails market makers settling all short positions and taking all long positions.

It's essential to note that while market makers "borrow" assets for swaps, assets from the other leg of the swap are directly received by Aqua. Position balances are recorded in the smart contract with every swap, preventing market makers from absconding with borrowed assets.

On the other hand , liquidity providers can utilise Aqua akin to a lending protocol like Compound. They can supply liquidity and use it as collateral to borrow from the pool. The distinction lies in market makers utilising supplied liquidity for their trading activities, incurring associated costs.. Consequently, capital efficiency and yield for liquidity providers are significantly enhanced.


---

# 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.native.org/aqua/introduction.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.
