0

For example https://token-cdn-domain/{id}.json. Can Opensea and other similar clients read this kind of metadata link? Or I should override the uri() function like this

function uri(uint256 _tokenId) override public pure returns (string memory) {
     return string(
          abi.encodePacked("https://token-cdn-domain/",Strings.toString(_tokenId),".json")
     );
}

1 Answer 1

0

As far as i know ERC1155 is itself supported by opensea ! So you don't need to change anything incase of opensea it'll fetch the metadata automatically

4
  • According to Opensea metadata standard, "When queried, this URL should in turn return a JSON blob of data with the metadata for your token.". But as ERC1155, it only returns link with {id}. SO I'm not sure if Opensea can read it or not
    – dtnwen
    Apr 29, 2023 at 7:37
  • I've deployed many ERC1155 tokens and i could see them all on opensea! have you tried yourself Apr 29, 2023 at 13:43
  • What should I set the metadata file name? Like this 0000000000000000000000000000000000000000000000000000000000000000.json?
    – dtnwen
    May 2, 2023 at 7:18
  • you can start from 0.json and move ahead with number 1.json and 2.json May 3, 2023 at 13:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.