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

# Providing Liquidity

## Overview

When you provide liquidity on HertzFlow, you deposit USDT into isolated market pools that serve as the counterparty to leveraged traders. In return, you earn yield from trading fees, borrow fees, and trader losses.

It works like this: traders pay fees and borrow your capital to open leveraged positions. When traders lose, the pool grows. When traders win, the pool pays out. Over time, fee income and the statistical edge of the house tend to generate consistent positive returns for LPs.

<figure><img src="/files/TUR1Fn3yNJLocwqImzab" alt=""><figcaption></figcaption></figure>

## Two Ways to Provide Liquidity

{% tabs %}
{% tab title="HertzFlow Liquidity Pool (HzLP)" %}

### HzLP: Market-Specific Pools

Each market has its own isolated liquidity pool. When you deposit USDT, you receive **HzLP tokens** representing your share of that pool.

**How it works:**

* You pick a specific market (e.g., BTC/USD, ETH/USD)
* Your capital only backs trades in that market
* Your returns depend on that pool's fee income and trader PnL
* If the BTC pool has a bad day, your ETH pool deposit is unaffected

**Best for:** LPs who want granular control over which markets they're exposed to.
{% endtab %}

{% tab title="HertzFlow Vault (HzV)" %}

### HzV: Vault Aggregation

Vaults aggregate liquidity across multiple markets that share the same strategy. Your capital shifts automatically between markets based on utilization and fee opportunities.

**How it works:**

* You deposit USDT and receive **HzV tokens**
* The vault allocates your capital across multiple pools
* Rebalancing happens automatically — no manual management needed
* Your returns reflect aggregate vault performance

**Best for:** LPs who want diversified exposure with minimal effort.
{% endtab %}
{% endtabs %}

## Depositing

When you deposit USDT into a pool, you receive HzLP tokens (or HzV tokens for vaults). The protocol automatically splits your deposit 50/50 between long and short collateral reserves, regardless of current open interest.

**Your HzLP/HzV token price:**

```
Token Price = Pool AUM / Total Token Supply
```

As traders pay fees and realize losses, the pool's AUM increases and your tokens become worth more. Conversely, trader profits decrease pool value.

**Deposit limits:** Each pool has a maximum AUM cap to prevent over-concentration:

```
Max Deposit = Max AUM - Current AUM
```

If a pool is near capacity, you'll see the remaining deposit cap in the interface.

## Withdrawing

Withdrawing burns your HzLP/HzV tokens and returns USDT at the current token price. Withdrawals settle **instantly** on-chain — no waiting periods.

However, withdrawal amounts are subject to two real-time constraints that protect remaining LPs and ensure adequate liquidity for active positions. Your effective withdrawal limit is the **lower** of these two checks:

1. **PnL Factor Constraint** — limits withdrawals when traders hold large unrealized profits
2. **Reserve Factor Constraint** — ensures enough liquidity remains for open positions

{% hint style="info" %}
The remaining withdrawal cap is always visible in the pool interface. If it's lower than expected, it usually means traders currently hold large unrealized profits or pool utilization is high.
{% endhint %}

## Automatic Rebalancing

Every deposit is split 50/50 between long and short collateral — the protocol handles this automatically. This ensures the pool can serve both sides without bias, regardless of open interest distribution.

Deposits and withdrawals have **zero price impact fees** — unlike trading actions, your LP operations won't be charged dynamic impact fees.


---

# 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://hertzflow.gitbook.io/hertzflow-docs/liquidity-provision/providing-liquidity.md?ask=<question>&goal=<endgoal>
```

`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.