# 2.1 System Layer Overview

DOR is a composite of several loosely coupled subsystems rather than a single smart contract. Macroscopically, it can be understood as a 3-Tier Architecture with the following layers:

* Execution & Settlement Layer: Implemented as a set of smart contracts on EVM-compatible chains. All swaps, staking, and liquidity movements are finally settled in this layer. Initially deployed on public L1/L2 (EVM), it follows a modular design to be transferable to a Meme Finance Settlement Layer in the form of a rollup or dedicated Appchain in the mid-to-long term.
* Meta-Liquidity & Oracle Layer: Consists of the HLP (Hierarchical Liquidity Pool) structure that aggregates multiple meme assets (Major Memes + Long-tail) into a single logical pool, and a multi-oracle/TWAP-based reference price system driving it. It reallocates capital from the perspective of a meta-pool existing above individual pools, synchronizing scattered price signals across chains/DEXs/pools into a single meta-price system.
* Policy & Accounting Layer: An accounting and policy layer that aggregates the results of swaps, staking, and revenue redistribution and commits them on-chain at regular intervals (daily). Actual asset movements are processed in the Execution Layer, while the Policy & Accounting Layer compresses and summarizes the results into an Integrity Hash + Distributed Storage (IPFS/Arweave link) format, making the meme-economic state at a specific point reproducible using only on-chain data.

As these three layers combine, DOR operates as a meta-ledger aggregating order flow, liquidity, and cash flow across the meme market, beyond the swap interface of individual tokens.

<br>


---

# 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/2.1-system-layer-overview.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.