> For the complete documentation index, see [llms.txt](https://tryflux.gitbook.io/flux-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tryflux.gitbook.io/flux-docs/2.-problem-statement.md).

# 2. Problem Statement

#### 2.1 The Gap in DeFi Automation

Despite the rapid growth of decentralized finance, a critical gap exists in automation tooling:

1. **Limited Middleware**: Most DeFi workflows require either manual execution or custom development. Existing solutions are tailored to specific strategies or risk profiles, leaving builders to start from scratch.
2. **Lack of Observability**: Users executing autonomous strategies often lack transparency into agent behavior, decision-making, and on-chain outcomes. Post-execution analysis is difficult and auditing is fragmented.
3. **Safety and Control Trade-offs**: Fully autonomous systems risk unsupervised execution, while manual systems don't scale. There is no widely adopted middle ground that preserves both safety guardrails and the benefits of automation.
4. **Fragmented Execution Models**: Different chains, AMMs, and liquidity sources require distinct integrations. A unified platform for Uniswap automation—across chains and versions—is absent.

#### 2.2 The User Need

Power users and builders need:

* **Repeatability**: Define a strategy once and execute it consistently across multiple pools or time windows
* **Auditability**: Complete visibility into every agent tick, quote, and on-chain transaction
* **Safety**: Runtime controls to prevent unintended large-scale or fast execution
* **Integration**: Native connectivity to production Uniswap APIs without reinventing the wheel
* **Experimentation**: A dedicated research environment (Liquidity Lab) for exploring advanced pool mechanics without live risk


---

# 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://tryflux.gitbook.io/flux-docs/2.-problem-statement.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.