GGlossary · 2 min read

What is a rug pull?

A rug pull is when a token's insiders take the value out and leave holders unable to exit. The three common mechanisms, and what you can check first.

299 words · about 2 minutes·Article updated 20 August 2026
Definition

A rug pull is when the people behind a token take the value out and leave holders unable to exit at any meaningful price — usually by withdrawing the liquidity pool, minting fresh supply into it, or selling a large insider allocation into thin liquidity.

The liquidity pull is the plainest version. The deployer wallet still owns the pool position, sends one withdraw transaction, and the liquidity every quote was priced against is gone in a single block. Balances still show in wallets; there is nothing left to sell into.

Three things are readable before you buy: whether the pool position is locked or burned, whether the mint function can still create supply, and how concentrated holdings are across wallets. None is a verdict. They are the mechanisms that make each version possible or impossible.

A lock guarantees exactly one thing: the pool cannot be withdrawn before the release date. Not the price, not the team, not the token. A locked pool can still fall.

"No lock found" means we found none — not that none exists. Locksley does not yet index every locker.

Where you'll see it on Locksley

Every token page renders lock state, supply and holder distribution as mechanisms rather than a rating, and locked at birth lists tokens whose liquidity lock was set at pool creation.

Rug pulls, explained honestly walks through each pattern and what it looks like on-chain.

Frequently asked questions

Is a rug pull the same as a honeypot?

No. A rug pull removes the value after people have bought, most often by draining the pool. A honeypot blocks the exit from the start: buys go through, sells revert because the contract refuses them. One is a withdrawal you can watch on-chain, the other is contract logic you can test before buying.

“No lock found” means we found none, not that none exists: we do not index other lockers yet, and it is never a claim about the project.

FiguresEvery number on this page is frozen at the date printed beside it and refreshed when the page is rebuilt — not live. The sentences reason about the figures, so a value that changed underneath them would make the prose wrong. Live values live on Explore and the pages it links out to. Methodology →
CorrectionsFound something wrong? Send the page and what you computed instead through the contact page. Every correction is logged publicly.
ReusePublished under CC BY 4.0. Quote it, translate it, fork it — cite the page and the date.
Who wrote thisWritten and maintained by the Locksley editorial team. Locksley is built by TrustSwap, which also owns Team Finance — the tool linked above.