Skip to content

Social Verification

Verify ownership of your social accounts and website domain, and display verified badges on your token page. Verified social channels also contribute to your health score.

How verification works

1. Add a link. Add a social or website link on your token page — Chain Daddy auto-detects the platform.

Adding a social link — paste your X profile URL; it's detected as X (Twitter)

2. It starts unverified. New links carry a shield-question badge, and a shield in the top bar flags how many are waiting.

An unverified X link — a shield-question badge until you verify itThe verification shield in the top nav, badged with the unverified count

3. Open the Verify panel. The Verify External Links panel lists every link with a Verify button (or Verify All).

The Verify External Links panel — one row per link with a Verify button and a "Verify All" action

4. Prove ownership. OAuth platforms (X, Discord, …) send you to authorize read-only access; bio-code and website methods use a code (both covered below).

Authorizing on X — "Chain Daddy wants to access your X account"

5. Verified. The account is now linked to your token, and it shows a check badge on your page.

X verified — the account is now linked to your tokenThe verified X handle with a check badge on the token page

The rest of this page covers the specifics for each verification method.

Supported Platforms

PlatformMethodBadge Display
X (Twitter)OAuthVerified handle with link
DiscordOAuthVerified username with link
TwitchOAuthVerified channel with link
YouTubeOAuthVerified channel with link
GitHubOAuthVerified username with link
TikTokBio codeVerified handle with link
TelegramBio codeVerified channel with link
InstagramBio codeVerified handle with link
RedditBio codeVerified username with link
PumpFunWallet matchVerified creator badge
WebsiteDNS TXT / HTML metaVerified domain with link

OAuth Verification (X, Discord, Twitch, YouTube, GitHub)

Prove you control an account by authenticating via OAuth.

Flow

  1. Click Verify [Platform] on your token manager dashboard
  2. You'll be redirected to the social platform for authorization
  3. Grant read-only access to your account
  4. Sign the verification attestation with your wallet (EVM or Solana)
  5. Badge appears on your token page immediately

What Gets Verified

  • Your platform username or channel name
  • The connection between your wallet address and platform identity
  • Timestamp of verification

Platform-Specific Scopes

PlatformAccess Granted
XRead profile info
DiscordIdentify (username, avatar)
TwitchRead user info
YouTubeRead channel info
GitHubRead user profile

Bio Code Verification (TikTok, Telegram, Instagram, Reddit)

Prove you control an account by placing a unique verification code in your profile bio or channel description.

Flow

  1. Click Verify [Platform] on your token manager dashboard
  2. You'll receive a unique verification code (valid for 10 minutes)
  3. Add the code to your profile bio or channel description
  4. Enter your handle/username and click Check
  5. The system fetches your public profile and confirms the code
  6. Sign the verification attestation with your wallet
  7. Badge appears on your token page. You can remove the code from your bio

The bio-code verification step for Telegram — a one-time verification code to place in your channel description, plus a handle input

Platform-Specific Details

PlatformWhere to Place Code
TikTokProfile bio
TelegramChannel description (public channels or groups only)
InstagramProfile bio
RedditUser bio/about

TIP

The verification code only needs to be in your bio at the moment of checking. You can remove it immediately after verification.

Telegram: public channel (bio code): one option

The bio-code path reads the description field of a public Telegram channel or group via the Bot API.

Requirements:

  1. A public Telegram channel or group with a @username. Private channels (t.me/+invite-link) cannot be verified via this path. If you only have a private group, switch it to public, or create a dedicated channel. Telegram's official guide: How to create a channel and How to make a public channel/group.
  2. You must be an admin on the channel/group so you can edit the description.
  3. Set the verification code in the Description field of the channel (not a posted message). Open channel info → Edit (pencil icon) → Description → paste the code → save.

Description propagation lag

Telegram caches channel descriptions for the Bot API. When you save a fresh description edit, it can take up to ~30 seconds before our verifier sees the new content. If verification fails immediately after saving, wait 30 seconds and try Check again.

Telegram: personal account (Login Widget): the other option

If you don't have or want a public channel, the Telegram Login Widget path lets you verify your personal Telegram account directly. The widget asks you to authorize Chain Daddy's verification bot (read-only: your Telegram ID + username); on confirmation the widget returns a signed payload to the page, which the backend HMAC-verifies against the bot's secret key. The signed attestation is stored under the same telegram platform key as the channel path, verified handles render identically regardless of which path produced them.

API endpoint: POST /api/v2/verify/social/telegram-personal/check (no /init step, the widget is purely client-side).

PumpFun Verification

Prove you created a token on PumpFun by matching your connected wallet to the token's deployer address on Solana.

Flow

  1. Click Verify PumpFun on your listing manager dashboard
  2. Enter your PumpFun token's mint address
  3. The system checks on-chain that your connected wallet deployed the token
  4. Optionally, if deployer doesn't match, you can use the bio-code method on PumpFun's profile page
  5. Sign the verification attestation
  6. Badge appears on your token page

Website Verification

Prove you control a domain by adding a verification record.

Method 1: DNS TXT Record

Add a TXT record to your domain's DNS:

_chaindaddy-verify.yourdomain.com  TXT  "chaindaddy-verify=YOUR_VERIFICATION_CODE"

Method 2: HTML Meta Tag

Add a meta tag to your website's <head>:

html
<meta name="chaindaddy-verify" content="YOUR_VERIFICATION_CODE" />

Flow

  1. Click Verify Website on your listing manager dashboard
  2. Enter your domain name
  3. Copy the verification code provided
  4. Add the DNS TXT record or HTML meta tag
  5. Click Check Verification: the system checks for the record
  6. Sign the attestation with your wallet
  7. Badge appears on your token page

DNS Propagation

DNS TXT records can take up to 48 hours to propagate. The HTML meta tag method is instant.

Verification Badges

Verified accounts display checkmark badges on your public token page. Each badge shows:

  • Platform icon and verified handle/channel
  • Link to your profile on that platform
  • Verification date

Badges appear in your token page header and are visible to all visitors. Verified links show a check badge; links you've added but not yet verified show a shield-question badge until you complete the flow.

Links in the token page header — a verified X handle with a check badge, alongside website, Telegram, and GitHub links with unverified shield-question badges and an "Add link" affordance

Multi-Chain Support

Works with both EVM and Solana wallets. Your verification is tied to the specific wallet you sign with.

In addition to verified accounts. You can add unverified social links to your token page:

Link TypeFormat
X (Twitter)Handle or profile URL
DiscordInvite link
TelegramChannel or username
GitHubRepository or org URL
WebsiteAny HTTPS URL
WhitepaperDocumentation URL
EmailContact address
CustomAny URL

Unverified links display without the verification badge but still link to your social presence.

Managing Verifications

  • View all verifications from your token manager dashboard
  • Each registration can have independent verifications
  • Verifications persist unless explicitly removed
  • Re-verification is available if you change your handle or domain
  • You can verify up to 11 platforms per registration (all supported platforms)