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

# Why Monad

### Decentralization & Performance Without Compromise&#x20;

As a Monad-native DEX, our mission is to deliver the speed, interactivity, and cost-efficiency users expect from centralized platforms *without sacrificing the decentralization and transparency that define DeFi*. This is exactly why we chose Monad.

### Performance that unlocks new UX&#x20;

Traditional EVM chains are limited by single-threaded execution and consensus-execution coupling. This restricts throughput and drives up gas fees during peak demand. These become major UX killers for active trading environments.

Monad changes the game with:

* 10,000 tps throughput
* 500ms block times
* 1-second finality

This enables a CEX-like experience with instant trade confirmations, low latency, and negligible transaction costs, even for complex smart contract interactions. For a DEX, that means supporting **order books, real-time trading UIs**, and **power users** without breaking a sweat.

### Ethereum compatibility, no tradeoffs&#x20;

Monad is fully EVM-equivalent and bytecode-compatible, meaning:

* All existing Solidity contracts work out of the box
* No changes needed for address formats, signatures, or wallets

This lets us reuse the existing Ethereum DeFi stack while building something fundamentally more performant.

### Parallel & pipelined execution: a new architecture for scalable DeFi&#x20;

Monad introduces **parallel execution** and **superscalar pipelining** at the VM and consensus layers:

* **Parallel execution** means Monad can run multiple transactions across cores while preserving the exact same serial ordering which is essential for DEXs where execution determinism matters.
* **Pipelined consensus and execution** means validation doesn't block throughput, unlocking much higher gas limits and execution budgets per block.

This architectural shift allows us to build features like:

* Fully onchain **matching engines**
* **High-frequency strategies** or social trading without congestion
* **Granular analytics and audits**, thanks to faster state access and finality

### Decentralized, credibly neutral&#x20;

Most high-performance chains today cut corners: centralized sequencers, geographic constraints, or high hardware requirements. Monad, by contrast, is designed to **preserve decentralization:**

* Proof-of-Stake & pipelined BFT consensus (MonadBFT)
* Anyone can run a full node with commodity hardware
* Deterministic state transitions and re-execution guarantees

For a permissionless trading venue, this is non-negotiable. It ensures no one can censor transactions, manipulate ordering, or gain unfair advantages.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.monday.trade/introduction/why-monad.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
