# DEX Aggregation

When multiple DEXs exist on a blockchain, liquidity gets fragmented. Each DEX has its own set of pools with its own liquidity. Token A might be cheap on DEX 1 but expensive on DEX 2. Without aggregation, users have to manually check each exchange and most don't bother, settling for whatever price their default DEX offers.

This is the exact problem Tower solves on Arc.

#### How Tower Aggregates

Tower's aggregation layer connects directly to the smart contracts of every DEX on Arc. It continuously fetches:

* **Real-time pricing** from every pool
* **Liquidity depth** (how much is available before significant price impact)
* **Pool states** (active, paused, or low liquidity)

#### The User Experience

From the user's perspective, aggregation is invisible. There is one swap interface, one quote, one button. Behind the scenes, Tower has compared every possible option and surfaces the best one. Users never need to think about which DEX to use.


---

# 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://tower-exchange.gitbook.io/tower-exchange/fundamentals/dex-aggregation.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.