When several Solana tokens share a name, use the intended issuer’s full mint, corroborated on-chain and by another established source. Names and symbols can repeat; each token has a unique mint account.
A rugcheck reviews token warning signs linked to scams or rug pulls. Use rugcheck once the mint is settled; a same-name copy yields a report on a different asset.
Which mint should you verify first?
Start with the issuer’s published mint for the intended asset version. Have the official site or announcement and your wallet or trading page ready. Projects can have an older token, a migrated replacement, or a bridged version under similar branding. You are ready when issuer and version are explicit, since the next checks must match one asset.
- Find the issuer record. Open the project’s official site, release note, or pinned announcement and copy the complete Solana mint. Save the page link beside it. You now have an address tied to a named issuer and version, rather than a row of identical tickers.
- Corroborate the mint independently. Search an established token listing by address, then compare its project links and asset description with the issuer record. The same complete mint should appear in both places. A name search alone is only a lead.
- Inspect the address on Solscan. Paste the copied address into Solscan. Confirm a mint page with the same address and token details such as supply and decimals. A wallet address identifies an owner; a Token account holds units for a mint; a Liquidity pool address belongs to a market. If you land on a Token account, follow its mint field. You should end on the mint account, rather than an address displayed near the token name.
- Resolve disagreements before selecting a version. If sources disagree, find an issuer announcement naming both mints, explaining the migration or bridge, and stating which version your destination accepts. Say an older token has more holders while a newer mint appears in the migration notice: popularity cannot establish which version you intend. You need a documented mapping and selected version; without one, pause.
- Save and test the exact address. Copy the chosen mint again, compare every character with the issuer record and listing, then paste it into the destination and compare its displayed address. Save the mint with both source links and the version label. You are done when the complete mint matches across sources and destination.
Related questions
Can a Solana token change its mint address?
A replacement mint creates a different token identity. An issuer can migrate holders to a new mint, but use its explicit announcement to connect the old version with the replacement before choosing either address.
Is a verified token badge enough?
A badge is a useful clue, but its criteria vary by platform. Match the complete mint against issuer records and the destination even when a listing marks the token verified.
What might you need to do next?
How do I identify a bridged Solana token?
Find the bridge operator’s asset record and match its Solana mint to the issuer’s named bridged version.
How do I add a verified token to my wallet?
Use the wallet’s custom token flow and paste the saved mint, then compare the displayed address before adding it.
What should I do with an unsolicited token airdrop?
Leave unfamiliar tokens alone while you identify their mint and issuer; avoid following links embedded in token metadata.
How can developers validate a mint programmatically?
Fetch the account, verify its token program owner and mint data, then compare its address with the issuer’s published value.