My money is on IPFS, because it’s so simple (like, in principle, obviously it’s complex under the hood).
It’s not fancy, it’s basically a better version of torrent and only handles static data, but it does that really fucking well.
It takes any data you add to your node, splits it into small blocks, does a fancy hash of those blocks, and then builds a tree of pointers that point to pointers that point to the constituent blocks. This means that any identical blocks have the same address, and thus only need to be sent once! And the same goes for anything that ends up being identical in structure, it has the same address and only needs sending once, and if for example two people rip a copy of the same obscure DVD and host it on a node, they will both provide the data to downloaders despite never having interacted with each other at all!
This is of course massively boner-inducing for anyone who cares about archiving stuff.
In effect it does the same thing that HTTP or FTP or whatever does, but in a modern and fundamentally decentralized way. You don’t care where the data comes from, you just request the ID from whatever nodes you can see, if they don’t have it they forward the request to those they can see etc etc, if anyone has it they reply to you and start sending the data, and then you do some fancy math to verify that it’s correct.
My money is on IPFS, because it’s so simple (like, in principle, obviously it’s complex under the hood). It’s not fancy, it’s basically a better version of torrent and only handles static data, but it does that really fucking well.
It takes any data you add to your node, splits it into small blocks, does a fancy hash of those blocks, and then builds a tree of pointers that point to pointers that point to the constituent blocks. This means that any identical blocks have the same address, and thus only need to be sent once! And the same goes for anything that ends up being identical in structure, it has the same address and only needs sending once, and if for example two people rip a copy of the same obscure DVD and host it on a node, they will both provide the data to downloaders despite never having interacted with each other at all!
This is of course massively boner-inducing for anyone who cares about archiving stuff.
In effect it does the same thing that HTTP or FTP or whatever does, but in a modern and fundamentally decentralized way. You don’t care where the data comes from, you just request the ID from whatever nodes you can see, if they don’t have it they forward the request to those they can see etc etc, if anyone has it they reply to you and start sending the data, and then you do some fancy math to verify that it’s correct.