~/blog/how-to-check-if-liquidity-is-burned-on-solana
How to Check if Liquidity Is Burned on Solana
Find the pool's LP mint, read its supply against the pool's own record of LP issued, and tell a real burn from a withdrawal. No code needed.
To check if liquidity is burned on Solana, find the LP mint of a Raydium AMM v4 or PumpSwap pool, read its current supply on an explorer such as Solscan, and compare it with the LP the pool records as issued. The gap is LP destroyed rather than redeemed, and the liquidity behind it can no longer be withdrawn.
This is an evergreen instrument piece, not a news item. This desk read Shyft’s Raydium burn-percentage page and pump.fun’s two public program documents, the Pump program and PumpSwap READMEs, on 23 September 2026. Nothing here was tested on a live pool.
What burned liquidity means on Solana
When someone adds liquidity to a Raydium pool, lpMint tokens are minted to them, and anyone removing liquidity needs those tokens back, per Shyft’s Raydium burn-percentage page. If they are burnt, Shyft writes, the liquidity is locked inside the pool and cannot be withdrawn. The LP token is the receipt; burn the receipt and the deposit stays at the carnival for good.
The catch is that a normal withdrawal also burns LP. PumpSwap’s withdraw instruction takes an lpTokenIn amount and burns exactly that many LP tokens while paying out the base and quote tokens. A falling LP supply alone proves nothing.
How to check if liquidity is burned on Solana, step by step
Step 1: find the pool and its LP mint
Start from the token, find its pool on a screener such as DEX Screener, and open the pool address on the explorer. On Raydium AMM v4 the pool account carries an lpMint field, per Shyft. On PumpSwap the Pool account stores lp_mint, which pump.fun’s docs say can also be derived from the seeds “pool_lp_mint” and the pool key.
Step 2: read the LP mint’s current supply
Open the LP mint itself, not the memecoin’s mint, and note its current supply and decimals. Shyft divides every figure by the mint’s decimals before comparing, and so should you.
Step 3: read the pool’s own record of LP issued
This is the number that makes the check work. On Raydium AMM v4 it is the pool’s lpReserve field. On PumpSwap it is lp_supply, which the PumpSwap README defines as the total supply of the LP mint without burns and lock-ups, so the pool can tell LP burnt by users directly from LP burnt by the withdraw instruction. The README links an example Pool account’s data on Solscan; whether a given explorer shows these fields decoded for your pool is something to confirm on the page, not assume.
Step 4: apply the Raydium frontend formula
Shyft’s code, which it credits to Raydium’s frontend, runs three lines:
- maxLpSupply = max(actualSupply, lpReserve - 1)
- burnAmt = maxLpSupply - actualSupply
- burn % = burnAmt / maxLpSupply x 100
The formula is documented for Raydium AMM v4 only. On PumpSwap the same comparison, lp_supply against current mint supply, follows from pump.fun’s definition of the field, but that is this desk’s reading, not a published formula.
Step 5: tell a burn from a withdrawal on the transaction page
Open the transaction that moved LP supply. A withdrawal burns LP and sends pool tokens back to the wallet in the same transaction. A standalone Burn instruction destroys LP and pays out nothing. The mechanics of reading a Burn instruction are in How to Verify a Token Burn on Solscan.
Which pools the check works on
| Pool type | LP mint recorded in | Pool’s record of LP issued | Status |
|---|---|---|---|
| Raydium AMM v4 | lpMint on the pool account | lpReserve | Sourced: Shyft |
| PumpSwap, including pump.fun graduates, whose migrated LP the Pump program README says is burnt | lp_mint on the Pool account | lp_supply, excluding burns and lock-ups | Sourced: pump.fun docs |
| Raydium CPMM | Not checked | Not checked | Unverified |
| Raydium CLMM | Not checked | Not checked | Unverified |
The CPMM and CLMM rows are blank because the Raydium documentation page tried during this desk’s research returned 404. Carrying lpReserve across to those pool types would be a guess.
Does a burned LP make a coin safe?
No. Burned LP answers one question, whether a withdrawal path exists for that share of the pool. It says nothing about who holds the supply, which Bubblemaps Against RugCheck covers, or whether new tokens can be minted, the subject of How to Check if Mint Authority Is Revoked on Solscan.
Questions readers ask
Can burned liquidity be removed? Not by redeeming the burned LP tokens, because they no longer exist. Shyft’s Raydium page says that if the lpMint tokens are burnt, the liquidity is locked inside the pool and cannot be withdrawn. The limit is the burned share: LP tokens still sitting in a wallet can, through the withdraw instruction the docs describe, be redeemed for their slice of the pool.
Does pump.fun burn liquidity? pump.fun’s own program documentation says so: when a coin hits a certain market cap, the bonding-curve liquidity migrates to PumpSwap and the LP tokens received from the PumpSwap pool are then burnt. The same documentation describes the migrate instruction as permissionless and idempotent. The documentation’s word is not a receipt; the pool’s LP mint supply is the thing to check.
Is burned liquidity the same as locked liquidity? No. A burn destroys the LP tokens, so nobody holds the claim on the liquidity behind them. A lock leaves the tokens in existence, held somewhere under terms of their own. PumpSwap’s documentation treats the two as separate categories: its lp_supply field is the LP supply without burns and lock-ups. Screeners sometimes blur them into one badge.
The check tells you whether the pool can be emptied through the front door; it does not tell you whether anyone should be standing in the queue. This desk reads the pool accounts because they are the ritual’s paperwork, and it holds none of the coins. Memecoins are extremely high risk and frequently go to zero; nothing here is financial advice, and the one recommendation on offer is to read lp_supply before you believe the badge.