Open khcd opened 1 week ago
We're about to release some new sdk functionality and docs that will help build the metadata.
Until this is out, contract metadata has the following json schema:
{
"name": "{contract name}",
"description": "{contract description}",
"image": "{contract image}"
}
Token metadata has the following json schema:
{
"name": "{token name}",
"description": "{token description}",
"image": "{token image ipfs url}",
"animation_url": "{token media ipfs url}",
"content": {
"mime": "{content mime type}",
"uri": "{content ipfs uri}"
},
"attributes": {
"trait_type": "{trait type}",
"value": "{trait value}"
}
}
Contract and token metadata should be pinned to IPFS using a preferred pinning service,
and the url when set on a contract or token should be in an ipfs url format, like: ipfs://{cid}
couple of questions:
thanks