> For the complete documentation index, see [llms.txt](https://docs.wheelx.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wheelx.fi/overview/safety-and-security/mev-protection.md).

# MEV Protection

<figure><img src="/files/rALU3rptLPgagRe2Rxbb" alt=""><figcaption></figcaption></figure>

### What is MEV?

Maximal Extractable Value (MEV) refers to the value that block producers or observers can extract by reordering, inserting, or censoring transactions within a block. The most common MEV attack is a **Sandwich Attack** — an attacker front-runs your trade (buys before you), pushes the price up, then back-runs (sells after you) to profit at your expense.

### Protection Mechanisms

* **Private transaction submission** — Transactions are submitted through private channels where supported by the chain, bypassing the public mempool. Attackers cannot observe your trade before execution.
* **Slippage protection** — Configurable thresholds ensure your trade only executes if the output amount is within your acceptable range. If price deviation exceeds your threshold, the transaction is automatically reverted.
* **MEV-aware routing** — The AI Router evaluates candidate paths for MEV exposure and preferentially selects routes with lower extractable value, reducing attacker opportunity.
* **Private relay integration** — For chains that support private relay infrastructure, transactions are submitted directly to block builders, completely bypassing the public mempool.

### Intent-Based Routing: Built-in MEV Resistance

WheelX's Intent-based routing provides inherent MEV protection. You only submit the desired outcome ("I want Token B from Token A"), not the execution path. This means:

* **No path details exposed** — attackers can't predict which route your trade will take
* **Internal orchestration** — the AI Router selects and executes the path privately
* **No manual multi-step signing** — each step is handled internally, not submitted to public mempools individually

### Benefits

* **Prevent sandwich attacks** — Private submission and MEV-aware routing eliminate front-run/back-run opportunities
* **Reduce value loss from front-running** — Transactions that can't be seen can't be exploited
* **Fair execution for all transaction sizes** — Same protection regardless of trade size


---

# 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.wheelx.fi/overview/safety-and-security/mev-protection.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.