First Flight #12: Kitty Connect

First Flight #12: Kitty Connect
Beginner FriendlyFoundryNFTGameFi
100 EXP
View results
Submission Details
Severity: low
Invalid

Kitty NFT uses non-standard metadata structure, making it difficult for marketplaces to retrieve information about the kitty

Summary

The structure of the NFT metadata includes properties/fields that does not follow the recommended ERC-721 standard, most marketplaces (e.g. OpenSea) follow the standard to pull data of the NFT to show it in their application.

A user interested in selling their NFT would've problems in doing so because marketplaces will be unable to pull all the data of the NFT because of the non-standard properties included in the token URI.

Vulnerability Details

The KittyConnect::tokenURI returns the following metadata structure:

{
"name": "Meowdy",
"breed": "Ragdoll",
"image": "ipfs://QmbxwGgBGrNdXPm84kqYskmcMT3jrzBN8LzQjixvkz4c62",
"dob": 1,
"owner": "0x6ca6d1e2d5347bfab1d91e883f1915560e09129d",
"shopPartner": "0x70997970c51812dc3a010c7d01b50e0d17dc79c8"
}

Properties like breed, dob, owner and shopPartner are not part of the recommended metadata structure, marketplaces would not know how the fetch this data to properly indexed the token in their application.

Tools Used

Manual review

Recommendations

I recommend following OpenSea recommendations on how to create a rich metadata structure for the kitty for easily integration with marketplaces. See recommendations.

Updates

Lead Judging Commences

inallhonesty Lead Judge over 1 year ago
Submission Judgement Published
Invalidated
Reason: Design choice

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.