How permanent is data stored on IPFS? #93
Comments
Permanence != Persistance Permanence is about naming: content-addressing makes it so that an object's name will always be the same. The "permanent web" is a web of links between objects with permanent names. The names are always the same, and thus the links won't break. Persistance is about storage: IPFS itself currently handles this by means of "pinning", which excludes an object and its children from garbage collection within one IPFS node. In the future there will be more involved ways of managing persistance. One of them is Filecoin (paper), and there a couple of concrete ideas for an ipfs-cluster tool (ipfs/notes#58). |
This one is also related: Replication on IPFS -- Or, the Backing-Up Content Model |
To add to this, the way you should think about it is this: Basics:
Advanced Collaboration + Replication:
|
Keeping this open so that it is more easily finable in the FAQ. Thanks. :) |
This issue has been moved to https://discuss.ipfs.io/t/how-permanent-is-data-stored-on-ipfs/354. |
In the whitepaper it says 'Objects are permanent'.
How can they be if there is no guarantee that all the 256KB objects that make up my original file are on other people's nodes? What if they ipfs repo gc? There has been talk about using IPFS as a versioned backup system but is my data really going to live forever out there?
Also, if I'm storing other people's objects, then I could also read the data in them, right?
The text was updated successfully, but these errors were encountered: