Social Check
/social <contract> answers one question: what are this token’s real
socials? It pulls links from many public sources, dedupes them, and
shows you what’s verified, what’s a candidate, and where it came from —
in one Telegram message you can scan in under five seconds.
What it returns
Section titled “What it returns”The reply is grouped into clear sections. You’ll see only the sections that actually have results for the token you queried — empty sections are hidden.
| Section | What’s in it |
|---|---|
| 🚀 Launched by … | Detected launchpad attribution. Lines up the original launch tweet/page when the token came out of a known platform (Bankr or Clanker on Base today). |
| ✓ Verified | Links pulled from curated primary sources — these are the project’s actual website, Twitter, Telegram, etc. as recorded by the major data providers. |
| ⚠ Potential (unverified) | X handles and websites the bot discovered by searching, ranked by signals like “contract address in bio,” profile-URL match, and follower count. |
| 🌐 Potential Domains (unverified) | Live domains found by probing common TLD variants of the project’s name (<name>.com, <name>.io, <name>.ai, <name>.xyz, etc.), sorted by registration date — newer-registered domains rank ahead of long-held squatter holdings. |
| 💬 Potential Telegrams (unverified) | Live Telegram channels and groups found by probing common handle variants (<name>, <name>official, <name>portal, <name>community, etc.), sorted by subscriber count. |
| 🗨 Mentions | Recent tweets that referenced the contract address — callers, scanners, and traders. Each row links to the actual tweet, not the profile. |
The token name and chain emoji always appear at the top; the contract address always at the bottom for easy copy.
How to call it
Section titled “How to call it”/social <contract> — auto-detect chain/social <chain> <contract> — when auto-detect can't disambiguate/social — as a reply to a message with a CAThe third form is a shortcut: if someone pastes a contract address in
chat, reply /social to their message and the bot extracts the address
from the parent. No copy-paste needed.
/socials is an alias — both names work identically.
Example
Section titled “Example”A token with strong socials looks like this:
🔹 Refix 🚀 Launched by Clanker https://www.clanker.world/clanker/0x31db…1bba3 ✓ Verified 🌐 https://refix.ai 🐦 @refix_AI (12.5K followers) 💬 @refixcommunity (3.2K subs) ⚠ Potential (unverified) 🐦 @regalstreak (CA in bio · 10K followers) 🌐 Potential Domains (unverified) 🌐 https://refix.io (registered 2024-08-12) 🌐 https://refix.xyz (registered 2023-06-21) 💬 Potential Telegrams (unverified) 💬 t.me/refixportal (1,247 subscribers) 🗨 Mentions 🐦 @qkl2058 — 67.6K followers 🐦 @meliboi_sama — 6.7K followers 0x31db36c125212b862aafd3d0c8b2785548b1bba3
A token with nothing curated yet might only show Mentions plus brute-force probes:
🔹 NewMeme No verified socials found across primary sources. 🌐 Potential Domains (unverified) 🌐 https://newmeme.fun (registered 2026-05-19) 🗨 Mentions 🐦 @kolscanner — 4.1K followers 0xabc…def
That’s still useful — the new newmeme.fun domain registered the day
of launch is a strong candidate for the project’s real site.
How the signal ranks
Section titled “How the signal ranks”Within each section, the bot ranks by quality:
- Verified rows order by source-agreement — links confirmed by more independent providers float first.
- Potential X handles rank by a score combining “CA in bio,” “name in handle,” “URL matches project name,” follower count, and account age. Squatter handles with single-digit followers naturally sink to the bottom.
- Potential Domains sort by registration date, newest first — a domain registered around the token’s launch is far more likely to be the project’s real site than a 10-year-old domain that happens to share the name.
- Potential Telegrams sort by subscriber count.
- Mentions sort by follower count.
Launchpad detection
Section titled “Launchpad detection”When a token was deployed via a recognised launchpad, the 🚀 Launched by … header surfaces at the top with a direct link to the original launch:
- Bankr (Base) — detected from the
@bankrbot (deploy|launch) $<TICKER>request pattern. The link points at the launcher’s original tweet that triggered the deploy. - Clanker (Base) — detected via Clanker’s public token registry. The link points at the canonical Clanker page for that contract.
If both signals fire for the same token, Bankr takes priority.
Filtering out noise
Section titled “Filtering out noise”A few quality filters run automatically so the output stays useful:
- Name-match required for Potential URLs — candidate links whose host doesn’t contain a distinctive token from the project’s name or symbol get dropped. Stops random analytics dashboards and KOL signal sites from leaking into the Potential section.
- Permalink filter — when a curated source mistakenly stores a
tweet URL (
x.com/<handle>/status/<id>) as the project’s Twitter, the bot drops it rather than surfacing the random tweeter as if they were the project’s official account. - Squatter detection — domains that redirect to known parking pages (dan.com, sedo, godaddy parking, etc.) are excluded. Telegram bot handles are de-prioritised behind real channels.
Caveats
Section titled “Caveats”- Cached for six hours. Re-running
/socialon the same contract returns cached data within the window. Brand-new tokens may take a few minutes after launch before the primary data sources index them. - “Verified” is not a security guarantee. It means a curated data provider has the link on record, not that the link is safe to click or trade against.
- “Potential” sections are best-effort. They surface candidates, not confirmed accounts. Always verify by clicking through and cross-checking the contract address yourself.