> For the complete documentation index, see [llms.txt](https://fluxflow.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://fluxflow.gitbook.io/docs/why-flux.md).

# Why Flux

## Flux: The Universal Liquidity Engine

Flux is the native engine for concentrated liquidity on the Fluent network. 

By leveraging the power of the **BlendedVM**, Flux enables high-precision capital allocation and serves as the foundational venue for universal liquidity. 

### The Vision

Liquidity is fragmented. Capital is scattered across chains, trapped behind risky bridges and wrapped assets. 

**Fluent breaks this at the architectural level with the BlendedVM. Flux unlocks it at the application level.** 

Flux leverages Fluent's rWasm core and simulated execution environments to build toward a unified venue where assets from WASM, EVM, and SVM stacks will coexist natively

**Today**, Flux delivers high-performance concentrated liquidity on the EVM stack. 

**As Fluent's BlendedVM matures**, Flux will extend this to SVM and WASM — enabling cross-stack swaps and unified liquidity pools in a single transaction.

### Core Capabilities

1. **Concentrated Liquidity AMM**: Higher capital efficiency for LPs and deeper liquidity for traders, optimized for rWasm execution.
2. **Native Integration**: Unlocking capital directly within the Fluent stack.
3. **Human-Centric Design**: Leveraging **Fluent Connect** to verify authentic participation and reward real users.


---

# 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://fluxflow.gitbook.io/docs/why-flux.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.