Tokens don't display on cnft.io if non-721 metadata is also present.

[bwbush]

If a token's minting transaction has multiple metadata tags, such as 721 for the token metadata according to CIP-25 and also 674 for a message according to CIP-20, then the token is not displayed at all in cnft.io. It seems preferable for cnft.io to ignore all non-721 metadata and display any token that has correct 721, regardless of other metadata in the minting transaction.

These contrasting minting transactions highlight the problem:

• Displays in cnft.io: https://cardanoscan.io/transaction/bb5bc30de4fa4fb64e95629ac32a531b1054d2968928614a95415fa17ca3277f?tab=metadata
• Does not display in cnft.io: https://cardanoscan.io/transaction/4c179ea7bc8a65641156b79b4949261267a2463dd201aa0f2aab2bd509d56759?tab=metadata

[santonode]

PigyToken is a breeding game use case. It has support from over 100 Stake Pools, The breeding of Pigys is what make the tokens unique and more valuable. I would support finding a resolution to this issue. Chris with Santo Stake Pool

[GlynnPowell]

So what happens if you have custom)fields for traits . e.g.

"#00002": { { "name": "#00002", "description": "UG2.", "image": "ipfs://TEST/00002.png", "mediaType": "image/png", "background": "sunset", "body": "blue", "clothes": "dress", "ears": "gold", "glasses": "shades" } }