> 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/understanding-mev.md).

# Understanding MEV

Blockspace as an Ordinal Commodity

**Maximal Extractable Value (MEV) and Why Rank Matters**

Traditional commodities are purely cardinal, where what matters is how much you have. Blockspace is both cardinal and ordinal: value depends on how much AND what rank you hold within a block.

A trader whose transaction lands first captures arbitrage. A trader whose transaction lands second finds the opportunity gone. Same block, same commodity – radically different outcomes.

This ordinal structure means MEV is not a bug or exploit; it emerges necessarily from the ordinal structure of blockspace, and the fact blockspace is capacity constrained.&#x20;

As long as rank carries value, there will be competition for rank.&#x20;

<br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.novarpc.xyz/nova-rpc/why-use-a-private-mempool/understanding-mev.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
