Need assistance with TON NFT metadata visibility issue

NFT
1

I’m having trouble with my TON NFT metadata. I’ve minted an NFT and the item contract shows it’s initialized with content. But the metadata isn’t showing up in my wallet or on tonviewer. What could be the problem?

Here’s a sample of how I’m setting up the metadata:

function createNFTMetadata(data) {
  console.log('Processing metadata:', data.picture);
  
  const metadataDict = Dictionary.create()
    .add(hashString('title'), textToCell(data.title))
    .add(hashString('info'), textToCell(data.info))
    .add(hashString('picture'), textToCell(data.picture));
  
  return Cell.begin()
    .addUint(0, 8)
    .addDict(metadataDict)
    .end();
}

Any ideas on what I might be doing wrong or what I should check next? Thanks for any help!

2

hey there leapingfox! interesting question about ton nft metadata :thinking:

ive run into similar issues before. have you double-checked that the metadata uri you’re using is accessible and properly formatted? sometimes wallets and explorers have trouble reading the metadata if the uri isnt quite right.

also, how long ago did you mint the nft? in my experience, it can sometimes take a little while for the metadata to propagate and show up properly. maybe give it a few hours and check again?

out of curiosity, what wallet are you using to view the nft? some wallets handle metadata better than others. have you tried checking it on multiple explorers/wallets to see if the issue is consistent?

let me know if any of that helps! always happy to brainstorm more if youre still stuck. nft metadata can be tricky sometimes!

3

I’ve encountered similar issues with TON NFT metadata visibility. One thing to consider is the content cell format. Ensure you’re using the correct off-chain format as specified in the TON NFT standard. The metadata should be a JSON object stored off-chain, with the content cell containing a URL to this JSON.

Additionally, verify that your metadata JSON is properly structured and accessible at the URL you’ve specified. Sometimes, network latency or caching can delay metadata updates. If you’ve recently minted or updated the NFT, allow some time for propagation.

Lastly, try querying the NFT contract directly using a TON API or SDK to confirm the metadata is correctly set at the contract level. This can help isolate whether the issue is with the contract or the viewer/wallet implementation.

4

yo leapingfox, metadata issues can be a pain! Have u tried using the IPFS format for ur metadata? Sometimes that works better for visibility. Also, double-check ur metadata structure - make sure it follows TON standards exactly. if all else fails, maybe try re-minting? Good luck man!