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

# Welcome to Parity DEX

#### The Native Liquidity Layer for Monad

**Every trade on Parity strengthens Monad.**

Parity is the native liquidity layer for Monad, designed to align the interests of traders, liquidity providers, and the broader ecosystem. Unlike traditional DEXs that extract value from their host chains, Parity contributes back, allocating 10% of all trading fees to the Monad Eco-Reserve.

#### Core Features

**Monad Catalyst**

10% of all trading fees flow to the Eco-Reserve, acquiring $MON and deploying liquidity for ecosystem projects. This creates persistent demand while deepening liquidity across the network.

**Next-Gen v(3,3)**

Parity takes the next step beyond ve(3,3) with an options-based emission system. Every reward requires an active decision before it becomes liquid value, eliminating passive extraction entirely.

**Dual Reserve System**

* **Value Reserve**: USDC from option exercises, distributed to voters
* **Eco-Reserve**: MON accumulation from trading fees, supporting ecosystem partners

### <mark style="color:$primary;">Parity, where Liquidity Aligns with Monad</mark>


---

# 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.parity.exchange/welcome-to-parity-dex.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.