Skip to main content

​
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.
Liquidity Compounding starts after graduation. Before graduation, the configured share accrues in its own bucket and waits for the graduated pool.

Project liquidity budget

Use the Fee Calculator to estimate how much SOL routes to locked liquidity from a target market cap, volume assumption, and liquidity allocation.

​
How it works

1

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

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

Blank waits for graduation

Execution only runs when the token has a canonical graduated Meteora DAMM v2 pool and Blank-owned position.
4

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.

​
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, and Liquidity Compounding 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 and Fee Status for API details.