The wrong account was changed
Token-2022 metadata extensions and Metaplex metadata accounts are distinct sources that consumers may support differently.
Solana metadata troubleshooting
Solana token metadata not updating?
Trace stale Solana token names, logos and links through update authority, metadata architecture, asset hosting and downstream caches.
Metaplex PDAOne metadata path
Token-2022 extensionAnother metadata path
Downstream refreshIndependent
What the scan separates
The same symptom can need a completely different fix.
CheckMyMint prioritizes evidence and dependencies so you can avoid repeating a valid update or paying the wrong platform.
The URI changed but the asset did not
Cached filenames, identical URLs or inaccessible JSON can make an update appear ineffective.
Update authority is missing
Immutable metadata or a different update authority prevents additional changes even when the wallet owns the token supply.
Solana troubleshooting guide
Diagnose the source before changing the token.
A successful Solana transaction proves that a particular account instruction executed; it does not prove that every consumer reads that account, that the off-chain URI serves new content, or that platform caches have refreshed. Metadata updates can therefore be correct on-chain while appearing stale elsewhere.
Diagnose from the mint outward. Identify whether consumers should read Metaplex or Token-2022 extensions, verify the current authority-controlled values, fetch off-chain resources independently, and compare timestamped platform records. The first stale boundary determines whether to repair data, correct the metadata path, or wait for downstream propagation.
Evidence-first process
Work through the problem in this order
- 01
Verify the confirmed transaction
Inspect the transaction and changed account rather than relying on an editor's success message. Confirm that it targeted the correct mint and the metadata architecture used by the token.
- 02
Read current on-chain values
Fetch the live metadata account or Token-2022 extension and compare its name, symbol, and URI with the intended update. Check authority and mutability when further changes may be required.
- 03
Fetch off-chain content cleanly
Request the URI and image outside the upload tool. Confirm that the new JSON and image bytes are public, valid, and not hidden behind an old gateway response or browser cache.
- 04
Build a propagation map
Record the value shown by Jupiter, DEXScreener, Solscan, Birdeye, and Phantom at the same observation time. Multiple stale platforms point upstream; one stale platform points toward its own cache, profile, or policy.
- 05
Change only the broken dependency
Correct the account, URI, or asset only when evidence shows it is wrong. Otherwise preserve the valid source and monitor or follow the affected platform's official update process.
Avoid unnecessary work
Common mistakes
Assuming transaction success equals ecosystem refresh
Independent indexers and applications can cache or source token information differently after the chain state changes.
Updating the wrong metadata mechanism
A Token-2022 extension and a Metaplex metadata account are distinct paths; changing one does not ensure that a consumer reads it.
Overwriting content at the same URL
Mutable files behind unchanged addresses make cache invalidation ambiguous and can preserve the previous logo across gateways.
Worked example
Confirmed transaction, old downstream logo
Observed
A Metaplex update transaction is confirmed and its URI changed, but Phantom and DEXScreener still show the old image while the new JSON works.
Diagnosis
The canonical update is correct. The remaining discrepancy begins at downstream consumers rather than the Solana metadata account.
Smallest correct fix
Keep the new source stable, compare each platform's official profile or upstream dependencies, and monitor before sending another metadata transaction.
Start with the free scan
Know what needs fixing before you spend.
Solana answers
Frequently asked questions
Why does Solscan update but Phantom does not?+
Each consumer has separate source, recognition and cache rules. One platform changing does not guarantee another has accepted the same source.
Can I force every platform to refresh?+
No universal refresh transaction exists. Correct the canonical source, then follow platform-specific workflows only where required.
How do I know whether a metadata transaction changed the right account?+
Identify whether the mint uses Metaplex or Token-2022, inspect the relevant account after finalization and compare the exact URI and fields instead of relying on a cached interface.
Should I use a new image URL when updating a token logo?+
A versioned, stable public URL can make changes easier to verify and reduce ambiguity from stale caches. The new asset must still return the correct content type without restricted access.
First-party references
Sources used for this guide
Third-party workflows change. CheckMyMint links to official documentation and displays when the platform rules were reviewed.