1

Imaging you have an ERC721 contract with an infinite max supply. Usually, the metadata IPFS url will be the base url concatenated with the token ID: ipfs://[base-url]/[token-id]. Say we are up to token ID 4000, and someone decided to create malicious metadata at IPFS location ipfs://[base-url]/4001, and then mint a new token, what is stopping this from happening? Is there any way to write protect the base url? If not, is it only possible to solve this problem by making the next token ID unpredictable? Thanks in advance.

1 Answer 1

1

If you are publishing to a URL that starts with ipfs://ABC then:

  1. Anybody can inspect all the files in all paths starting at ABC.
  2. Nobody can change the contents of the paths starting at ABC.

This is a major design of the system. In fact, the choice of the letters ABC is based on the contents of all the files in all paths underneath it.


Applying to your question that means by the time ipfs://[base-url]/4000 is published, ipfs://[base-url]/4001 is already known and unchangeable.

1
  • 1
    Ah yes i get it now. As you are saying and as indicated here the base path (ABC) will change if the content in a directory is changed and this is handled under the hood when using the Files API. Jun 17, 2022 at 5:31

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.