> For the complete documentation index, see [llms.txt](https://sdk.chorus.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk.chorus.one/staking-fundamentals/staking-concepts/what-is-mev.md).

# What is MEV?

## MEV Demystified

While it might sound complex, MEV is actually fairly simple from a big picture perspective, but of course the nitty-gritty technicals of how it works are far more nuanced.

{% hint style="success" %}
**MEV (Maximal Extractable Value)** refers to the extra profit validators can make by controlling the order of transactions in a block.
{% endhint %}

For institutional staking providers, how MEV is captured and distributed has a direct effect on validator performance and client yield. Chorus One operates validator infrastructure designed to capture MEV efficiently — through MEV-boost integration and internal research into proposer timing — while maintaining network integrity.

***

### That's MEV at a Glance

For a deeper technical perspective, Chorus One' research team has contributed to the public body of knowledge on MEV. This includes **Adagio**, an in-house optimized Ethereum MEV-boost client designed to capture additional rewards by improving timing behavior in the transaction supply chain ([research writeup](https://chorus.one/articles/timing-games-and-implications-on-mev-extraction)).

* In a pilot study, Adagio generated approximately 4.75% additional MEV rewards on Ethereum compared to baseline configurations.

Related research is publicly available on [EthResearch](https://ethresear.ch/t/the-cost-of-artificial-latency-in-the-pbs-context/17847).

***

Feel free to reach out to our Support Team if you would like any clarification.

{% hint style="info" %}
For direct support, please create a ticket on our [support platform](https://support.chorus.one/hc/en-us/requests/new).

A link for a support request can also be found along the top of this webpage as well as many other Chorus One resources including [Ethereum Staking Pool](https://opus.chorus.one/pool/stake/), [The Chorus One SDK](https://chorus-one.gitbook.io/sdk), and [our Blog](https://chorus.one/insights-category/blog).
{% endhint %}

***

<details>

<summary>About Chorus One</summary>

Chorus One is one of the largest institutional staking providers globally, operating infrastructure for over 60 Proof-of-Stake (PoS) networks, including Ethereum, Cosmos, Solana, Avalanche, Near, and others.

Since 2018, we have been at the forefront of the PoS industry, offering easy-to-use, enterprise-grade staking solutions, conducting industry-leading research, and investing in innovative protocols through Chorus One Ventures.

As an ISO 27001 certified provider, Chorus One also offers slashing and double-signing insurance to its institutional clients. For more information, visit [chorus.one](https://chorus.one/) or follow us on [LinkedIn](https://www.linkedin.com/company/chorus-one/), [X (formerly Twitter)](https://twitter.com/ChorusOne), and [Telegram](https://t.me/chorusone).

</details>


---

# 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://sdk.chorus.one/staking-fundamentals/staking-concepts/what-is-mev.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.