> For the complete documentation index, see [llms.txt](https://docs.crescent.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crescent.network/introduction/crescent-dex-legacy/batch-execution.md). # Batch Execution In traditional exchanges or newer AMM DEXs, prioritization of orders by sub-second latency creates huge problems around fairness of the marketplace. Especially in decentralized setup, MEV(Miner Extractable Value) is a huge cost to every ordinary traders in DEXs. In Crescent DEX, we minimize such value extraction by adopting batch execution for orderbook order matching mechanism. In batch execution, orders within a batch are treated equally without prioritization by order time. The only prioritization is the order price, not the order time. It brings healthy competition among arbitrageurs and traders which result in more efficient price discovery of the orderbook. --- # 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.crescent.network/introduction/crescent-dex-legacy/batch-execution.md?ask=&goal= ``` `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.