# 0. Executive Summary {% hint style="info" %} This chapter presents the core concept of the DOR protocol at a glance. Starting from the structural failures of the meme market, it summarizes how DOR implements liquidity aggregation, stabilization, and re-circulation under the principle of "Many Memes, One Pool." {% endhint %} Meme assets exhibit endogenous beta driven by the attention economy, yet today's market is defined by liquidity fragmentation, price distortion, and abnormal volatility clustering. As a result, quoted depth and execution elasticity remain structurally weak, while generated economic surplus (fees, yield, and reserve returns) leaks out instead of accumulating inside a governance-controlled framework. DOR addresses this by linking major meme ecosystems, such as DOGE, SHIB, and PEPE, into a single aggregated liquidity surface. It is designed not as a single DEX pool, but as a meta-market infrastructure. The protocol operates through four coordinated engines: * A reference-price framework (Oracle x TWAP) with parametric market-making. * A hierarchical liquidity architecture (main supply, reserve, operation, and interest-reserve layers). * A synthetic yield layer. * Composable incentives that enable cross-meme participation. Together, these engines improve liquidity provisioning, price stability, and capital retention. Under the "Many Memes, One Pool" principle, DOR redesigns fragmented meme markets into a stable, capital-efficient, and culture-native structure. In this model, memes are no longer purely disposable speculative waves; they become sustainable culture-financial assets jointly owned and operated by communities. This white paper presents DOR's technical architecture, economic model, and implementation strategy. The solution integrates blockchain primitives to deliver a secure, scalable, and user-oriented infrastructure for meme ecosystems. --- # 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://dormanagement.gitbook.io/dormanagement-docs/0-summary.md?ask= ``` 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.