> For the complete documentation index, see [llms.txt](https://paragon-protocol.gitbook.io/paragon-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://paragon-protocol.gitbook.io/paragon-protocol/core-products/protocol-owned-liquidity.md).

# Protocol-Owned Liquidity

### Base Swap Fee

Each trade includes a **0.20% fee**:

* **0.17% → Liquidity Providers (LPs)**
* **0.03% → Treasury Vault (POL engine)**

***

### What This Means

* LPs earn consistent swap fees
* the protocol accumulates value
* liquidity becomes increasingly protocol-controlled

***

### How POL Works

The Treasury Vault:

* collects the 0.03% fee share
* accumulates assets over time
* buys XPGN from the market
* pairs it with assets (e.g. USDT / BNB)
* creates liquidity positions

***

👉 These LP tokens are:

* owned by the protocol
* not withdrawable by external users
* managed through governance

***

### Result

Paragon progressively becomes its own liquidity provider, strengthening its markets over time.

***

### Why POL Matters

#### 📈 Stronger Token Support

* continuous XPGN buy pressure
* protocol-aligned demand

***

#### 💧 Deeper Liquidity

* permanent LP positions
* reduced reliance on short-term liquidity

***

#### 🛡️ Market Stability

* improved execution during volatility
* tighter spreads
* reduced slippage

***

#### 🔁 Flywheel Effect

More volume →\
more fees →\
more XPGN buybacks →\
more POL →\
better execution →\
more volume

***

### Treasury Vault

The Treasury serves two core functions:

***

#### 1. Liquidity Engine (POL)

* builds and maintains protocol-owned liquidity
* manages LP positions
* adjusts allocations over time

***

#### 2. Protocol Support Layer

* supports core protocol operations
* funds ecosystem development
* enables long-term system growth

***

👉 All treasury activity is governed on-chain.

***

### Governance (veXPGN)

POL decisions are controlled by:

* veXPGN holders
* DAO proposals
* timelocked execution

***

Governance can adjust:

* buyback cadence
* liquidity allocation
* treasury parameters

***

### Transparency

All treasury activity is:

* on-chain
* auditable
* publicly verifiable

Future dashboards will display:

* fees collected
* XPGN buybacks
* POL positions
* treasury balances

***

### Key Notes

* POL does not replace external liquidity
* LPs continue to earn standard swap fees
* protocol behavior is designed around accumulation, not distribution

***

### Current Parameters (Testnet)

* base fee: **0.20%**
* LP share: **0.17%**
* treasury (POL): **0.03%**

***

### FAQ

**Does POL compete with LPs?**\
No.\
LPs earn fees from trading activity, while POL strengthens long-term liquidity.

***

**Where does XPGN demand come from?**

* trading fees
* treasury buybacks
* ecosystem activity

***

**Can POL be changed?**\
Yes — through governance.

***

### Summary

Protocol-Owned Liquidity enables:

* permanent liquidity growth
* sustained token demand
* stronger execution conditions

POL transforms Paragon into a system that continuously reinvests trading activity into its own liquidity base.


---

# 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://paragon-protocol.gitbook.io/paragon-protocol/core-products/protocol-owned-liquidity.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.