# Architecture & Concepts

## Mechanics & Architecture

RemusDEX matches buy and sell orders through an on-chain orderbook. Every interaction—from placing orders to confirming executions—happens within the Starknet framework. As trading activity rises, Starknet’s high throughput can handle the surge. This not only benefits RemusDEX users but also highlights Starknet’s ability to support elevated transactions per second (TPS), potentially enhancing its valuation and ecosystem traction.

<figure><img src="/files/p0UbrQJoE776hqdn7Wq7" alt=""><figcaption></figcaption></figure>

**Key** **Points**

* **Precision** **and** **Control**: Limit orders let you specify exact prices, appealing to traders used to centralized exchanges.
* **Full** **Transparency**: On-chain execution ensures that all trades remain auditable.

Ecosystem Growth: RemusDEX activity boosts Starknet’s composability and total transaction volume.

## Concepts

### Market Creation

* A **MarketConfig** is defined by base token, quote token, tick size, lot size, trading status, and fee settings.
* Only the contract owner can add or update market configurations.

### Order Types & Flow

* **Maker Orders**: Placed into the orderbook if not immediately filled.
* **Taker Behavior**: If a new order crosses the spread, it executes as a taker.
* **IOC**: Immediate fill or partial fill, then cancel leftover.
* **Post**: Reverts if the order would match on submission.
* **Basic**: Partial fill if crossing, then rest is posted as a maker.

### User Orders & Limitations

* A user can hold **up to 200 active orders** across all markets. Once fully or partially filled and closed, the slot is freed.

### Claiming Matched Funds

* Proceeds for matched orders are tracked in the DEX contract.
* Users must explicitly call `claim(token, amount)` to withdraw.


---

# Agent Instructions: 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:

```
GET https://remusdex.gitbook.io/remusdex-docs/architecture-and-concepts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.