Hey Storjlings! Now that we are in the Sputnik release (public alpha for developers), and our white paper has been published, we would love for the community to start contributing to the project. We have opened a number of GitHub issues for open source developers within the community to tackle, if they would like to get involved.
Read More →S3 Compatibility is Key to Breaking into the Cloud Storage Market
John Gleeson
on
business
•
Nov 13, 2018
Suppose you want to take a unique and disruptive approach to cloud storage and launch a new product into the established market. Where do you start? Sure, you want to be half the price of the most dominant provider. You’ll also want to be just as reliable, as well as faster and much more secure. But once you’ve checked all those boxes, what’s really going to move the needle in terms of adoption? As it turns out, it’s not more differentiation. It’s compatibility. As such, compatibility was a huge priority for us as we planned the build-out of our new decentralized cloud storage network.
Read More →Security and Encryption on the V3 Network
Moby von Briesen
on
engineering
•
Nov 8, 2018
Data privacy and security are very important components of the Storj network and are primarily maintained through client-side encryption of file paths, content, and metadata. By encrypting client-side, we avoid the danger of making this data available to attackers, and anyone else who is unable to derive the necessary encryption keys.
When designing our method for encryption, we had to consider future features and how our encryption method might impact them. For example, we plan to implement bucket, file, and directory sharing, which places constraints on how files and file paths are encrypted. We need to maintain the security of encrypted components while still allowing for the possibility of decryption without direct control of the root secret used to upload files. In the new V3 network, we make this possible by hierarchically deriving keys based on the root secret and file path. This method is detailed more below. We also designed our encryption method to avoid using the same keys for content encryption of different files and different segments of the same file. This is advantageous not only because it makes file sharing of encrypted files more secure, but because it does not put other segments or files at risk if one of them is compromised.
Read More →Replication is bad for decentralized storage, part 1: Erasure codes for fun and profit
JT Olio
on
engineering
•
Nov 6, 2018
Hi! JT Olio here. We recently launched the white paper for our V3 network! The document offers 90 pages of detail about what we’ve built and are now working on for our near-term roadmap, and it’s wonderful to finally have it out!
I would have loved to go into this amount of detail during my conversation with David Vorick of Siacoin a few months ago. We were talking about how this V3 architecture is fundamentally better than other approaches, but I was unable to go into why at that time. Now, with the release of our white paper, we can finally dive into those reasons.
Read More →
Hey Storjlings! If you haven’t heard yet, we’ve released the Storj V3 white paper! We hope that the white paper will bring more clarity about what we are building and how it works. Most of our time has been dedicated to writing and publishing the white paper during the last several weeks, but here are a few additional things we were able to accomplish:
Recent development accomplishments:
We finished the initial implementation of the data repair component.
Read More →
The 1970s was an era of individualism and a decentralized internet. While not all of the circa 1970 trends may be coming back in style - I’m looking at you, tie-dye t-shirts - decentralization is very much back in vogue, and it’s definitely not going the way of the 8-track.
Read More →