RugSignal
Menu

Meteora DLMM liquidity: who can pull it, and how to check

How liquidity in a Meteora DLMM pool is owned through position accounts, why there is no LP token to burn, and how RugSignal measures each wallet's withdrawable share.

RugSignal editorial notes · Published · Updated · Source-based, not investment advice.

There is no LP token to burn

A Meteora DLMM pool organizes liquidity into discrete price bins. Liquidity providers do not receive a fungible LP token; each deposit lives in a position account owned by one wallet, holding shares of specific bins. That is why the familiar check "LP burned or locked" does not apply: the question is which wallets own positions, how much of the pool they hold, and whether any position is time-locked.

Why it matters for a new token

Many token launches seed a DLMM pool from a single wallet. Whoever owns those positions can remove the liquidity in one transaction, leaving holders with nothing to sell into. A pool spread across many independent providers is harder to drain at once. Neither case predicts intent: a team can hold its own pool legitimately, and many providers can still leave together.

How RugSignal measures it

RugSignal enumerates every position of the pool from the DLMM program, including positions widened beyond 70 bins, and reads the bins they cover. The map counts as complete only when, for every bin, the positions' shares add up exactly to the bin's liquidity supply, so no unseen owner can hold liquidity there. Each position is valued at its bins' own prices. The report then lists the wallets with the largest withdrawable share and how much sits in positions locked for at least 30 more days.

How the result is scored

If at least 90% of the pool's value is locked 30+ days, liquidity control passes. If one wallet can withdraw half or more, it is a warning. If the verified launcher of the token holds 10% or more in positions it can withdraw now, it is the critical case. Otherwise the report states the largest single withdrawable share. Unclaimed fees are excluded, and bins shared with limit orders are left unattributed rather than guessed.

What stays unresolved

Very large pools (more than 400 positions), pools whose liquidity changed while being read, and bins with substantial limit-order funds are reported as unresolved with the specific reason. A complete owner map shows who can withdraw, not how much you could sell: price impact still depends on depth around the active bin, so use a size-specific quote before trading.

Sources and further reading

Official protocol documentation explains capabilities; it does not certify an individual token. RugSignal-specific statements describe our current implementation.

Continue your research

Check a Solana token