> For the complete documentation index, see [llms.txt](https://comm-1.gitbook.io/comm-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://comm-1.gitbook.io/comm-docs/chapter-4-matrix-vault-participation-mechanism-and-compounding-model/yield-aggregator-withdrawal-rules-and-100-recirculating-freezing-tax.md).

# Yield Aggregator Withdrawal Rules and 100% Recirculating Freezing Tax

To prevent short-term speculative capital from creating a destructive "liquidity drain" on the liquidity pool, the COMM protocol has designed a smart yield aggregator combined with a tiered unlock freezing tax mechanism. This transforms the friction of capital inflows and outflows into a long-term moat for the protocol ecosystem.

**1. Tiered Unlock Freezing Tax**

When users apply to withdraw their daily DOGE market-making yield, the system deducts an equivalent value of MMT as a freezing tax from the withdrawal amount, based on the unlock waiting period chosen by the user:

* Instant Unlock: No waiting period; yield is withdrawn immediately to the user's personal wallet, with a deduction of 20% equivalent MMT freezing tax.
* 10-Day Unlock: The yield lock-up period is 10 days, automatically unlocked upon maturity, with a deduction of 10% equivalent MMT freezing tax.
* 30-Day Zero-Loss Unlock: The yield lock-up period is 30 days, fully unlocked to the account upon maturity, with only a 3% low-loss freezing tax deducted.

**2. 100% Internal Recirculation Allocation Architecture**

The freezing tax is not a punitive destruction mechanism by the protocol. Instead, it serves as a system adjustment dividend, with 100% recirculating back into the ecosystem's internal loop. The specific allocation ratios are as follows:\
$$\text{Total Freezing Tax} = 50\\% \text{ Yield Aggregator Compounding} + 30\\% \text{ Governance Node Dividends} + 15\\% \text{ COMM Foundation} + 5\\% \text{ D8 Leader Dividends}$$Plaintext

```
                     [Withdrawal Deducts MMT Freezing Tax]
                                       │
         ┌─────────────────────────────┼─────────────────────────────┐
         ▼                             ▼                             ▼
[50% Recirculated to Yield]   [30% Governance Node]         [15% Foundation Reserve]
[      Aggregator         ]   [     Dividends     ]         [(Market-making hedging]
(Auto-compounding deepens)   (Distributed to nodes)         [  & risk control reserve]
(   liquidity pool       )                                           │
                                                                     ▼
                                                          [5% D8 Leader Dividends]
                                                          (Top network community )
                                                          (     incentives       )
```

Through this design, short-term withdrawal behavior is successfully converted into deeper liquidity pool depth, cash flow replenishment for governance nodes, and long-term incentives for top leaders. This achieves a virtuous economic closed loop where "game-theoretic friction generates adjustment dividends, and dividends automatically recirculate back to the community."


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://comm-1.gitbook.io/comm-docs/chapter-4-matrix-vault-participation-mechanism-and-compounding-model/yield-aggregator-withdrawal-rules-and-100-recirculating-freezing-tax.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.