1msc.xyz

Why a Token Fails a Rug Pull Check Despite Locked Liquidity

Liquidity being locked is one checkbox, not the whole checklist. A token can pass that single test and still be a rug pull in every practical sense. Locked liquidity means the tokens in a pool cannot be pulled out by the deployer, but it says nothing about how the token itself behaves, who holds the supply, or whether the contract can be changed to make those locked tokens worthless.

Here is the plain mechanics of why a locked-liquidity token still fails a rug pull check, and what to look at instead.

Locked liquidity only locks the pool

When someone "locks" liquidity, they send the paired tokens (say, BNB and the token) to a smart contract that prevents the deployer from withdrawing them for a set period. That is the entire function. It stops a specific, crude attack: pulling the pair’s tokens out and dumping them, leaving buyers with nothing.

What it does not stop:

A rug pull check that stops at "is liquidity locked?" is not a rug pull check. It is a check of one specific vulnerability.

Why the Check Fails Even With a Clean Contract

Sometimes the contract is not malicious at all. It has no mint, no blacklist, no pause, and the liquidity is locked. It can still be a bad deal that fails a broader safety check.

Consider the holder distribution. If one wallet holds 80% of the supply and the rest is in the locked pool, that wallet is the market. When the deployer sells, the price falls. When they sell a lot, the price falls a lot. Locked liquidity does not prevent this; it only prevents the deployer from pulling the pool's tokens directly.

Consider the lock itself. Not all locks are equal. A "lock" that is actually a time-locked owner change, or a lock with a withdrawal function that the deployer can call early, is not a true lock. There are tools that will show you a lock, but you need to read the lock's contract to see who can call what and when. A lock that can be bypassed by the deployer is just a label.

Consider the liquidity pool itself. Some tokens have the liquidity locked, but the pool is not the main trading venue. There may be a second, unlocked pool on another exchange where the deployer holds the tokens. You checked the wrong pool.

What a proper rug pull check looks like

If you are verifying a token, do not stop at the lock. Work through these in order.

  1. Check the token contract for mint, pause, blacklist, and transfer-fee modification functions. Use a scanner that flags these. A mint function is an automatic fail for most checks. A pause or blacklist is a fail unless you have a specific, verifiable reason to trust the project.

  2. Check the owner and admin keys. Who can call the functions you just found? If the owner is a multi-signature wallet or a timelock contract, that is better than a single deployer wallet. But a timelock is only useful if the timelock itself is not owned by the deployer. An owner can renounce ownership, which removes the ability to change the contract. That is the cleanest result.

  3. Check the holder distribution. Look for the top 10 wallets. If any non-locked wallet holds more than 5-10% of the supply, factor that in. A large holder is a risk, even if they are not the deployer. Use a holder-analysis tool, but remember these tools have their own blind spots.

  4. Look at the liquidity pool's composition. The lock is only part of the picture. Check if the pool token is paired with a stablecoin or a major asset. Check if the pool is the only one. If the largest pool is on an obscure exchange and a smaller one is on a major exchange, the smaller one might be the one that matters.

  5. Test a sell in a simulation. Use a tool that simulates a buy and a sell in the same block. If the sell fails, the token has a transfer restriction that the tools may not have flagged. This is the single most reliable check because it tests the actual transaction path.

  6. Check the lock's specifics, not just the fact of the lock. Look at the lock contract's address. If it is a known locker (like Team Finance, Unicrypt, or a similar service), verify the lock's parameters. How long is it locked for? Can the deployer end the lock early? Is the lock's owner the deployer or a separate contract?

A token that has a mint function, a blacklist, a pause, and a deployer holding 70% of supply will fail the check even with a four-year lock. A token with none of those and a 90-day lock on a single, large pool is a different risk profile entirely.

The Real Meaning of a Failed Check

A failed rug pull check does not mean the token is a scam. It means the token does not meet the minimum safety criteria for a rational trader. It is a signal to walk away, not to investigate further. There are thousands of tokens; you do not need to find the one that is only 80% safe.

The reason a token fails a rug pull check despite locked liquidity is that locked liquidity is the easiest thing to fake or to present misleadingly. It is a necessary condition for many serious tokens, but it is nowhere near a sufficient one. The check fails because you asked a single question and the token gave a single answer. The real check demands you ask what else the contract can do, who controls it, and where the supply sits. Locked liquidity answers none of those.

Not financial advice. 1msc.xyz publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.

Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.

Back to token safety