← Back to blog
Checklist

Aug 25, 2026 · 13 min read

The Solana Holder Verification Checklist for Community Launches

Discord

Telegram

Key takeaways

  • Test before traffic: do not publish your holder verification link until a pass wallet, fail wallet, wrong wallet, Discord role, Telegram access, and removal path have all been checked.
  • Verify holdings, not identity: Solana holder verification proves wallet control and checks SPL token or Metaplex NFT holdings. It is not KYC, liveness, AML, age verification, or identity compliance.
  • Role setup causes most launch pain: Discord roles, bot position, and channel overwrites must be clean before members start signing. Discord bots can only grant roles below their own highest role. (docs.discord.com)
  • Telegram needs invite discipline: bot admin rights, invite link controls, and leaked link cleanup matter as much as the onchain rule. Telegram bot invite workflows depend on administrator rights and can use expiring, limited, join request, and revoked invite links. (core.telegram.org)
  • Recurring checks protect the room after launch: a holder room should not become a one-time snapshot. Sellers and wallets below the rule need a resync or removal path.

Solana holder verification checks whether a member controls a wallet that holds the required SPL token or Metaplex NFT, then maps access into Discord roles or Telegram entry after a gasless wallet signature. The point is simple: real holders get the room, non-holders do not.

Holder verification checks holdings, not identity. It does not prove someone is a safe person, stop every scammer, replace moderation, or turn your Discord into a compliance system. It gives your launch team a live access rule instead of screenshot checking, manual role assignment, and support chaos.

A launch gate is part product setup, part community ops, and part trust signal. Clean links, calm signing copy, tested roles, and visible support make the community feel more credible when mint, presale, token campaign, raid, or announcement traffic hits.

Vertical Ancla infographic showing a Solana holder verification launch checklist with official link, wallet signature, asset rule, Discord roles, Telegram access, recurring checks, and support plan.

A launch-ready holder gate is tested across links, wallets, roles, Telegram access, recurring checks, and support before members arrive.

The 10-minute version of the checklist

A clean launch gate is tested before traffic arrives. Use this as the fast pass before you post the verification link in announcements, X, your website, or Telegram.

CheckWhy it mattersPass condition
Exact asset ruleWrong token mint, NFT collection, or threshold creates fake failuresThe SPL token mint, Metaplex NFT collection, minimum balance, and tier logic match the launch plan
Discord roles createdThe verifier cannot assign a role that does not existHolder, whale, OG, contributor, or tier roles already exist and have clear names
Bot role positionDiscord role hierarchy can block role assignmentThe verifier bot sits above every role it needs to assign, consistent with Discord role hierarchy rules (docs.discord.com)
Channel permissionsMembers can verify and still see nothing if overwrites are wrongHolder channels allow the holder role to view and send, while non-holder roles cannot view
Telegram bot permissionsPrivate group or channel access depends on bot/admin rightsThe bot has the rights needed for invite, approval, and member management workflows (core.telegram.org)
Official verification linkFake links and DMs are a real launch riskOne official link is pinned, posted on your site, repeated by mods, and never sent by random DMs
Wallet signing copyMembers need to know what they are signingInstructions say the signature proves wallet control, has no network fee, and should never ask for a seed phrase
Pass wallet testConfirms the real holder flow worksA wallet holding the required asset receives the correct role or Telegram access
Fail wallet testConfirms non-holders stay outAn empty or under-threshold wallet does not receive access
Resync or removal testPrevents stale holder roomsA member who stops meeting the rule loses role or access according to your configured checks

Do not publish the verification link until you have tested a wallet that should pass, a wallet that should fail, and the role or access removal path.

For the broader concept behind this checklist, read Solana Token Gating: The Complete Guide. This article stays closer to launch execution.

1. Confirm the exact holder rule

Start with the asset rule, not the announcement copy.

For SPL tokens, confirm the exact token mint address, minimum amount, and whether decimals create any edge cases in your threshold. A team that says “hold 10,000 tokens” should know whether that means raw UI amount, staked balance, liquidity position, or only the wallet balance the verifier can read.

For NFTs, confirm the Metaplex collection, update authority, verified collection status, or whatever identifier your gating setup uses. The support nightmare is predictable: holders bought the right-looking asset from a secondary market, but the rule points at the wrong collection or an old migration address.

Use a simple rule sheet before configuration:

Rule fieldExample decisionSupport risk if wrong
Asset typeSPL token or Metaplex NFTMembers verify with the wrong asset
IdentifierToken mint or NFT collectionReal holders fail verification
Minimum1 NFT, 1,000 tokens, 10,000 tokensSmall holders get blocked or whales get the wrong tier
TieringHolder, whale, councilDiscord becomes a role maze
Partner assetsPartner NFT gets guest accessPartner holders flood support if not announced clearly
ExpiryTemporary campaign gate or permanent holder roomOld campaign members keep access too long

