Blockchains are more complicated than other distributed storage applications, because they have to enforce a global ordered history. It's very important whether Transaction A or Transaction B came first.
This is a huge design constraint, and it makes it much harder to design scaling solutions. Any prior block could potentially affect the validity of a new block, so new clients must download every old block and check them.
It doesn't make any sense to keep this constraint if you're designing a distributed data storage system. If there's a missing piece of data for an old block, the storage system should ignore that and keep going.
Storj don't save data in the blockchain but this is a good option. – Sklavit – 2016-05-08T22:15:40.400