> For the complete documentation index, see [llms.txt](https://docs.opaldex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opaldex.com/problem-and-vision.md).

# Problem & Vision

### The Problem with Current DEXs

Public order flow in L1/L2 mempools reveals trader intent before execution, enabling:

**Front-Running & Sandwiching** Sophisticated actors see your order in the mempool and place their own orders around yours to extract value.

**Stop-Loss Hunting** Large players can see clusters of stop orders and manipulate prices to trigger cascading liquidations for profit.

**Predatory Liquidations** Traders face aggressive liquidation dynamics that erode PnL and confidence, especially during volatile conditions.

**MEV Extraction** Miners and validators can reorder, insert, or censor transactions to extract maximum value at traders' expense.

### Why Existing Solutions Fall Short

Traditional approaches like private RPCs or order obfuscation provide limited protection:

* Single points of trust
* Incomplete privacy (timing/size leaks)
* No post-trade verifiability
* Still vulnerable to sophisticated MEV


---

# 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://docs.opaldex.com/problem-and-vision.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.