Liquidity-pull scams: depth is only durable when the position is not removable

The short answer

A liquidity-pull scam occurs when a project presents market depth as a durable basis for trading while a controller retains the ability to withdraw the pool reserves, then uses that ability to impair holders' exits and extract the valuable side of the pair. The decisive object is the liquidity claim—not the project wallet label or the pool's current dollar display.

In constant-product pools, liquidity ownership is commonly represented by fungible LP tokens. In concentrated-liquidity designs, each provider controls one or more positions with chosen price ranges, often represented by NFTs or position-manager records. A lock, burn, or escrow must be matched to the exact instrument and pool before it means anything.

Resolve the market before inspecting the lock

Save chain, DEX and program version, pool address, both token addresses, fee tier, creation transaction, reserves, and current active liquidity. A token can have several pools with different quote assets and owners. Locking one thin pool does not protect the deeper pool that traders actually route through.

Verify whether the interface shows pool reserves, total value, active concentrated liquidity, or a token-wide aggregate. Use a current intended-size quote and the depth and exit-capacity workflow to translate the pool state into executable output.

Identify the instrument that controls withdrawal

• Fungible LP token: a proportional claim on a pool; ownership, supply, burns, and locker deposits can be traced like other tokens.
• Concentrated position: a claim with its own lower and upper price bounds; only in-range liquidity is active for current swaps.
• Program-owned position: a launchpad, vault, farm, or locker may custody the claim while separate rules determine who can withdraw it.
• Composite exposure: several positions, pools, or chains may produce the visible depth while only some are locked.

Trace the position ID or LP mint from pool initialization to its current owner. Calculate the locked, burned, team-held, and independently held shares against total liquidity supply. Do not infer ownership from the wallet that originally funded the token side.

“Locked” has protocol-specific mechanics

A credible lock requires the exact LP instrument to be held by an immutable burn destination or a verified locker whose program and live state prevent early withdrawal. Record locker address and program, beneficiary, amount, percentage, start, unlock, extension and transfer rights, emergency paths, and whether the locker or underlying pool is upgradeable.

Raydium's Burn & Earn illustrates why labels need decoding. Its official documentation says the LP token or position NFT moves into program-owned escrow and cannot be withdrawn, while a transferable Fee Key NFT preserves the right to claim trading fees. For a concentrated position, the range still matters: a permanently locked position outside its active range does not provide current executable depth.

A pull is visible as a position and reserve event

Identify the decrease-liquidity, remove-liquidity, burn, collect, close-position, or protocol-specific instruction. Reconstruct the position before and after, amounts of both tokens returned, recipient accounts, remaining pool reserves, active liquidity, and subsequent transfers, swaps, bridges, or exchange deposits.

The valuable quote asset may be withdrawn directly, or the operator may first trade project inventory against the pool and then remove what remains. Preserve transaction ordering and use entity evidence before combining recipients. The withdrawal itself is direct evidence; who benefited and whether it was deceptive require the surrounding ownership, disclosure, and flow record.

Not every liquidity decline is a pull

• Price movement: AMM reserve composition and USD value can fall even when no LP claim is redeemed.
• Out-of-range liquidity: a concentrated position can become inactive without being withdrawn.
• Migration or rebalance: liquidity may move to a new pool, fee tier, range, or protocol under a disclosed process.
• Independent LP exit: third-party providers can remove their own capital without project control or deception.
• Indexing: dashboards can lag, misprice one reserve, or change which pool they treat as primary.

Follow the underlying position and token flows. The liquidity-migration guide provides the execution checks for a claimed replacement market.

A valid lock protects only liquidity withdrawal

Locked depth does not prevent linked holders from selling, a mint authority from creating supply, an administrator from freezing or taxing transfers, a proxy from changing code, or a team from abandoning the project. It also cannot guarantee demand or price stability.

Treat the lock as one row in the rug-mechanism review and pair it with the authority and upgrade audit. The strongest conclusion is narrow: a defined share of a defined position cannot be withdrawn under the verified current mechanism and terms.

A liquidity-control audit workflow

1. Resolve every relevant pool. Save program version, pool, assets, fee tier, positions, reserves, active range, and routing significance.
2. Identify withdrawal claims. Map LP token supply, position IDs, owners, custody programs, and control of any managing contract.
3. Verify lock mechanics. Record exact instrument, amount, denominator, beneficiary, unlock, transfer, emergency, and upgrade paths.
4. Measure executable depth. Quote intended exit sizes and distinguish total deposited value from liquidity active at the current price.
5. Trace changes. Decode withdrawals, range changes, migrations, reserve outputs, recipients, and later movement of both assets.
6. Write mechanism-first. Separate removable exposure, verified lock, ordinary LP exit, migration, inactive range, and confirmed withdrawal.

What belongs in the journal

Record every pool and quote asset, protocol and program version, LP mint or position IDs, owners and entity confidence, total and active liquidity, locked amount and denominator, locker code and authority, beneficiary, unlock and emergency terms, fee rights, intended-size quotes, withdrawal or migration signatures, reserve changes, recipients and proceeds, alternative explanations, public claims, and the narrow conclusion supported by the position state.

Primary sources