Scan a token
Reads only public chain data: the launch's snipe-tax exemption list, who bought in the launch block, what the exempt wallets hold now and whether they've started selling. Try the audit's example:
Live launches scanning each launch ~3 s after it appears, then re-checking while it trades
Waiting for the next launch… (about one per second on this chain)
How the verdict works
Every Pons V2 curve taxes early buyers 99 % → 0 % over 3 seconds — except wallets on the creator's exemption list, which pay 0 % from block one. The list is emitted on-chain (SnipeTaxExempted) but never shown to buyers. We read it.
We rebuild every trade on the curve from CurveBuy/CurveSell events. Exempt wallets buying inside the 3-second snipe-tax window (blocks +0…+30) paid 0 % while you'd have paid up to 99 % — including batched buys by a dozen wallets in one transaction two blocks after launch.
What the exempt wallets hold right now, as a share of total supply (the number a tiny float can't inflate) and of everything outside the curve. SNIPED = launch-block insider buy ≥ 10 % of supply, insiders holding ≥ 15 %, or 3+ extra exempt wallets buying at block one. DEV BUY ONLY = just the deployer's small initial buy. We also flag insider sells on the curve and tokens insiders move to other wallets — the usual way to dump without it showing as an insider sell.
Creator tax (up to 10 %) is charged on every buy and sell on top of the 1 % curve fee — the round trip can cost 22 % before price moves.