metadata schema for
ERC721 Tokens requires three properties to be populated for each Token:
So if we created a collectible-game called say "CryptoHippos", we could populate these properties as follows:
name - "CryptoHippo Token#123" (where the # would of course change for each Token)
description - "Another unique creature from the super-addictive CryptoHippo Blockchain Game!"
image - "http://www.cryptoHippos.com/images/CryptoHippo123.png"
Or something like that.
Now let's say our game is a huge hit and someone decides to steal some of our thunder by creating their own "hippo" contract that generates Token-metadata that is 99.9% identical to ours, as follows (see if you can spot the difference):
name - "CryptoHippo Token#123" (here they make an exact copy of our
description - "Another unique creature from the super-addictive CryptoHippo Blockchain Game!" (same thing: an exact copy of our Metadata)
image - "http://www.cryptoHippoos.com/images/CryptoHippo123.png" (here they have to use a slightly different URL - it's just one letter off - because they obviously can't access our domain)
So, if they put these tokens out there, my questions are:
- How would the average consumer know that these are not authentic "CryptoHippo" tokens? The
descriptionproperties certainly says they are, so how would they know they're not?
- What if we decided to store the images of our tokens on IPFS and not host them on our
cryptoHippos.comserver - meaning that instead of our very true and authentic
cryptoHippos.comdomain appearing in the Token's metadata, the generic
ipfsdomain would appear, making it even easier to fake Tokens to seem authentic - so what then?
Seems like the metadata is very hackable.
Is there some other technique, trick, or different approach to take to ensure Tokens aren't fake-able?