Way cheaper than AWS, and a lot less headache than trying to run it all yourself.
34 karma · joined June 11, 2014
Way cheaper than AWS, and a lot less headache than trying to run it all yourself.
Its only expensive because cloud providers overcharge. The listed prices on Tardigrade start at half of Amazon S3, and there are significant discounts if you are storing more than 100 TB.
Disclaimer: My company Storj is building a distributed Amazon S3 competitor and we are actually partnered with MongoDB. We share revenue with MongoDB for any customers they bring us.
Basics are data stored for each. Storj: ~1400 TB, Sia: ~100 TB, Filecoin: Not Functional, Maidsafe: Not Functional.
I disagree that its devoid of how does it work, but sure I could see someone wanted more info in the video. What do you suggest needs to be included?
Storj is a direct competitor to Amazon S3. We don't have to educate the public, just the developers that need to store data somewhere.
We were focused on writing the code first, and now we are in the process of writing down what we learned. Don't take me at my word, but do give me a few weeks to prepare a more formal paper now that most of our core code has been implemented or speced.
As far as the $6M we don't intend to raise that much. What is left over will be distributed through the early mining, and future crowdsales for other platforms build on top of Storj(decentralized Youtube, Imgur, etc.) In that way we can give the network a kickstart with the actual resources that it needs to survive.
If sidechains or treechains become viable we plan to merge it back in to Bitcoin proper.
That paper was written before decentralized storage was really just a new idea. I've since implemented a baseline core algorithm, and we have one application running.
I'm in the process of rewriting the whitepaper. Hopefully will put out a draft in two weeks(I'll be at conferences all this week). From there I want to actually collect network data(after all I'm trained as a researcher and what is good paper without any data?) before putting out a solid draft to be peer reviewed.
To affect a file large amount of nodes would have to go down simultaneously. Again the user has control over this N = 1 - Data failure N = 3 - Good for just average cases. Probably still Sybil attacks possible if the have 20-30% of the network. N = 100 - Are you expecting tactical nuclear strikes or acts of God?
Cool thing is if you increase redundancy to a large number Storj starts to act like a CDN or torrent network. But thats outside the scope of your question.
Bitcoin only supports up to 80 byte of data per transaction, our model uses 1 kb or more, which makes unusable for our current platform. We are not creating another cryptocurrency just for the sake of doing so. There are many technical reasons why we can't do this yet.
So we already have a long term plan to implement sidechains or treechains. Currently this is only concept/vaporware, so we are not waiting around until it happens.
Because VPS providers profit margins are so high vs a typical home user, they will be eventually replaced, but it allows Storj to scale pretty quickly using the traditional cloud as network nodes.
The metadata for the file is stored in a blockchain. The actually data may live on a centralized or decentralized source.