Telegram Verification Guide for TON Projects — Get the Blue Checkmark Right (Step-by-Step)

Why Telegram Verification Matters for TON Projects

A verified Telegram account protects users from impersonators, improves trust, and increases visibility inside the TON ecosystem. For projects building on TON, the blue checkmark also reduces scam friction and improves onboarding for community members, partners, and press.

Two official routes to verification

1) Standard path — via @VerifyBot

Most projects follow Telegram’s standard route. Key requirements you’ll need before submitting:

• Two verified social profiles (e.g., Twitter/X, Instagram, Facebook, or LinkedIn) that clearly reference the same project or company.

• Two independent media mentions from reputable outlets that name the project and link to the official site or team.

• A consistent public identity: matching project name, website domain, and account naming conventions.

• Clear statement of purpose for verification (why the account needs to be verified).

Tip: Provide direct URLs and screenshots; list publication dates for media mentions.

2) Accelerated path — via TON Foundation support

For high-impact projects the TON Foundation can bundle evidence and liaise with Telegram moderators. Typical eligibility signals:

• 1,000,000+ users (or comparable scale metrics showing broad adoption)

• Mini Apps SDK integration or demonstrable, functional use of TON in production

• Clear, verifiable proof that the project actively uses TON in product flows

TON Foundation support does not guarantee approval — Telegram retains final authority — but it helps present a complete, prioritized evidence package to moderators.

Step-by-step submission checklist (copy-ready)

1. Official project page URL (with SSL) and canonical contact email (domain-based).
2. Two verified social profiles (links + screenshots).
3. Two separate media articles or press mentions (links + screenshots).
4. Clear statement of intent (one short paragraph explaining the account’s role).
5. Proof of product scale (download numbers, active users, or traffic metrics) — required for accelerated review.
6. Mini Apps SDK integration proof (screenshots, repo links, or integration demo) — required for TON-assisted path.
7. Screenshots of your Telegram channel/group showing admin list and pinned governance posts.
8. Single PDF folder or ZIP with numbered files matching the checklist (helps reviewers).

Do not submit partial evidence — incomplete packages are the most common reason for delays or rejections.

Common pitfalls that block approval

• Inconsistent naming across website, socials, and Telegram handle.

• Personal accounts only — verification expects official project channels.

• Weak or irrelevant media mentions (paywalled or low-quality sites often don’t count).

• Missing proof of domain ownership or a public contact email using a free provider.

• Submitting screenshots without live links or dates.

After you submit: what happens next

Telegram makes the final decision. TON Foundation support can package and escalate a well-documented submission but cannot override Telegram’s policy. Keep your submission organized and numbered — it speeds internal review cycles and improves your odds of a positive result.

Quick template: “Why we need verification” (paste into your submission)

[ProjectName] requests verification to protect our community from impersonation and scams, improve trust for customers and partners, and enable secure distribution of official updates. We operate at [users/DAU metric] and integrate TON via [Mini Apps / smart contract link]. Attached: social proofs, media mentions, domain verification, and a product demo.

Related: Why Institutions Are Entering Web3 in 2025 — And What It Means for TON