Slingshot uses a community-driven approach to indicate that certain tokens have been checked by enough community members to warrant additional visibility. A “Verified” label can help you identify tokens that have garnered a higher level of community trust or interest. However, it is not an authoritative or foolproof indicator.
How does a token become verified?
Community Voting: Users can vote on any unverified token to help it progress toward verification.
Manual Review: Once a token gathers enough votes (10 votes), it goes through a manual review process. If everything looks legitimate, the token is marked “Verified.”
What verification does not guarantee
Even if a token is marked “Verified,” that does not guarantee it’s risk-free or backed by an official authority. Verification represents a snapshot in time: a token may have had decent liquidity or non-malicious code at the moment of review, only for conditions to change (e.g., drained liquidity or updated contract logic) afterward. Malicious tokens can still appear verified if they meet certain criteria and pass manual checks at a particular point in time.
Best practices
Always DYOR (Do Your Own Research): Verification is just a signal, not a guarantee. Review the token’s liquidity, contract, developer reputation, and community sentiment.
Stay Alert: Even verified tokens may hold hidden risks, such as upgrades, high taxes, or honeypot features not detectable by scanners
Use Other Tools: Check block explorers, community forums, social media, or third-party scanners for additional safety checks.
Need more help?
For further assistance or troubleshooting, click on the chat bubble at the bottom right of this screen, or from within the app, under Profile → Settings → Help Center → Contact Support.