> For the complete documentation index, see [llms.txt](https://docs.evedex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.evedex.com/key-features-and-components/trading-platform-and-matching-engine/off-chain-orderbook.md).
# Off-chain Orderbook
An off-chain order book (Matcher) system manages buy and sell orders outside the blockchain. This approach follows the same principle as centralized exchanges, enabling faster order processing and matching. By handling order management off-chain, EVEDEX achieves higher performance and lower latency, which are critical for efficient trading.
**Matcher’s** **responsibilities** **include**:
* **Order Matching:** Matches buy and sell orders and places them in the order book.
* **Essential Risk Management:** Ensures orders meet risk criteria before execution.
* **Real-Time Updates:** Provides live data on the state of the order book and order matching events via WebSocket.
We provided a detailed description of the Matcher’s specifications on this [page](/key-features-and-components/trading-platform-and-matching-engine/off-chain-orderbook/matching-engine-overview.md).
#### Interaction Between EVEDEX Core Engine and Matcher
The exchange’s backend communicates with the Matcher through API requests and Websocket. Here’s the workflow:
1. A user submits an order request signed by his private key.
2. The backend performs basic feasibility checks, such as verifying sufficient funds, ensuring the order meets minimum position requirements, and verifying the wallet’s signature.
3. The backend forwards the validated request to the Matcher.
4. The Matcher verifies the order signature, processes it, updates its status (e.g., executed, partially executed, pending, or canceled), and records it in the database.
5. The updated order status is relayed back to the backend.
6. The filled order will be recorded on the blockchain based on the demand from the backend.
---
# 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.evedex.com/key-features-and-components/trading-platform-and-matching-engine/off-chain-orderbook.md?ask=&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.
.png?alt=media){kind=spacer}