How a find works.
First who launched it. Then what else that wallet launched, where the supply went, and a score from fixed rules. This page is built from the same config that scores your token.
Who
launched it.
A find starts at the wallet that created the token and walks back through what it launched before.
Statuses
- DEAD
- Older than 24 hours, market cap under $10k. An unknown market cap counts as $0.
- DOWN 90%+
- Peak of $30k or more, now under 10% of that peak. Counted as dead in every total.
- ALIVE
- Younger than 24 hours, or market cap of $10k or more.
- SUCCESS
- Market cap of $250k or more, or a peak of $1M or more and still at 25% of it.
Limits
- Only pump.fun launches are counted. Coins from other launchpads do not show.
- The walk can stop early on pages or time. Then every count is a minimum, and the report says so.
- Big launchers get a sample: the newest coins plus an even spread of older ones. Statuses cover that sample only.
- A coin counts only when the wallet signed its creation, or its bonding curve names the wallet as creator. When in doubt it is left out.
- Statuses are from the moment of the find.
The formula.
Every token starts at 10. Red flags add, green flags subtract, and the score stays between 0 and 100. Tick the flags and watch it move. These are real rules with real points. The start is only an example. Tiered rules show their maximum.
- Start
- 10
- Red
- +40
- Green
- −10
Kept between 0 and 100.
- Any critical flag: at least 50.
- A copy of a verified token, or live mint or freeze authority: at least 75.
- Under 60% of sources: partial data, no level.
Four levels.
We never call a token safe. The best result is no major red flags found.
- LOW0 to 24No major red flags found. It can still go to zero.
- WARNING25 to 49Flags worth reading before you decide.
- DANGER50 to 74Serious flags, or at least one critical flag.
- SEVERE75 to 100Many flags, a copy of a verified token, or live mint or freeze authority.
Five steps.
AI only words the reply. It never sees bios or websites, and code fills in every number.
- 1Find the token: from an address, a link, a post or a ticker.
- 2Read: every source at once, each with its own timeout.
- 3Freeze: one snapshot with a SHA-256 hash.
- 4Score: fixed rules. Same input, same score.
- 5Reply: card, bot reply and report, all from that snapshot.
Which token.
Tag the bot under any post. It works out the token in this order and stops at the first exact hit.
- 1An address in the post. A token address or a token link, in the post that tagged us.
- 2The parent or quoted post. Same search in the post you replied to or quoted.
- 3The author's token. A saved verified link, then bio, website, pinned post, our index of token socials, DexScreener search and latest posts.
- 4$TICKER. Solana only, with real liquidity. One clear match is used. If not, the bot asks which one.
- 5Nothing found. We say so and ask for the address. We never guess a token.
Then we check the link both ways
- Verified
- Two sources agree. For example, metadata links the X account and the website shows the same address.
- Unverified
- Only the account claims the address. The token does not point back.
- Conflict
- The website or bio lists a different address than the token.
15 sources.
A source that fails lowers completeness. Rules that need it are skipped, never guessed.
| Source | What it reads | From |
|---|---|---|
| Who launched it | Dev wallet balance, sells, moves to other wallets | |
| Earlier coins | Coins this wallet launched on pump.fun, with status | |
| pump.fun | Creator, create transaction, bonding curve, graduation | |
| Launch | Buys in the creation slot and the first slots after it | |
| Clusters | Who funded the top holders. A shared funder links wallets | |
| Holders | Largest owners and top 10 share | |
| Labels | Pools, burn, locks and exchange wallets, left out of concentration | |
| Mint | Authorities, supply, Token-2022 extensions | |
| Metadata | Name, image, socials, update authority | |
| Market | Price, market cap, liquidity, volume, main pool | |
| DEX paid | Paid profile, ads, community takeover | |
| Locks | Streamflow locks and the unlock schedule | |
| X account | Account age, handle changes | |
| Website | Domain age, status, address on the site | |
| Copies | Name, ticker and logo against verified tokens |
36 rules.
Built from the scoring config. Change a rule and the version changes with it.
Red: adds points
| Rule | Severity | Points |
|---|---|---|
| Name, symbol or logo copies an older verified token with a different mint. | +45 | |
| Mint authority is not revoked, so more supply can be printed. | +30 | |
| Freeze authority is not revoked, so holders' tokens can be frozen. | +30 | |
| The project's website or X bio lists a different contract address than this token. | +30 | |
| Dev created at least 3 earlier tokens old enough to judge (over 24 hours or already resolved) and at least 70% of those are dead. | +30 | |
| Token-2022 with a permanent delegate, a transfer hook or a non-zero transfer fee. | +25 | |
| Dev sent at least 3% of supply to other wallets. | +20 | |
| Wallets buying in the creation slot (bundle) took more than 30% (at least DANGER), 10% or 3% of supply. | +20 (> 30%)+12 (> 10%)+5 (> 3%) | |
| Main pool is a classic AMM with LP tokens and the LP is neither burned nor locked. | +20 | |
| Dev created at least 10 tokens in the last 30 days. | +18 | |
| Dev wallet holds an unlocked share of supply above 10% (or above 5%). | +18 (> 10%)+10 (> 5%) | |
| Holder groups funded by the same wallet (at least 2 wallets each) together own more than 15% (or 8%). | +12 (> 15%)+6 (> 8%) | |
| We have seen this X account under a different username before. | +12 | |
| Top 10 holders (excluding pools, burn, locks, CEX) own more than 40% (or 25%). | +10 (> 40%)+5 (> 25%) | |
| Early buyers (first launch slots, bundle included) still hold more than 10%. | +10 | |
| Graduated to a DEX but liquidity is below $5,000. | +10 | |
| The project's X account is younger than 7 days. | +8 | |
| More than 5% of supply unlocks within 72 hours. | +8 | |
| Website domain was registered less than 7 days ago. | +5 | |
| The project website does not respond. | +5 | |
| No X, website or Telegram anywhere in metadata or DexScreener. | +5 | |
| An X account claims this CA but the token does not link back to it. | +5 |
Green: subtracts points
| Rule | Severity | Points |
|---|---|---|
| Dev has at least 2 earlier tokens old enough to judge, none down 90%+, at least one success, and under 30% dead. | −15 | |
| At least 80% of the dev allocation is locked on Streamflow. | −10 | |
| Top 10 hold less than 15% and there are more than 500 holders. | −8 | |
| Both mint and freeze authority are revoked. | −5 | |
| X account to token link verified by at least 2 sources and the website is live. | −5 | |
| Liquidity above $50,000. | −5 | |
| Dev has not sold anything, has not moved tokens to other wallets, and holds less than 5%. | −3 | |
| Approved DexScreener token profile (paid). | −2 |
Notes: no points
| Rule | Severity | Points |
|---|---|---|
| DexScreener paid orders (profile, ads, trending), shown for context. | 0 | |
| Community takeover registered on DexScreener. | 0 | |
| Token is less than 1 hour old, so everything can change fast. | 0 | |
| Still on the pump.fun bonding curve. | 0 | |
| Graduated from the pump.fun bonding curve to a DEX pool. | 0 | |
| Launched on a known launchpad (PUBLIC_LAUNCHPADS). | 0 |
FAQ.
What is a find?
One check of one token. It reads who launched it, their earlier coins and the supply, then scores it.
What does dead mean?
Dead means older than 24 hours with a market cap under $10k, or a peak of $30k or more and now under 10% of that peak. An unknown market cap counts as $0.
Why does a count say minimum?
The history walk stops when it runs out of pages or time, and big launchers get a sample of their coins. When that happens the count is a minimum and the report says so.
Are all launches counted?
No. Only pump.fun launches. A wallet can have coins from other launchpads that do not show. None found does not mean none launched.
Does LOW mean it is fine?
No. LOW means no major red flags found in the data read at that moment. A token at LOW can still go to zero.
Does a report say who the person is?
No. It shows wallets and coins. It does not say who holds a wallet, or why anything happened.
What if a report is wrong?
It is automated, so it can be. A project can reply from its report page, and a deployer record can be disputed. A person reviews both. A reply never changes the score. Only data does.
Not advice.
Truvo is an automated research tool. Wallet and deployer data can be late, incomplete or wrong.