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

# Dev-Overview

## <mark style="color:purple;">Engineered for Performance, Scalability, and User Experience</mark>

Our protocol’s backend architecture is meticulously designed to deliver a high-performance, scalable, and developer-friendly trading environment. By leveraging advanced offchain and onchain mechanisms, we ensure minimal latency, gas efficiency, and robust data integrity, catering to the needs of both traders and developers building on our platform.

* **Fast Settlements:** Queue-based, offchain processing with message queues minimizes onchain delays, using batching for efficiency.
* **Gasless Ops:** EIP-2612 Permit for deposits, ECDSA signatures for other actions—zero gas for users via relayers.
* **RMM Pricing:** Price publishers sync CEX data, mirrored onchain with automated market-making calculations (e.g., CPMM models).
* **Volatility Tools:** Real-time monitoring using metrics like standard deviation, with APIs for custom strategies.


---

# 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.aark.digital/architecture/dev-overview.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.