> For the complete documentation index, see [llms.txt](https://docs.novarpc.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novarpc.xyz/nova-rpc/why-use-a-private-mempool.md).

# Why Use a Private Mempool

There are two structural mechanisms through which transaction originators lose value on Ethereum:<br>

1. **MEV:** Routing transactions to the public mempool transforms transactions into exploitable signals, meaning value is extracted by adversarial third parties before inclusion. This leads to:
   * Front-running
   * Back-running
   * Sandwich attacks
   * Increased slippage
   * Strategic manipulation\ <br>
2. Given lack of information, transaction originators commonly guess the price of blockspace. This leads to two forms of loss:&#x20;

   * **Overpayment**: unnecessary transfer of surplus to validators/builders
   * **Underpayment**: delayed inclusion, failed execution, or opportunity loss

In both cases, execution uncertainty destroys value.


---

# 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.novarpc.xyz/nova-rpc/why-use-a-private-mempool.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.