LP Risks
Market losses, administrator misconduct, and token-authority risks
LP returns depend on token prices, the basket you eventually withdraw, and pool operations. You can lose money while earning trading fees.
Pool creation is permissionless, subject to token and parameter rules. A pool's existence does not mean its creator, manager, or assets have been vetted.
Pool admin and range-manager misconduct
The pool admin can appoint a faulty or malicious range manager and change its operating limits. A manager can move virtual balances and weights in ways that price assets incorrectly. Traders can exploit those quotes through arbitrage, extracting value from the pool and leaving LPs with depleted reserves or a less valuable basket. This can cause severe divergence losses that fees do not offset.
Manager updates do not directly withdraw vault assets, but harmful repricing can still cause permanent LP losses. The contract checks update limits, not whether prices match the market. Small permitted steps can accumulate, and the pool admin can change the limits. Read Range Management before trusting a manager.
Separately, a protocol-level full pause blocks normal withdrawals, and emergency recovery can move vault assets without redeeming LP tokens. Upgrade authority can change program behaviour. See Pool Controls for these powers.
Your basket changes as people trade
When traders buy a token, the pool holds less of it and more of what they paid. Your LP share follows that basket. If the sold asset later rises, you can end up with less value than holding the same original assets.
This difference is called impermanent or divergence loss. The name does not promise recovery, and fees may not offset it.
Virtual liquidity does not remove market risk
Virtual balances set the concentration factor without creating an LP loan, interest bill, or margin-liquidation position. Real reserves still limit payouts. A pool can exhaust one asset, reject trades in that direction, and leave LPs with a different basket.
A higher concentration factor can narrow the range and change real inventory faster; it does not guarantee better returns. Read Virtual Liquidity and Coffer's concentration factor explainer.
Similar assets can still diverge
A stablecoin can depeg, a wrapped asset can lose backing, and an issuer can freeze transfers. In a shared pool, swaps involving a compromised asset can also change or deplete reserves of other assets.
Token authorities and Token-2022 extensions
Token-2022 extensions can give an issuer powers over assets held in a pool. Depending on the mint and the pool's admission policy:
- A freeze authority can freeze the pool's token account, blocking transfers of that asset and potentially preventing LP withdrawals. Classic SPL tokens can also retain this authority.
- A
PermanentDelegatecan transfer or burn that mint's tokens from the pool vault without LP consent, removing assets backing LP tokens. - An initially inactive
TransferHookcan be activated later by its authority and make transfers fail, potentially locking withdrawals.
The contract does check mints and extensions at creation. Creators can relax the default extension blocklist within mandatory protocol rules. The current instruction implementation can accept active hooks when policy permits them and the required accounts are supplied; additional-signer hooks are unsupported. These checks do not remove every issuer power or guarantee future transfer behaviour. Passing creation checks also does not guarantee compatibility with swaps or withdrawals. See Token Extension Policy.
Check before depositing, monitor afterward
Verify the exact mint addresses, pool admin, range manager, manager limits, and each token's mint, freeze, and extension authorities. Inspect the pool's effective extension policy rather than assuming it uses the defaults. After depositing, monitor authority changes, manager updates, token extensions, and pool status. Decide which authorities you trust with your liquidity; these powers can affect your position after the deposit.
Separate performance from fee income
Compare your position with holding the same initial basket, using the same prices and time. For an unchanged starting basket:
pool_position_USD = (your_lp_tokens / total_lp_tokens) × Σ(actual_i / 10^decimals_i × price_i)
hold_basket_USD = Σ(original_amount_i / 10^decimals_i × price_i)
relative_result = pool_position_USD / hold_basket_USD − 1Use LP-owned actual balances, already net of protocol fees. For a real portfolio, separately account for deposits, withdrawals, transaction costs, and entry/exit swaps; this formula does not adjust for cash flows.
A limited example is a fee-free two-token pool with no virtual amplification,
fixed weights, and starting value shares matching those weights. If token T
has weight w and its relative price changes by factor r, after arbitrage:
pool_value / hold_value = r^w / (w × r + 1 − w)This is not a general Coffer loss formula: virtual liquidity, changing weights, fees, or exhausted reserves change the comparison. Displayed fee yield measures neither this result nor total portfolio performance.
Quotes, contracts, and data
Minimum-output settings protect token amounts at execution. They do not guarantee a later USD value or eliminate smart-contract risk. Dashboard data can lag; missing prices can understate TVL and distort annualized yield. See Tracking Pool Activity for interpreting those figures.