> For the complete documentation index, see [llms.txt](https://docs.emdx.io/emdx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emdx.io/emdx/emdxv2/emdxv2-protocol.md).

# EMDXv2 Protocol

## Order Book-Based DEX <a href="#id-1892" id="id-1892"></a>

EMDX offers a sound DEX Limit OrderBook- based exchange, currently running on Arbitrum Network, BASE and Optimism.

As a decentralized perpetual futures exchange, EMDX leverages the robustness of a Limit Order Book to offer users unparalleled liquidity and an experience akin to centralized finance (CeFi) platforms.&#x20;

EMDX is built on the foundation of Orderly Network's cutting-edge, omnichain, permissionless exchange protocol.

This collaboration is a significant leap forward in our continuous efforts to enhance the EMDX platform and provide our users with an unmatched trading experience while paving the way to become a multichain protocol.

{% hint style="info" %}
**Documentation Update:** We are diligently working on the EMDXv2 documentation to ensure you have all the resources you need for an optimal trading experience. The comprehensive guide will be available soon. We appreciate your patience and are excited to support your journey on EMDXv2.
{% endhint %}

## Highlighting the features of the EMDX orderbook-based venue. <a href="#id-2f75" id="id-2f75"></a>

Among a number of institutional-grade tools and services, traders will find on this venue a user-friendly and CeFi like platform to trade a massive amount of assets (30 different markets will be available at launch time), full of professional widgets and user-centric market data delivery.

## Adding an Orderbook Venue for perps <a href="#id-1e8a" id="id-1e8a"></a>

Algonside with our vAMM- based exchange for perpetuals on traditional assets, EMDX users will enjoy an CLOB based venue to trade perps. According to our roadmap, we´ll be firstly launching perps on crypto assets, and gradually including traditional assets on the CLOB venue.

## Markets <a href="#b19f" id="b19f"></a>

EMDX initial product offering consits of 30 different cryptocurrencies and tokens, among which users will find native currencies from top networks and the most iconic tokens of the industry.

Available markets will be increased steadily as the platform stabilizes and get traction.

## Massive Liquidity <a href="#id-1892" id="id-1892"></a>

Key to EMDX’s allure is its provision of liquidity, a cornerstone of successful trading platforms. With a robust liquidity layer in place, liquidity is assured, facilitating seamless transactions and minimizing slippage.<br>

## CEX-Level Performance: **Trading Speed and Low Latency** <a href="#id-7c50" id="id-7c50"></a>

Designed to meet the needs of HFT and institutional traders, EMDX offers low latency trading. Leveraging Orderly’s high-performance matching engine will complement this, ensuring rapid execution and a competitive edge in the market.

##


---

# 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.emdx.io/emdx/emdxv2/emdxv2-protocol.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.
