Home › Guides
How to check a token before buying: 6 checks that matter
Most money lost on new tokens is not lost to a falling price. It is lost because the contract would not let the holder sell, or because the exit was priced into nothing. Both are visible before you buy — here is exactly what to look at.
Published:
Why the chart tells you nothing about contract risk
A price chart shows what buyers did. It says nothing about whether selling is permitted. A honeypot chart looks like the best entry you have ever seen: it only goes up, because nobody can take profit out. Volume can be manufactured by the deployer trading with themselves, and a screenshot of a locked liquidity pool proves nothing if the lock expires next week.
Everything that actually decides your downside lives in two places: the token contract and the liquidity pool. Both are public. Reading them takes two minutes with a scanner, and the six checks below are the ones that change decisions.
1. Honeypot: can the token be sold at all
This is the only binary check. A honeypot permits buys and blocks sells, using a blacklist, a whitelist of allowed sellers, a maximum sell amount set near zero, a transfer cooldown, or simply a sell tax of 99%.
Static contract analysis catches the crude versions. It misses the dynamic ones, where the block depends on state that only exists at runtime. The check that catches those is a simulated sell from wallets that actually hold the token: if 30% of real holders cannot get out, no reading of the source code matters.
2. Buy and sell tax — and the break-even it forces
Taxes are not just a fee, they are a hurdle. With a buy tax of b and a sell tax of s, the price has to rise by 1 / ((1−b)(1−s)) − 1 before you are level. A 5% buy and 5% sell tax needs +10.8% just to get your money back; 10% and 15% needs +30.7%.
Then ask the second question: can the owner change the tax? A contract with a modifiable tax has an effective sell tax of "whatever the owner sets when you try to leave". Treat a scanned 3% with a modifiable setter as far riskier than a fixed 8%.
3. Owner permissions: the switches still in someone's hand
These are the powers that turn a healthy-looking token into a loss without any market event. Each one is a yes/no flag in the contract:
- Mintable — new supply can be created, diluting holders to nothing.
- Pausable transfers — trading can be frozen at will, including yours.
- Blacklist — specific addresses can be barred from selling.
- Modifiable tax — the sell fee can be raised after you are in.
- Owner can change balances — your holdings can be rewritten directly.
- Hidden owner / reclaimable ownership — "renounced" ownership that can be taken back.
- Proxy contract — the logic itself can be swapped for different code.
4. Liquidity: how much can leave before the price collapses
Liquidity is the size of the door. A token with $3,000 in its pool cannot return $3,000 to holders — the first few hundred dollars of selling already move the price, and the rest fills far lower. Market cap is irrelevant here; a $10M "market cap" on $5,000 of liquidity is a number, not money.
A useful habit: compare your intended position to total pool liquidity. If you are more than roughly 1% of it, you are the exit liquidity.
5. Holder and LP concentration
If the owner or deployer holds 40% of supply, their decision to sell is the only chart that matters. Same for the pool: LP tokens that are neither burned nor locked mean liquidity can be withdrawn in one transaction, which is the classic rug.
Very few holders is a related signal. Ten holders means no market — it means a deployer, some bots, and you.
6. Verified source and proxy pattern
Unverified bytecode means nobody outside the team has read the rules you are agreeing to. It is not automatically malicious, but it removes every other check's foundation, and it is trivially cheap for an honest project to fix.
A verified proxy is not the same as a verified token: the proxy points at an implementation that can be replaced. Verified today does not mean unchanged tomorrow.
The two-minute routine
Run the address through a scanner and read four numbers in this order: honeypot verdict, sell tax, liquidity, owner permissions. If the honeypot verdict is bad, stop — nothing else matters. If liquidity is under a few thousand dollars, stop. If the owner can mint, pause or re-tax, size the position as if it could go to zero at any moment, because it can.
Re-check immediately before you trade, not an hour earlier. Taxes and permissions are live state — a clean scan expires.
Check a contract now
Paste a contract address into the scanner and get a honeypot verdict, live tax figures, liquidity depth and a 0-100 risk score in a few seconds.
FAQ
Is a locked liquidity pool enough to make a token safe?
No. A lock only prevents liquidity withdrawal, and only until it expires. A locked pool is fully compatible with a 99% sell tax, a blacklist or mintable supply.
Does a contract audit mean the token is safe?
An audit reviews code quality at a point in time. It does not stop the owner from using the powers the code grants them, and an upgradeable proxy can be pointed at unaudited code afterwards.
Can a token become a honeypot after I buy it?
Yes. If the contract allows pausing transfers, blacklisting or raising the tax, a token that sold fine yesterday can block sells today. That is why the permission checks matter as much as the current honeypot verdict.