Executes what you enter.
Useful when you already know the correct metadata path, authority state, asset format and downstream consequences.
Transaction utilityCheckMyMint diagnoses why the logo is wrong, prepares the compliant asset, fields and evidence, then routes you through the official on-chain or platform workflow. No blind edits.
A missing logo does not always require an on-chain metadata change. CheckMyMint determines whether the correct route is an authority-signed metadata update, an asset repair, an upstream registry correction or a platform-specific official submission.
We sit between diagnosis and the official provider workflow. We prepare everything needed; you retain the wallet, account and final Submit action.
Useful when you already know the correct metadata path, authority state, asset format and downstream consequences.
Transaction utilityCan be appropriate when canonical metadata is healthy and that specific platform profile is the actual problem.
Provider-specific purchaseWe identify the broken layer, prepare the asset, fields, evidence and official route, then recheck live status after you submit.
Independent submission preparationSame-day preparation is our target for eligible requests. We remove research, formatting and form-preparation time; we do not pretend to control third-party review queues.
Each step exists to prevent an unnecessary transaction or an update at the wrong layer.
We separate canonical metadata, broken assets, upstream registries, reputation and platform-specific profiles.
The plan may be an authority-signed update, asset repair, registry correction, platform submission or simply monitoring.
We assemble the correct logo, public URL, description, links, evidence and copy-ready platform fields.
You retain the authority wallet and provider account. CheckMyMint never receives private keys or impersonates the project.
Canonical and platform evidence is rechecked, with clear next steps if a cache or review remains pending.
Current-state evidenceExisting metadata, image delivery, upstream dependencies and platform records.
Production-ready logoCorrect bytes, dimensions, public URL and provider-ready variants.
Copy-ready fieldsNeutral description, website, socials, mint, evidence and project-domain email checklist.
Official submission routeThe correct provider form or authority-controlled transaction workflow.
Monitoring checklistEvidence showing what changed, what is pending and when another action is justified.
Changes after the authority wallet signs a valid update for mutable metadata.
Customer-controlledOften refresh canonical data automatically, but cache timing varies by product.
Third-party timingMay combine canonical metadata with external lists, profiles, reputation or paid updates.
Separate workflows possibleVerification and reputation are not purchased by changing the token image.
No approval guaranteeWe resolve the current identity before checkout. Then we determine whether the right route is canonical metadata, an upstream registry or an official platform submission.
No. The metadata must still be mutable and the customer must control the relevant update authority. If authority was revoked or the metadata is immutable, an on-chain logo change cannot be performed.
Never. CheckMyMint prepares and validates the update, but the authority wallet signs the on-chain transaction. Never share a seed phrase with any metadata service.
CheckMyMint prepares the correct asset, fields, evidence, checklist and official route. The project owner retains the provider account and presses Submit, or signs the on-chain transaction from the update-authority wallet.
For eligible tokens, CheckMyMint targets same-day preparation of the corrected asset and metadata package. On-chain confirmation is fast after signing, but third-party platform caches and reviews have their own timelines.
Not necessarily. Canonical metadata may update immediately while wallets, explorers and market platforms refresh later. Some platforms use additional lists, reputation systems or paid submission products.
No. The service fee covers CheckMyMint preparation, guidance and verification. Optional third-party charges, including DEXScreener Enhanced Token Info, remain separate.
The eligibility review identifies the token metadata architecture first. Supported updates depend on the detected metadata path, mutability and authority configuration.
The authority and mutability check occurs before update work begins. An immutable token is not presented as updateable, and alternative platform-specific options are explained where relevant.
Our workflow follows first-party Solana and platform documentation rather than assuming every display reads the same source.