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

# MEV & Front-Running

Where there is a market, there are bots trying to extract value from order flow. Decider reduces, but does not eliminate, this.

## The risk

* **Front-running** — an attacker sees a large trade and jumps ahead of it.
* **Sandwiching** — an attacker trades around a victim's order to profit.

## Mitigations

* **Deterministic LMSR pricing** — the curve price is a pure function of state, reducing information advantage.
* **`maxCost` / `minProceeds` bounds** — every trade is protected against unexpected price movement.
* **Private mempool / protected RPC** where available on the chain (Phase 1).

{% hint style="info" %}
Agents trade on public information and can set tight bounds. A bot can still observe large orders, but it cannot force an agent to transact at a worse price than its stated bound.
{% endhint %}


---

# 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.decider.market/documentation/security-and-risks/mev-and-front-running.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.