# Why Alphix

Decentralized Finance (DeFi) markets are evolving toward hook-based architectures (Uniswap V4, Balancer V3, PancakeSwap, Ekubo)**.** In this paradigm, allocating capital in fragmented pools, where liquidity sits idle, and fees remain static despite dynamic conditions, should be a thing of the past. 

Yet current solutions remain isolated, complex and risk-prone. As a result, Liquidity Providers (LPs) juggle multiple pools, traders suffer increased slippage, and innovation faces an immediate competitive disadvantage.

**Alphix it** introducing **Unified Pools**<mark style="color:$info;">.</mark>

By building a simple, efficient and modular hook solution on top of Uniswap V4, Alphix combines innovation into a single pool:

* **Dynamic Fees**

  Swap fees that adjust to market conditions, making pools competitive across volatility regimes.
* **Unified Yield**

  Idle liquidity is deployed to lending markets, earning additional yield without added management complexities.

Together, these features maximize capital efficiency for LPs while providing traders with competitive execution.

***

**Our Mission**

* [x] **LPs** earn more from a single and efficient position (per token pair).
* [x] **Traders** get better execution through competitive swap fees and deeper liquidity.
* [x] **Aggregators & Protocols** use Unified Pools to route volume&#x20;
* [x] **Partners** leverage our inherent pool customization to fine-tune markets to their respective demands.


---

# 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://alphix.gitbook.io/docs/the-basics/why-alphix.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.