No reputation review yet
A new token can remain Unclassified until an eligible project or community representative submits the official form.
Understand Solscan’s default Unclassified reputation, why it can hide a token logo and what evidence a reputation update requires.
CheckMyMint prioritizes evidence and dependencies so you can avoid repeating a valid update or paying the wrong platform.
A new token can remain Unclassified until an eligible project or community representative submits the official form.
Solscan requests a functioning website, official email, public logo, description and working social links.
Solscan can update information displayed in its interface but cannot alter token metadata on your behalf.
Unclassified is a Solscan reputation state, not a diagnosis that the mint or image is technically invalid. Solscan explains that most tokens begin in this category and that an Unclassified token may not display its logo, which is why an otherwise healthy project can look incomplete only on Solscan.
Resolve this by proving both technical correctness and project legitimacy through Solscan's documented process. Validate the metadata first so the application does not contain broken resources, then prepare the functioning website, public logo, neutral description, social links, and project-domain contact evidence requested by the platform.
Open the exact mint on Solscan and record the current label and visible fields. Do not infer the state from a missing image alone because technical image failures can produce a similar symptom.
Inspect the correct Metaplex or Token-2022 source and test the JSON and image publicly. Save the canonical URLs and response details for the update package.
Use a functioning project website, project-domain email, stable public logo, complete socials, and a factual neutral description. Ensure the mint address is consistent everywhere.
Follow Solscan's official token update and reputation guidance. Keep free and any optional priority handling distinct, and verify current terms before choosing a route.
After submission, track whether descriptive fields changed and whether the reputation changed. One can update before the other, so neither should be treated as automatic proof of final review.
On-chain metadata changes do not directly control Solscan's platform-specific reputation classification.
A neutral, verifiable project description is stronger evidence than price claims, hype, or unsupported superlatives.
A logo that requires authentication, expires, or returns the wrong content type undermines an otherwise complete reputation request.
The token logo and identity are consistent on-chain and on Jupiter, while Solscan labels the mint Unclassified and suppresses the image.
The platform-specific reputation state explains the isolated display issue; another metadata transaction would not target the cause.
Submit a complete Solscan reputation update using official guidance and maintain the valid canonical metadata while review is pending.
No. It is Solscan’s default state and does not by itself mean the token is malicious.
Not when reputation policy is the reason it is hidden. Validate metadata, then use the official Reputation Update route if appropriate.
Use Solscan's current official guidance to confirm eligibility and required project evidence. The request should represent the project accurately and use verifiable first-party information.
The Unclassified label is a Solscan reputation state, not a trading switch. Market availability depends on the token and its liquidity venues rather than logo visibility alone.
Third-party workflows change. CheckMyMint links to official documentation and displays when the platform rules were reviewed.