> For the complete documentation index, see [llms.txt](https://zunamilab.gitbook.io/zunami-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zunamilab.gitbook.io/zunami-docs/protocol-overview/revenue-streams.md).
# Revenue Streams
The entire income generated by the protocol — including the 20% yield from zunStables collateral and the 15% performance fee from APS — is distributed to ZUN stakers.
To stimulate liquidity influx and engage the interests of ZUN stakers, a portion of ZUN emissions is allocated to incentivize pools that utilize zunStables and for locking zunStables in APS.
***
## Example: Revenue Distribution to ZUN Stakers
Let’s break down how income is generated and distributed to ZUN stakers using a simple scenario:
### 💰 Assumptions:
* **Total Value Locked (TVL):** $100,000,000
* **Average yield from collateral:** 15% annually
* **Performance fee distributed to ZUN stakers:** 20% of the total yield
***
### 🧮 Step-by-step Calculation:
1. **Total protocol income:**
```
$100,000,000 * 15% = $15,000,000 per year
```
2. **Share allocated to ZUN stakers (via performance fee):**
```
$15,000,000 * 20% = $3,000,000 per year
```
***
### ✅ Final Result:
**ZUN stakers receive $3,000,000 per year** from the protocol’s yield, assuming a $100M TVL and a 15% average return on collateral.
This structure aligns incentives: the more TVL and collateral efficiency the protocol achieves, the more income flows to ZUN stakers.
*\*This example does not include the additional income for ZUN stakers from the APS performance fee.*
---
# 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://zunamilab.gitbook.io/zunami-docs/protocol-overview/revenue-streams.md?ask=&goal=
```
`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.