01Disclose everything you can BEFORE the launch tx hits
Pre-launch disclosure is the single highest-impact thing you can do. Not because the scanner gives "credit" for a Twitter thread — it doesn't. Because traders trust what they can verify hours before the contract mints. If your tokenomics are public the day before launch, your launch-window concentration looks intentional, not predatory.
Publish 24+ hours pre-launch:
- Total supply — just the number.
- Allocation table — every wallet that will hold supply at T+0. Team, treasury, marketing, airdrop, liquidity, locked. Percentages summing to exactly 100.
- Dev wallet address — public, before the contract exists. Buyers verify the create-tx came from this wallet.
- Lock contract addresses — if marketing/team is locked, publish the lock + unlock schedule on-chain. Streamflow, Goki, Squads — pick one and link it.
- Premine percentage — if the dev wallet keeps any, label it. The scanner finds it anyway. Disclosed = "team allocation". Undisclosed = "dev sniped 8% in create tx".
- Whether you're pre-buying — if you'll snipe your own bundle in the first minute, say so and explain why. Marketing wallet pre-fund is normal. Stealth pre-fund is the #1 thing we flag.
Format: pinned X thread, GitBook, README, footer of your website. What matters: a stranger can read it and predict what they're going to see on-chain post-launch.
02Win the launch window or don't bother
The scanner walks the first 60 seconds and the first 10 minutes of trading separately. Both windows are scored. Both can kill your organic_score in a single block.
| Signal | Healthy | Caution | Manipulated |
|---|---|---|---|
| % supply bought · first 60s | < 5% | 5-15% | > 15% |
| % supply bought · first 10m | < 15% | 15-35% | > 35% |
| Largest 5-second cluster (wallets) | < 5 | 5-10 | > 10 |
| Dev create-tx snipe | 0% | < 3% | > 3% |
Hitting "Manipulated" on any single row costs 20-60 points off a 100-point organic score. Two = your token reads as Manipulated — launch was bundled and/or dumped on retail. Every aggregator flags red.
If you want to seed early liquidity from team funds, the right play: (a) disclose the pre-fund publicly the day before, (b) use a single wallet labelled in your X bio, (c) lock those tokens on-chain with a public vesting contract, and (d) link to the lock from your launch tweet.
03LP burn or LP lock — pick one and prove it
Liquidity is binary: secured or not.
- 100% burned → +20 blue-chip. LP went to a dead address. Permanent.
- 100% locked in a known vault (Streamflow, Goki, Mooncake, Team Finance, UniCrypt) → +18. Verifiable unlock date on-chain.
- Partial / mixed → scaled credit. 50%+ secured = "mostly secured" verdict.
- Unsecured → 0 on this dimension + a +10 rug-risk factor.
Pump.fun handles this automatically — the Raydium Launchpad migration contract burns the entire LP at the bond. Launching elsewhere? Lock the LP within 1 hour of LP-add. Long delay between LP-add and lock is a flag pattern.
05The post-launch dump signal
The scanner doesn't just look at launch state. It runs a hold/sold analysis on every scan: for every wallet that bought in the first 10 minutes, we walk their current on-chain balance and compare it to what they bought.
- Holding ≥ 80% of launch bag — green
- Sold partial (20-79%) — amber
- Sold all (≤20% remaining) — red
- Re-accumulated (current > launch) — violet
The aggregate becomes the "% still held" headline on the bundle card. There's no escape from a bad launch via "vesting" — if you bundled the launch and your wallets still sit on the supply 30 days later, the scanner labels you "Bundle held".
Conversely, a token that was bundled at launch but has since fully sold gets a redemption flag: "Bundle already dumped — risk materialized". A real, healing path. If you launched messy 3 months ago, the scanner gives you credit for cleanup.
07Dev wallet behaviour after launch
The scanner tracks every buy + sell + transfer + fee claim from the dev wallet, with timestamps and realized P&L.
A dev wallet that buys back into the token over time, holds the position, has zero outgoing transfers to non-DEX addresses is the strongest possible alignment signal. Scored as +5 blue-chip.
A dev wallet that flushes its holdings to a fresh address within 30 days is the strongest possible misalignment signal. Cluster analysis runs on every recipient address. Plausible deniability is impossible.
Public rule: if the dev wallet net balance changes by more than the dev's claimed allocation in any 7-day period, your token reads as "team is offloading".
08Wash trading — the scanner already knows
The trade tape walks every swap on every pool, dedupes by wallet, and computes wash ratio, bot ratio, and organic ratio.
A token with 70% wash gets labelled "Wash-traded launch detected" on the bundle card and the headline volume on the trending page is annotated "wash-flagged". The trust narrative is gone.
Paying a market maker is normal — but make them quote within reasonable bounds. A 95%-wash token gets surfaced on every scan. A 30%-wash token (typical of legitimate MM activity early in life) gets noted but doesn't trigger the verdict.
09The scoring formula
Three independent scores compose into the verdict pill:
Rug Risk (lower is better)
- +30 each: deployer rugged-before · hidden mint authority · hidden freeze authority · LP unsecured · honeypot detected · blacklist function present
- +20 each: dev-snipe ≥ 5% · top-10 holders > 50% · no socials · age < 1 hour
- +10 each: dev-snipe 2-5% · fresh deployer · single-pool-only liquidity
- Resolved factors (visible dumps, time elapsed) subtract from active risk
Blue Chip (higher is better)
- +20 each: LP locked/burned · market cap > $10M · top-10 < 30%
- +10 each: mint renounced · freeze renounced · age > 30d · listed on 4+ DEXes · strong volume
- +5 each: each verified social · verified website · established CEX listing
- +8: organic adoption (sustained volume + age + low wash)
Verdict pill — exact thresholds
- LIKELY_RUG when Rug ≥ 60 (or any confirmed honeypot / critical contract flag)
- HIGH_RISK when Rug 40–59
- SUSPICIOUS when Rug 25–39
- CAUTION when Rug 12–24
- CLEAN_ON_SURFACE when Rug < 12 + Blue < 50 (default for new tokens with no flags)
- ESTABLISHED when age > 30d AND Blue ≥ 50 (or hits the strict gate: $10M+ mcap · $500K+ liq · active vol)
- BLUE_CHIP when Blue ≥ 70 AND blue-chip qualified ($50M+ mcap · $2M+ liq · 90d+ · active vol)
Hard rule: Blue is forced to 0 when Rug ≥ 40 — a rug cannot be rewarded for being "old" or "renounced". Canonical tokens (USDC, WBTC, PEPE, etc.) override to VERIFIED_* regardless of launch-window heuristics.
10The shortest possible launch checklist
Tap each item as you complete it. Progress saves to your browser — close the tab and come back later, your state persists.
- Allocation table published 24h pre-launch
- Dev wallet address published 24h pre-launch
- Pre-buy disclosure (yes/no, which wallets, why) published 24h pre-launch
- First-60s buys: < 5% of supply
- First-10m buys: < 15% of supply
- No 5-second cluster > 5 wallets
- Dev create-tx snipe: 0%
- LP fully burned OR locked in a known vault, within 1 hour of LP-add
- Mint authority renounced
- Freeze authority renounced
- X handle contains the token symbol
- Website registered with the same socials as DexScreener + CoinGecko
- Socials updated on DexScreener + CoinGecko + on-chain metadata URI
- Dev wallet plan documented (will hold X% for Y months)
- First scan run on analyzer69000.com/check within 10 minutes of bond
- Verdict: PROCEED / ESTABLISHED / BLUE_CHIP within 24 hours
Book a 1:1 with cryptoflan
If you're shipping in the next 30 days and want a forensic pre-check of your launch params before the contract mints, book a slot. I'll review your tokenomics, dev-wallet plan, LP setup, and likely launch-window data. Mon–Fri 9am–4pm CST. First-come, first-served.
EXWhat a good scan looks like
Paste any of these into analyzer69000.com/check for the live scan:
- $JUP — verdict BLUE_CHIP, organic 90+, LP secured, every social cross-verified
- $PYTH — verdict ESTABLISHED, mint + freeze renounced, distributed top holders
- $BONK — verdict BLUE_CHIP, age 2y+, organic adoption signal active
Common ground: none of them tried to fake the early data. Each had a clean launch window, public allocation, and the patience to let price find itself. The only path to a verdict that doesn't get flipped to "Likely rug" by the next scanner.
→Once you've passed the scan
If your scan reads PROCEED+ with organic ≥ 50, your token qualifies for a Verified Boost. The scanner runs as the gate — if your organic score drops below 30 mid-window, 50% of the slot fee refunds automatically on-chain.
The point isn't the boost. The point: if you've launched right, the scanner will tell people. We built the gate so paid trending placement only flows to tokens that earned the verdict.
Build the token. Pass the scan. Then talk about it.
06Socials — verified, cross-linked, matching the token
A social is "verified" only if it appears in at least one curated public registry (the same registries every aggregator + scanner cross-references). The scanner also crawls your project website and runs a relevance filter — if a linked twitter handle has zero textual relation to your token name/symbol, it gets rejected (had to ship that after a $MAGA scan was surfacing an unrelated tiktok as "verified" because the project's site linked to a merch shop).
Do this: