> ## Documentation Index
> Fetch the complete documentation index at: https://blank.build/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Liquidity Compounding

> How Liquidity Compounding routes part of creator-side trading fees into permanently locked graduated liquidity.

# Liquidity Compounding

Liquidity Compounding lets a creator route part of their creator-side trading fees into a dedicated liquidity bucket. After graduation, Blank uses that bucket to add paired liquidity to the token's Meteora DAMM v2 position and permanently lock the added liquidity.

<Info>
  Liquidity Compounding starts after graduation. Before graduation, the
  configured share accrues in its own bucket and waits for the graduated pool.
</Info>

<Card title="Project liquidity budget" icon="calculator" href="/docs/start-here/fee-calculator">
  Use the Fee Calculator to estimate how much SOL routes to locked liquidity
  from a target market cap, volume assumption, and liquidity allocation.
</Card>

## How it works

<Steps>
  <Step title="Creator sets an allocation">
    At launch, or later from the creator dashboard, the token controller chooses
    what share of creator-side fees goes to Liquidity Compounding.
  </Step>

  <Step title="Fees accrue in a liquidity bucket">
    The fee-splitter books that share into `liquidity_claimable`. This bucket is
    separate from creator payouts, staking rewards, and buybacks.
  </Step>

  <Step title="Blank waits for graduation">
    Execution only runs when the token has a canonical graduated Meteora DAMM v2
    pool and Blank-owned position.
  </Step>

  <Step title="The batch adds locked liquidity">
    Blank swaps part of the SOL bucket into the project token, pairs it with
    SOL, adds liquidity, and permanently locks the added liquidity.
  </Step>
</Steps>

## Public signals

Completed batches are visible on public token surfaces:

* an `LP+` chart marker
* fee status totals for SOL injected into liquidity
* total project-token amount paired into liquidity
* total Meteora liquidity units permanently locked

## Rules

* Allocation can be set at launch.
* Allocation can be increased later by the current token controller.
* Allocation cannot be reduced or turned off after launch.
* Liquidity Compounding executes only after graduation.
* The default execution threshold is `0.1 SOL` in the liquidity bucket.
* Staking, Auto Buyback and Burn, Liquidity Compounding, and Price Prediction allocations share the same creator-side fee budget and cannot exceed 100% combined.
* Failed or delayed batches do not stop trading; fees remain in the liquidity bucket for retry.

## Developer fields

Use `liquidityCompounding.shareBps` in the launch payload to enable the feature at launch.

Use `GET /api/v1/token/{mint}/fees` to read:

* `liquidity_compounding_share_bps`
* `total_liquidity_compounded_earned`
* `vault_liquidity_compounding`
* `pending_liquidity_compounding`
* `distributed_liquidity_compounded`
* `liquidity_compounded_token_a_raw`
* `liquidity_compounded_liquidity`

See [Launch Tokens](/docs/for-developers/launch) and [Fee Status](/docs/for-developers/fee-status) for API details.