Metadata not shown on fungible token after minting
Opened this issue · 8 comments
I have checked throughly , and here the pictures proofs
For some reasons , when i minted fungible token on meshjs , it doesnt show up properly on eternl.io wallet. But just a month ago , with the same data and tool , it showed up properly . eternl.io does regconize its fungible token . non fungible token show up properly on eternl.io with same tool.
Hi, could you please try the refresh button top left corner of the metadata modal?
Hi, could you please try the refresh button top left corner of the metadata modal?
Sir , I was very busy , but as you can see , it has been 2 weeks already , and the data never updates.
Here is the link to the asset on the preprod scan:
https://preprod.cardanoscan.io/token/asset1ezhyww3n6lm28t3wdtql652w4xfjrlunrm9s3j
Its definitely on the preprod scan , but it just doesnt show up on Eternl.io wallet.
Hi, could you please try the refresh button top left corner of the metadata modal?
Sir , I was very busy , but as you can see , it has been 2 weeks already , and the data never updates.
I had a look at the metadata now and I haven't heard of format using label 20 before. It seems to use same structure as 721. So a quick fix would be to use that instead. But I will look into this and see if there is an CIP that describes metadata with label 20.
I had a chat with Mesh team and now understand that label 20 metadata is something that was proposed a couple of years ago but has yet to be approved as a standard. Its currently unclear if we will support this or not.
The currently approved method is to use CIP-721 metadata together with offline github token registry(CF for mainnet and IOG for testnets) for FT data like decimals etc. But we will discuess internally of potentially support it in a future release.
I see . Thank you for your help . We will find a way to work around for now . As of now , which label should we set for native tokens so that they show up properly ?
I had a chat with Mesh team and now understand that label 20 metadata is something that was proposed a couple of years ago but has yet to be approved as a standard. Its currently unclear if we will support this or not.
The currently approved method is to use CIP-721 metadata together with offline github token registry(CF for mainnet and IOG for testnets) for FT data like decimals etc. But we will discuess internally of potentially support it in a future release.
I think we will add 20 metadata support soon so you could do both that and register your token in the offline token registry.
I see , thanks a lot for your help !