-
Notifications
You must be signed in to change notification settings - Fork 4
IPFS
We are using IPFS to store the NFT images and audio. IPFS is not a service that is storing data for the user. IPFS is a protocol that makes it possible that data can be stored on multiple location, and it can be referred by a unique identifier. It's one step forward from torrent. Similarly, as a torrent can be dead, an IPFS CID can also link to a content that does not exist anywhere in the network anymore. A very good resource on IPFS is proto.school
Our own server runs an IPFS node, and that's where the uploaded files will be stored first. We are using the Go implementation of IPFS, that was previously called go-ipfs, now it is called kubo. This is the repository for kubo: https://github.com/ipfs/kubo
The IPFS software is turned into a service by the config file that is at /etc/systemd/system/ipfs.service
To check the status of our IPFS node, type service ipfs status.
After the file was added to our local IPFS node, it will be pinned by multiple pinning services, see Services Used for Storage