> For the complete documentation index, see [llms.txt](https://docs.earnpark.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.earnpark.com/earnpark-protocol/economic-model.md).

# Economic Model

### Wrapper Backing

Every circulating wrapper is backed by a reserve of the corresponding underlying asset. For this purpose, the protocol maintains separate principal accounting and holds backing for the entire circulating supply of the wrapper token.

### Reserve Yield

The reserve backing the wrapper does not sit idle. It is deployed through an approved adapter in a venue with instant liquidity and generates yield. This yield **is not distributed to wrapper token holders** and **does not convert the wrapper into a yield-bearing token**. Instead, reserve yield is directed to a separate protocol address as a revenue/backstop stream.

> **The economic logic is simple:** reserve yield is protocol revenue, strategy yield is strategy users' revenue, and the wrapper token is the base transport layer — not a yield-bearing asset.

### Strategy Economics

Each strategy has its own economics: a separate share token, its own exchange rate, its own redemption fee, its own cooldown, and its own limits on external allocations. User yield arises only at this level.


---

# 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:

```
GET https://docs.earnpark.com/earnpark-protocol/economic-model.md?ask=<question>
```

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.
