Scankr monitors token launches from Bankr and Clanker, scrapes X/Twitter profiles, and computes an automatic trust score for every launch. This page explains how it all works.
Every row in the table is one token launch, split into four columns:
đŚ125 đ124 â1). đŚN = total tokens, đM = self-deployed (same deployer wallet), âK = external (different deployers). Color-coded: green â¤5, yellow 5-20, orange 20-50, red >50.now, 5m, 2h)All filters update the table instantly. Combine them to narrow down what matters.
The filter bar has two rows â the DEPLOYER row (purple label) and the FEE TO row (yellow label). Most filters exist for both, allowing you to evaluate each side independently.
| Filter | Target | How it works | Example |
|---|---|---|---|
| Search | All | Searches token name, symbol, contract address, and X handles | pepe â all tokens with "pepe" in name |
| Source | All | all / Bankr / Clanker â refetches data from the server | Clanker â only Clanker tokens |
| đŁ Deployer Socials | Dep | all / has X (only deployers with X linked) / no X (only without X) | has X â only deployers with scraped profiles |
| đŁ Deployer Followers | Dep | Single number = min. -number = max. X-Y = range. Use K for thousands. |
100-5K â deployer has 100 to 5000 followers |
| đŁ Deployer Key Fol | Dep | Alphagate key followers count for the deployer. Single number = min. -number = max. X-Y = range. Use K. |
5-200 â deployer has 5 to 200 key followers |
| đŁ Max Dep | Dep | Maximum number of tokens this wallet has deployed. Set to 1 for first-time deployers. | 5 â wallets with â¤5 deploys |
| đĄ Fee Socials | Fee | all / has X / no X â filters by whether the fee recipient has an X profile | no X â fee recipients with no X account |
| đĄ Fee Fol | Fee | Fee recipient follower count. Single number = min. -number = max. X-Y = range. Use K for thousands. |
-1K â fee recipient has â¤1000 followers |
| đĄ Fee Key Fol | Fee | Alphagate key followers count for the fee recipient. Single number = min. -number = max. X-Y = range. |
10 â fee recipient has âĽ10 key followers |
| đĄ Min Tw | Fee | Minimum tweet count for the fee recipient's X account | 50 â fee recipient has 50+ tweets |
| đĄ Verified | Fee | all / yes (verified/blue) / no (unverified) â for the fee recipient | yes â fee recipient is verified/blue |
| đĄ Max đŚ | Fee | Maximum total tokens assigned to this fee recipient wallet. Color-coded in the table: green â¤5, yellow 5-20, orange 20-50, red >50. | 20 â fee recipient has â¤20 assigned tokens |
| đĄ Min â | Fee | Minimum external token count (tokens where fee recipient is NOT the deployer). Higher = fee recipient collects from many different projects. | 5 â fee recipient has 5+ external tokens |
| đĄ Ratio | Fee | Ratio of external vs self-deployed tokens: Any / ext (more external) / self (more self-deployed) / s-only (self-deployed only, no external) | ext â fee recipient collects from others, not just their own tokens |
| đĄ Listed ⼠| Fee | Minimum X listed count for the fee recipient. Higher = appears in more X lists, a quality signal. | 5 â fee recipient is in 5+ X lists |
These filters control what appears in the Fee Claims sidebar on the right side of the dashboard. They do not affect the main launch table.
| Filter | How it works | Example |
|---|---|---|
| 1st Only | Toggle checkbox â when enabled, shows only first claim events per token (the inaugural fee claim). Subsequent repeat claims are hidden. | â â only first-ever claims displayed |
| Key Followers | Range input for minimum Alphagate key followers. Single number = min. -number = max. X-Y = range. |
5-50 â claimers with 5 to 50 key followers |
| Min MC | Minimum market cap threshold for fee claims. Supports: raw numbers, K, M suffixes. Tokens below this MC are hidden from the sidebar. |
100k â only tokens with $100K+ MC1M â only $1M+ MC |
Orange warning badges that appear in the deployer and fee recipient columns.
| Flag | Source | Trigger | Severity |
|---|---|---|---|
| â ď¸ Serial (X) | Wallet | Wallet deployed >10 tokens | High |
| â ď¸ New account (< 7d) | X Profile | X account is less than 7 days old | High |
| â ď¸ No followers | X Profile | X account has fewer than 10 followers | Medium |
| â ď¸ Private account | X Profile | X account is protected (private) | High |
| â ď¸ Inactive (< 5 tweets) | X Profile | X account has fewer than 5 tweets | Low |
| â ď¸ Fee: New account (< 7d) | Fee X Profile | Fee recipient's X account is <7 days old | Medium |
| â ď¸ Fee: No followers | Fee X Profile | Fee recipient has <10 followers | Medium |
| â ď¸ Fee: Private account | Fee X Profile | Fee recipient account is private | High |
| â ď¸ Fee: Inactive (< 5 tweets) | Fee X Profile | Fee recipient has <5 tweets | Low |
The right-side column displays the latest fee claim events detected from on-chain events. When someone claims fees from a token launch, it appears here in real-time. (Only Bankr)
2m, 1h)Detection latency is ~2-4 seconds from on-chain confirmation
Scankr is actively evolving. New features and documentation pages will be added regularly. Check back often or follow development updates for what's next.