> 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/13.-earning-caps-2x-3x.md).

# 13. Earning Caps (2X / 3X)

Caps protect vault solvency while allowing meaningful returns for participants.

```mermaid
flowchart TB
    P["Active Principal Deposit"] --> PASS["Passive cap 200% (2×)<br/>Daily yield up to 1.25%/day"]
    P --> ACT["Active cap 300% (3×)<br/>Direct + levels + leadership"]
```

## Passive yield cap — 2×

Non-active stakers earn daily protocol yield until total returns reach **200% of principal**:

**Max passive = Principal × 2.0**

After 2× is reached, yield pauses until the user tops up or re-stakes.

## Active working cap — 3×

Builders earning referrals and level income are capped at **300% of active principal**:

**Max active = Principal × 3.0**

Direct incentives, generation overrides, and leadership bonuses count toward this ceiling.

## Cap exemptions

These streams are **not limited** by the 3× active cap:

| Stream                     | Why exempt                           |
| -------------------------- | ------------------------------------ |
| **Milestone rank rewards** | One-time organizational achievements |
| **DAO Sovereign Pool**     | Weekly leadership revenue share      |

## Re-activation

When a cap is hit, payouts pause automatically. Users **renew or top up principal** to resume earning on new volume.


---

# 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/13.-earning-caps-2x-3x.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.