# 2. Technical Architecture

This chapter describes the technical structure of the DOR protocol as a multi-layered system to implement the principle of "Many Memes, One Pool."

DOR is designed to function not simply as a DEX with an added liquidity pool, but as a meta-market infrastructure and meta-ledger penetrating the entire meme asset class.

To this end, the protocol is decomposed into the following five axes:

1. Execution & Settlement Layer
2. Hierarchical Liquidity Architecture
3. Reference Price & Oracle Layer
4. Swap & Routing Kernel with Parametric Market-Making
5. On-chain Record & Transparency Protocol

Each axis operates as an independent module but is mutually combined to converge into a single user experience of "Many Memes, One Pool."

{% content-ref url="/pages/khve341qcuVYo1sv1dTQ" %}
[2.1 System Layer Overview](/dor/dor-whitepaper-english/2.-technical-architecture/2.1-system-layer-overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/noA5posR5yFEb8guXWmE" %}
[2.2 Hierarchical Liquidity Architecture](/dor/dor-whitepaper-english/2.-technical-architecture/2.2-hierarchical-liquidity-architecture.md)
{% endcontent-ref %}

{% content-ref url="/pages/dH299VnOc6IN2hncXQVb" %}
[2.3 Reference Price & Oracle Layer](/dor/dor-whitepaper-english/2.-technical-architecture/2.3-reference-price-and-oracle-layer.md)
{% endcontent-ref %}

{% content-ref url="/pages/0BEiptk3TZtDhzvD6CyD" %}
[2.4 Swap & Routing Engine with Parametric Market-Making](/dor/dor-whitepaper-english/2.-technical-architecture/2.4-swap-and-routing-engine-with-parametric-market-making.md)
{% endcontent-ref %}

{% content-ref url="/pages/0FmtOtmfefrvJQG2Z4cS" %}
[2.5 On-chain Record & Transparency Protocol](/dor/dor-whitepaper-english/2.-technical-architecture/2.5-on-chain-record-and-transparency-protocol.md)
{% endcontent-ref %}


---

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

```
GET https://tripleplus-1.gitbook.io/dor/dor-whitepaper-english/2.-technical-architecture.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.