# 2.2 Hierarchical Liquidity Architecture

DOR's core structure is a Hierarchical Liquidity Architecture that classifies externally inflowing meme assets multi-dimensionally according to capital purpose, tenor, and risk profile, and then aggregates them back into the Main Supply Pool (MSP).

This entire structure is called HLP (Hierarchical Liquidity Pool).

Intuitively, DOR does not design "one pool" but implements a dual characteristic of "a single pool externally, a multi-layered structure internally" by combining operation-specific pools (MOP/SOP/IRP) and a dual supply/reserve structure (MSP/RP).

#### 2.2.1 Operation Pool Classification: MOP / SOP / IRP

All meme assets flowing into DOR from external wallets are automatically classified into one of the following three categories of operation pools at the time of entry according to protocol rules.

The ratio and operational purpose of each pool are fixed by on-chain parameters and can be gradually adjusted through governance.

* MOP (Mid–Long Term Operation Pool) – 30%: A pool aiming for long-term positions such as external staking for over 12 months and low-risk DeFi strategies. Only strategies meeting certain criteria, such as annual yield, collateral/insurance structure, and on-chain transparency, are incorporated. It serves as the system's long-term alpha engine.
* SOP (Short Term Operation Pool) – 68.5%: A pool responsible for activities requiring immediacy and elasticity, such as real-time swaps, liquidity provision, and farming. Strongly connected to the MSP/RP structure, SOP operates as a real-time market-making engine supplying real-time liquidity to the main pool during swap demand surges.
* IRP (Interest Reserve Pool) – 1.5%: A reserve pool for paying promised interest and various incentives in deposit/staking products. It follows the basic principle of conservative operation focused on long-term bonds and stable assets, corresponding to the interest & insurance buffer managed by the DAO Treasury.

Consequently, MOP functions as a long-term alpha generator, SOP as a real-time market maker, and IRP as a stable reward payer—three engines with different timescales. Their combination artificially extends and amplifies the residence time and capital efficiency of meme liquidity.

#### 2.2.2 MSP / RP Dual Structure: Main Supply Pool & Reserve Pools

Each operation pool (MOP/SOP/IRP) is further decomposed into two layers: Main Supply Pool (MSP) and Reserve Pools (RP).

* Main Supply Pool (MSP): The primary liquidity pool directly used for swaps, liquidations, and immediate execution. The "single pool" seen by users and routing engines is actually a logical union of multiple MSPs, exposed as a single pool on the frontend.
* Reserve Pools (RP): Secondary liquidity reservoirs connected to each MSP. They perform auto-backstopping according to priority rules when MSP balances fall below a certain threshold. Conversely, they absorb excess liquidity during market overheating or surplus liquidity periods to mitigate pool risk.

Multiple RPs do not exist as isolated islands but eliminate tail-risk (where specific RPs are depleted or become excessively bloated) through a periodic Equal Rebalancing mechanism.

Users obtain the experience of interacting with a single pool having a similar slippage curve regardless of chain, asset, or time zone, without needing to recognize this complex backend structure.

In other words, HLP aims for a structural asymmetry: "Externally a single pool, internally a hierarchical liquidity engine."

<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.2-hierarchical-liquidity-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.