How can we ensure the metadata (name, symbol, image) shows up on the Phantom wallet? #427
Replies: 3 comments
-
|
Hey @scromie, We are investigating a possible bug affecting this. Apologies for the trouble! |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your answer! Basically, I need to be able to provide my client with a token with all the metadata showing up in Phantom, whether T22 or SPL, which does not have community traction yet. They want to launch it with a liquidity pool and airdrop it, and something showing up with no metadata looks incredibly suspicious. |
Beta Was this translation helpful? Give feedback.
-
|
Is there any update here? Thanks! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
I have created several tokens, both SPL and Token22, and they show up properly on the Solana explorer but not in the Phantom wallet (nor on Solscan, if that matters). I am unsure what is required to ensure that the metadata comes through.
I am also using the solana command line tools in order to do this. I create the on-chain data, and in the on-chain data is a uri field which points to the off-chain metadata (which is stored through ipfs using pinata), and that off-chain metadata points to the image url (also stored on ipfs through pinata).
I have seen many different answers out there in support groups, on youtube videos, and the like, and those do not give me any answers.
I did notice that the token-list in this repo was the old way to do this, but it was recently archived a few weeks ago. It looks like you have a new verification method, but I am not sure that will work in this case because we are launching the token through meteora ourselves and we will need the metadata to show up properly to ensure the community will trust us.
Our client is getting tired of waiting and we need this token to be perfect. Is there a concise set of instructions that tells us exactly how to create a token using the solana SPL library (i.e. using the tokenkeg.... program) that will be guaranteed to appear in Phantom?
Here is a link to one of the test tokens I created (on Devnet) - the metadata comes through on the Solana explorer:
TokenId: Ukc6z5qob4kjnPUfTfNBvaPP1WiMbsZBt9CvnaXENBN
Solana Explorer link: https://explorer.solana.com/address/Ukc6z5qob4kjnPUfTfNBvaPP1WiMbsZBt9CvnaXENBN/metadata?cluster=devnet
I also attempted another token using the Token22 library and that yielded the same result:
Token Id: u3izZpEZR4XC1NJT2MUSkmqbATmQHNR33kBVj6MTkBH
Solana Explorer link:
https://solscan.io/token/u3izZpEZR4XC1NJT2MUSkmqbATmQHNR33kBVj6MTkBH?cluster=devnet
Solscan link:
https://explorer.solana.com/address/u3izZpEZR4XC1NJT2MUSkmqbATmQHNR33kBVj6MTkBH?cluster=devnet
So, I don't know what needs to happen what I need to do in order to get this to show up, be validated, etc.
I have also logged a support ticket for this, and after a few interactions he referred me to this forum.
Please let me know how I should create the token so that it's valid to display.
Example
https://explorer.solana.com/address/Ukc6z5qob4kjnPUfTfNBvaPP1WiMbsZBt9CvnaXENBN/metadata?cluster=devnet
Steps to Reproduce
I created the token using the umi library from Metaplex.
Phantom Version
25.14.0
Is there an existing discussion for this?
Beta Was this translation helpful? Give feedback.
All reactions