The following is a summary of a talk given by Alan Shaw, Core Developer at IPFS. Watch the full recording here:
If you import data to an IPFS node, you get what is called a content identifier, or CID. CIDs are what make IPFS unique when it comes to storage because CIDs address content instead of the typical
https:// location-based addressing.
It’s important to note that CIDs are a cryptographic hash of the content. This means that:
- Any change to the content will produce a different CID.
- The same content added to two different IPFS nodes using the same settings will produce the same CID.
CIDs are very important to NFT storage because they help prevent “rug pull”, or the issue when NFT addresses are changed to lead to something else than the original NFT content. CIDs allow for safer NFT storage long term.
To help NFT creators and owners more easily store their NFTs with CIDs, IPFS and Filecoin offer https://nft.storage/ (opens new window), a brand new service built specifically for storing off-chain NFT data. Data is stored decentralized on IPFS and Filecoin.
The nft.storage demo in this talk walks you through:
- Uploading data to nft.storage using the JS client in Node.js and the browser
- Managing API keys
- Data retrieval via IPFS gateways
- Querying for information about stored data: file size, IPFS pinning status and Filecoin deal status
Along with nft.storage and Minty, IPFS and Filecoin have comprehensive documentation on CIDs (opens new window), an article detailing the differences between content addressing and content integrity (opens new window), a best practices guide to long term NFT storage (opens new window), and how to mint NFTs on IPFS with Minty (opens new window). Also, check out NFT School (opens new window) for a collection of tutorials, how-tos, and concept guides on NFT best practices and NFTs in general.
- Nothing in these presentations is investment advice.
- Any models shown in presentations are based on many assumptions, and should not be relied upon as the source of truth. Any estimates should not be relied upon and are for illustrative purposes only. You should build your own models based on the code and the Filecoin spec.