# Protocol Owned Liquidity Protocol Owned Liquidity (POL) is all about the protocol taking control of its own liquidity instead of renting it from outsiders. In most DeFi systems, liquidity comes from external providers who chase incentives, but the moment rewards dry up, that liquidity can disappear overnight. With POL, the protocol itself owns the liquidity pools, meaning it doesn’t need to beg or bribe mercenary capital to stick around.

https://rezerve.money/risk The liquidity tab in the risk page gives a full breakdown of the various assets and pools that the protocol owns liquidity with

## Why Should the Protocol Own Liquidity? In short, when the protocol owns liquidity, it owns its future by building stability, sustainability, and resilience that benefit every holder. 1. **Long-term commitment:** When the protocol owns its own liquidity, it no longer has to rely on “rented” capital that disappears the moment incentives dry up. Instead, it creates permanent liquidity that users can always count on. This makes the system far more trustworthy, because markets stay liquid and functional regardless of external conditions. 2. **Revenue**: On top of stability, protocol-owned liquidity is a source of revenue. By holding LP tokens directly, the protocol earns trading fees and yield instead of paying out unsustainable liquidity mining rewards. That income flows back into the treasury, creating a feedback loop that makes the protocol stronger over time. --- # 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-controlled-value-pcv.md?ask= ``` 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.