> For the complete documentation index, see [llms.txt](https://eigenphi-1.gitbook.io/classroom/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eigenphi-1.gitbook.io/classroom/eigenphis-methodologies/how-eigenphi-identifies-mev.md).

# How EigenPhi Identifies MEV

Presently, EigenPhi analyzes three types of MEV, namely Arbitrage, Sandwich, and Liquidation, which aim to examine transaction structures on the ETH and BSC chains.

* EigenPhi assists users in comprehending how MEV strategies function regarding asset transfers.
* EigenPhi demonstrates how searchers can leverage arbitrages to enhance market productivity and promote market efficiency.
* EigenPhi presents the entire Arbitrage, Sandwich, and Liquidation processes through Token Flow charts, increasing community awareness and promoting responsible trading practices.

In summary, by providing users with a better understanding of market dynamics and exposing unethical practices, EigenPhi contributes to a more transparent and productive DeFi ecosystem.


---

# 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://eigenphi-1.gitbook.io/classroom/eigenphis-methodologies/how-eigenphi-identifies-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.