> For the complete documentation index, see [llms.txt](https://crezanetwork.gitbook.io/crezanetwork-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crezanetwork.gitbook.io/crezanetwork-whitepaper/14.-dao-sovereign-pool.md).

# 14. DAO Sovereign Pool

The DAO Sovereign Pool is CREZA’s weekly leadership revenue share—**5% of global deposit turnover** every 7 days.

```mermaid
flowchart TB
    V["7-day global deposit volume"] --> P["5% → DAO vault"]
    P --> S["Sunday 00:00 UTC snapshot"]
    S --> Q["Qualified leaders paid"]
    S --> R["Unearned → next week rollover"]
```

## Settlement schedule

| Item       | Rule                                  |
| ---------- | ------------------------------------- |
| Allocation | 5% of rolling 7-day protocol deposits |
| Snapshot   | **Every Sunday 00:00 UTC**            |
| Payout     | Automatic via rewards engine          |

## Share qualification

**1 DAO share = $2,500 qualified weekly matching volume**

Leaders earn shares based on verified downline matching volume across active legs. Qualification recalculates each cycle.

## Rollover protection

If shares go unearned (partners miss volume targets):

* Funds **do not** return to any corporate wallet
* Unearned allocation **rolls into next Sunday’s pool**

**Next pool = Rollover + (5% × new weekly volume)**

This creates compounding pools for consistently qualified leaders.

## Strategic role

The DAO pool rewards **organizational builders** at the top of the network while remaining mathematically bounded by deposit turnover—not by inflationary token printing.


---

# 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, and the optional `goal` query parameter:

```
GET https://crezanetwork.gitbook.io/crezanetwork-whitepaper/14.-dao-sovereign-pool.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.