> For the complete documentation index, see [llms.txt](https://dubble-dex.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dubble-dex.gitbook.io/docs/amm/liquidity-pools.md).

# Liquidity Pools

The main purpose of Dubble DEX is to enable secure trading of digital assets with low fees and slippage. Slippage is the difference between the expected price of an asset and the actual price at the time of the trade. To ensure the best rates for users, we have identified two types of assets:

* Stable assets, such as stablecoins like $USDC and $DAI.
* Volatile assets, such as tokens like $LINK and $CRV.

Dubble DEX provides two types of liquidity pools: Stable Pools and Volatile Pools. When executing a trade, the protocol router evaluates both pool types to determine the best available price quotation and trade execution route. To prevent flashloan attacks, the router uses 30-minute TWAPs to calculate prices. Additionally, the router does not require any external maintenance. A pool with deeper liquidity (higher value locked) will typically offer smaller slippage.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dubble-dex.gitbook.io/docs/amm/liquidity-pools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.