Skip to content
Crypto Record

Crypto news across every chain

2026-11-20 14:38 UTC0f4952

How to check a Solana creator’s earlier launches for removals

To check whether a Solana token creator removed liquidity from earlier tokens, trace creator-linked pools and compare withdrawal instructions, amounts, times and destinations.

Crypto Record Editorial4 min read

How to check a Solana creator’s earlier launches for removals

A Solana token creator’s earlier launches can be checked by tracing creator-attributed mints to their pools, then inspecting withdrawal transactions and destinations. Transaction history supplies the evidence for a repeated pattern: each recorded incident ties a mint and pool to a time, signature, actor and liquidity reduction.

What should you have ready?

For a Solana creator-history review, have the current mint, the Token creator wallet, Solscan access and a place to record signatures ready. Start with the current mint because its creation transaction can help confirm which wallet launched it.

Use the creator wallet as a lead, then substantiate each earlier launch through its creation transaction. A wallet appearing near a token is not enough to attribute the launch; record the transaction that connects the wallet to the mint. Keep the evidence tied to each mint so similar names do not blur separate tokens.

How do you trace earlier launches and liquidity removals?

  1. Attribute launches. Starting from the current mint, inspect its creation transaction in Solscan and identify the Token creator wallet. Follow that wallet’s transaction history to candidate earlier mints, then open each mint’s creation transaction. The visible result is a list of launches with a transaction-based link to the creator wallet; leave out candidates without that link.
  2. Locate each mint’s pools. For every attributed mint, find its Raydium pools and record the pool address. Then identify the creator-linked liquidity position and the wallet or authority controlling it. Raydium CPMM positions use LP tokens; CLMM positions use position NFTs. Follow those assets and their associated transactions to connect a position to the creator wallet. The result is a pool-and-position record for each launch.
  3. Inspect withdrawal transactions. Open successful transactions associated with each position and read the instructions, token balance changes, actor and recipient. Solana transaction metadata includes instructions and token balance changes, which helps connect the operation to the assets moved. Record the signature and time alongside the liquidity reduction. A transfer after withdrawal can show where the withdrawn assets went, so follow subsequent transfers and note their destinations.
  4. Separate CLMM fee collection from liquidity removal. Raydium CLMM decrease-liquidity calls can collect fees while reducing liquidity by zero. Read the liquidity parameter in the instruction before counting a transaction as a withdrawal: a zero reduction is fee collection, while a positive reduction records liquidity taken out. The [Raydium instructions](https://github.com/raydium-io/raydium-docs-v1/blob/main/products/clmm/instructions.mdx) describe the instruction distinction. This check keeps fee collection from inflating the removal count.
  5. Compare launches and close the record. For each pool, compare successful reductions, remaining liquidity and later deposits. A withdrawal followed by a deposit into another pool may be part of a migration; trace the destination pool and record the redeposit before judging whether liquidity was removed from the project. The [Solana getTransaction documentation](https://solana.com/docs/rpc/http/gettransaction) explains the transaction evidence available for review. The task is complete when each counted incident has a mint, pool, time, signature, actor and liquidity reduction in your evidence table.

Repeated positive reductions across attributed launches, especially where the record shows no corresponding redeposit and tracks assets to a destination, make a pattern easier to document. A fuller review takes more time as the wallet’s history and pool count grow. For a skeptical buyer considering meaningful exposure, that time can buy a clearer comparison of removals, retained liquidity and redeposits; a quick scan is less work but leaves more of the history unexamined.

What if liquidity moved during a pool migration?

Trace the destination pool and redeposit. Match the outgoing assets and timing to activity in the new pool, then record both sides of the move so the history shows whether liquidity was transferred or remained withdrawn.

What if the creator has no previous launches?

Record the search coverage and the limited history: which wallet you traced, which transactions and pools you reviewed, and the earliest activity visible in that review. That gives the evidence table a clear boundary.

A rugcheck reviews a token for warning signs that could point to a scam or rug pull, while a transaction table documents a creator-linked liquidity history. The solana token safety topic connects to that review because earlier pool activity is one piece of the token’s risk context.

Keep the table focused on attributable transactions and positive liquidity reductions. That is the documented pattern a buyer can compare across launches.