The first support ticket is usually born inside the rule, not inside the wallet. Have one owner on the team sign off on the exact mint, collection, and threshold before the server admin touches roles.

Discord setup starts inside Discord.

Create the roles first. Keep names readable: Holder, Whale, Founder Pass, DAO Voter, Partner Holder. Avoid clever names that make support harder. A member should be able to say, “I verified but did not get Holder,” and your moderator should immediately know which role to inspect.

Then check role hierarchy. Discord’s developer documentation says a bot can grant roles only when those roles are lower than the bot’s highest role. It also documents channel-level overwrites, which are often the reason a verified member still cannot see a channel. (docs.discord.com)

Minimum Discord checklist:

  1. Put the verifier bot role above every holder role it must assign.
  2. Do not put the bot above admin or team roles unless required for a specific workflow.
  3. Give the bot only the permissions needed for role assignment and access sync.
  4. Create holder channels before launch day.
  5. Check View Channel, Send Messages, Read Message History, and thread permissions for the holder role.
  6. Test with a normal member account, not only an admin account.

For a deeper Discord role walkthrough, use How to Set Up Token-Gated Discord Roles on Solana. For holder verification specifically inside Discord, keep How to Verify Solana NFT and Token Holders in Discord open while testing.

A common failure pattern looks like this:

  • Member signs correctly.
  • Verifier accepts the wallet.
  • No role appears.
  • Mods assume the wallet failed.
  • The real issue is role hierarchy.

That is avoidable. Test role assignment before the public link exists.

3. Lock down Telegram access

Telegram gating has a different failure mode. Discord problems usually look like role assignment issues. Telegram problems usually look like leaked links, wrong group permissions, and members entering through a path that bypasses the intended gate.

For a private Telegram group or channel, confirm that the bot has the admin rights your gating workflow needs. Telegram’s Bot API documents administrator rights such as inviting users, receiving join request updates, creating invite links, approving join requests, and revoking invite links. (core.telegram.org)

Telegram checklist:

  1. Use a private group or channel for gated access.
  2. Add the gating bot as an admin with the required rights.
  3. Avoid public permanent invite links for holder-only rooms.
  4. Use controlled invite links where your flow supports them.
  5. Revoke leaked links fast.
  6. Test from a non-admin Telegram account.
  7. Confirm what happens when a member stops qualifying.

The invite link is part of the gate. A perfect SPL token rule does not help if an old private group link is sitting in a public announcement thread.

For a Telegram-specific setup angle, read How to Token-Gate a Telegram Group on Solana.

4. Publish one official verification path

The official link is part of the security model.

Do not let every mod improvise. Do not let KOLs post their own shortened links. Do not ask members to search for the verifier. During launch week, scammers copy your branding, impersonate moderators, reply under announcements, and DM members with fake “urgent verification” messages.

Use one verification path:

  • Website button.
  • Pinned Discord message.
  • Pinned Telegram message.
  • Announcement channel post.
  • Mod macro with the exact same link.
  • X post pointing back to your official site or official community post.

Member-facing copy should be boring and repetitive:

Official verification link: use only the link pinned in this channel and on our website. Admins will never DM you a verification link. Use the wallet that holds your NFT or token. The verification prompt should not ask for your seed phrase.

Explain the wallet signature in plain language. Phantom’s developer docs describe message signing as a way to verify address ownership without network fees, while also noting that applications display their own message inside the wallet prompt. (docs.phantom.com) Phantom also documents domain and transaction warnings that may appear when a domain is new or when the wallet cannot predict a transaction outcome, which is a useful reminder to prepare support copy for launch-week wallet warnings. (docs.phantom.com)

Do not say “signing is always safe.” Say this instead:

  • This verification uses a wallet message to prove control of your wallet.
  • Check the domain before signing.
  • Read the wallet prompt.
  • Do not sign surprise transactions from DMs.
  • Never share a seed phrase or private key.
  • Ask in the official support channel if the prompt looks different from the screenshot.

Token gating is not your whole Discord security plan. Keep official links, impersonation reporting, locked announcement permissions, AutoMod, mod escalation, and scam reporting procedures in place. For that wider server safety layer, use How to Stop Scammers in Your Crypto Discord Server.

5. Test the full flow like a member

Admins are bad test users because they can already see everything.

Use normal accounts. Use wallets that match real holder behavior. Launch teams often test only the happy path, then discover on launch day that mobile users, hardware wallet users, or people with assets in a different wallet are stuck.

Pre-launch test set:

