Storj Blog

The recent release of our white paper was a huge milestone in communicating with the community, our customers, and our partners about the direction and status of development on the new network. The white paper defines our long-term vision for Storj and lays out the foundation for the concrete implementation of the network. While the white paper includes extensive information about the network we are building, it doesn’t give any indication about when development milestones will be achieved - which brings us to the announcement of our public roadmap.

Our public roadmap includes a series of alpha releases leading up to a beta release and ultimately, the production launch of our V3 network. The composition and sequence of the releases is designed to accelerate the launch of the production network with SLAs. This blog post provides some additional information about each of the most recent and upcoming releases.  Quick disclaimer - this document contains forward-looking statements about our product direction. The development, release, and timing of any features or functionality described for our products remains at the sole discretion of Storj Labs. The information herein is not a commitment to deliver any material, code or functionality, and should not be relied upon in making purchase decisions.

Read More →

Instead of spending the week shopping for online holiday deals, we have been busy making huge amounts of progress on the V3 network. Our next major milestone is the Explorer release, which will allow storage nodes to start joining the V3 alpha network. Most of our efforts have been focused around building out features related to this. Recent development accomplishments: We added the ability for storage nodes to advertise a wallet and email address over Kademlia.
Read More →

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 →

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 →