# Protocol Owned Supply

Protocol Owned Supply (POS) refers to the portion of a token’s circulating supply that is directly controlled by the protocol itself, rather than by external users or investors.

<figure><img src="/files/eqWEW6z4CZiS8DZvD77P" alt=""><figcaption><p><a href="https://rezerve.money/risk">https://rezerve.money/risk</a> The RZR supply that the protocol owns and has deployed into liquidity can be seen in the supply analysis section in the risk page.</p></figcaption></figure>

This creates a strategic reserve of assets that strengthens the protocol’s stability, sustainability, and long-term alignment with its community.

This supply can take multiple forms.

* The protocol may hold tokens as lending collateral, backing borrowing activity and liquidation mechanics.
* It can also own LP tokens, giving the protocol direct exposure to liquidity pools and ensuring that deep, stable liquidity exists for its users.
* In addition, supply can be deployed in staked positions such as Pendle markets, where it accrues yield and compounds over time.
* Finally, treasury holdings provide reserves that can be tapped for emergencies, growth incentives, or governance participation.

In an ideal scenario, the protocol should deploy all of it's idle RZR supply into lending markets or liquidity markets.

## Why Should the Protocol Own Supply?

A protocol that owns part of its own supply is directly invested in its own future. Unlike external actors who may be driven by short-term profit, the protocol always acts in its own long-term best interest and by extension, in the best interest of its holders.

When the protocol holds supply, it becomes both the architect and the stakeholder, ensuring that decisions are guided by sustainability, stability, and growth rather than by external speculation.


---

# Agent Instructions: 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://rezerve.gitbook.io/protocol/mechanics-rzr/protocol-driven-buybacks-pds/protocol-owned-supply.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.