TestWhat to verify
Pass walletHolds the required SPL token or NFT and receives the correct Discord role or Telegram access
Fail walletHolds nothing and gets blocked cleanly
Under-threshold walletHolds some tokens but not enough and receives no gated access
Wrong walletMember connects a wallet without the asset and sees clear support guidance
Mobile walletThe signing flow works on the wallets your holders actually use
Hardware walletSupport copy exists for holders using extra signing steps
Existing memberA current Discord or Telegram member can verify without losing normal access
Seller testA wallet that no longer qualifies loses access through your resync or removal path

After each test, ask four questions:

  1. Did the member know where to click?
  2. Did the wallet prompt make sense?
  3. Did the correct access appear?
  4. Did the member know what to do if it failed?

Cleaner holder rooms also help Web3 marketing. Segmented holders make launch announcements, raid coordination, rewards, allowlists, governance pings, and contributor asks feel less noisy. The point is not just privacy. It is campaign trust.

6. Prepare support before launch traffic hits

Support macros reduce panic. They also keep moderators from accidentally giving unsafe advice in DMs.

Create a small support runbook before the announcement:

Support issueLikely causeModerator response
“I verified but got no role”Bot role too low, wrong server, wrong role mapping, channel overwriteCheck bot role position, mapping, and audit logs. Ask the member to resync only through the official link
“I hold but failed”Wrong wallet, token below threshold, NFT in another wallet, wrong collection ruleAsk: “Use the wallet that holds your NFT or token.” Then verify the asset rule internally
“I cannot see holder chat”Role assigned but channel overwrites block visibilityCheck View Channel and holder role overwrites
“I joined Telegram but cannot enter”Bot lacks admin rights, invite flow failed, old link usedCheck bot admin rights and whether the member used the current official path
“A seller still has access”Recurring check has not run, removal rule not configured, user holds another qualifying assetTrigger the supported resync path or wait for the configured check. Confirm the rule before manual removal
“Is this signature safe?”Signing anxiety, fake link fear, wallet warningRepeat official domain, explain wallet-control proof, and remind them never to share seed phrase
“Someone DMed me a link”Impersonation attemptTell them not to click it, report the account, and use the pinned official link only

Use these snippets:

  • “Use the wallet that holds your NFT or token.”
  • “Admins will never DM you a verification link.”
  • “The verification prompt should not ask for your seed phrase.”
  • “Do not use screenshots as proof. We need wallet control plus current holdings.”
  • “If the wallet prompt looks different from the guide, stop and ask in the official support channel.”

Screenshots are useful for support, not for access. A screenshot, Solscan link, or wallet address alone does not prove that a specific Discord or Telegram user controls the wallet.

7. Check resync and access removal after launch

A launch gate that never rechecks is just a snapshot.

Recurring checks matter because holders sell, transfer assets, consolidate wallets, move NFTs, and change behavior after launch. Your gated room should reflect the rule you published, not the wallet state from mint day.

Ancla’s official homepage says it gates Telegram and Discord communities to token holders, supports token and NFT gating, supports Solana for now, and positions entry and exit rules around filtering who enters and removing who sells. It also states that community checks happen on plan-based intervals, with plan details visible on the pricing section as checked on August 25, 2026. Plans can change, so verify current packaging before publishing pricing or SLA-style claims. (ancla.club)

Post-launch audit:

  1. Export or review verified members.
  2. Check whether each gated Discord role still maps to the intended asset rule.
  3. Confirm Telegram access is not open through an old invite link.
  4. Review support tickets for repeated failure patterns.
  5. Test a fresh pass wallet and fail wallet again after launch.
  6. Confirm seller removal or access cleanup behaves as expected.
  7. Remove manual exceptions unless there is a clear team-owned reason.

Do not hide removal rules. Tell holders that access depends on current holdings. That makes the gate feel fair and reduces “why did I lose access?” tickets later.

Where Ancla fits

Ancla is built for Solana teams that need holder verification without turning launch ops into a custom bot project.

Use Ancla when you need:

  • SPL token gates.
  • Metaplex NFT gates.
  • Discord roles.
  • Telegram access.
  • Gasless wallet signatures to prove wallet control.
  • Recurring checks so access does not become stale.
  • Seller removal or access cleanup based on the rules you set.
  • A simpler setup path for founders, CMs, admins, and moderators running real launch traffic.

Ancla is not KYC. It does not verify legal identity, age, liveness, AML status, or whether a member is a good actor. It verifies wallet control and onchain holdings, then helps keep Discord and Telegram access aligned with those holdings.

That is the right job for a Solana launch gate.

Try Ancla free at ancla.club/select-plan.

Trusted by Solana communities running on Ancla

Frequently asked questions