> 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/safety-and-security/mev-protection.md).

# MEV Protection

MEV Protection Protect your transactions from Maximal Extractable Value (MEV) attacks.

<figure><img src="https://4149802529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTtoew6SwbdqR04YafQFk%2Fuploads%2FOFySwKtATdxf4tX6vE0R%2Fmev-protection-wheelx-v1.png?alt=media&amp;token=01d861ca-397c-4625-9c0f-83ad3478e6aa" 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