Updated Details Storjcoin {SJCX} +1 PB Milestone Reached

  • Storjcoin (SJCX) Core Release v7.0.3

    • Fix issue with proof-of-work script running with electron #725
    • Add protocol to contact updates #726


  • Storjcoin (SJCX) Core Release v7.0.4



  • Storjcoin (SJCX) Core Release v8.0.0

    • Added persistent tokens for shard server for SIP6 #724
    • Fix disk over allocation that leads to farmer crashes #730
    • Bug fix for logging #728
    • Deprecated BridgeClient and related: FileMuxer, FileDemuxer, DecryptStream, EncryptStream, DataCipherKeyIv, DeterministicKeyIv, KeyRing #731


  • Storjcoin (SJCX) Release GUI v7.0.1

    • Update to storjshare-daemon 5.0.0
    • Add installer / uninstaller checkbox for creating / removing windows firewall rules - thanks @MysticRyuujin
    • Re-insert comments into configuration file - thanks @JacksonML
    • Rename wizard STORJ payout address
    • Ignore pre releases for update notification
    • Update to nodejs 6.11.3


  • Storjcoin (SJCX) Core Release v8.1.0

    • improve farmer logging, paid and unpaid downloads #734
    • remove _pendingOffers #733

    Thanks @littleskunk


  • Storjcoin (SJCX) Core Release v8.4.2

    Reverts restify upgrade as it was conflicting with express #747



  • Storj (SJCX) Town Hall Meeting Q4 - 17

    Storj Labs is happy to invite everyone in the community to participate in a world-wide accessible town hall meeting. At the town hall, attendees will hear from Storj team leaders about our product roadmap, recent accomplishments, internal staffing, community growth, and our 2018 high-level goals. We will share a presentation followed by a 20 minute session at the end to answer community questions, which can be submitted via email and chat during the town hall. The town hall meeting will be recorded and be made available for those who cannot attend.

    Community members can submit questions in advance by email to [email protected] ahead of the actual date of the town hall meeting. Please remember, this is your chance to join us to discuss important topics related to Storj and our community.  All the details for the event are listed below. 

    Storj Town Hall Details:

    Where: The town hall meeting will be live-broadcast on the Zoom.us platform.

    Please use the link above to pre-register. Make sure you have the software downloaded before the town hall meeting. If you have any questions or concerns, please send an email to [email protected].

    When: November 21, 2017

    Time: 11:00 AM EST, 3:00 PM GMT, 6:00 PM in MSK, 11:00 PM CST and 8:00 AM PST. Please check your local time.

    Email: [email protected]

    Please submit questions via email before November 20, 2017 at 11am ET. If your question is answered, we will send you some tokens and/or swag as a thank you for being awesome! Please make sure you have an ERC20 compatible wallet ready to receive any reward tokens for your helpful questions. 

    Town hall format: 45 minute presentation and a 20 minute open floor Q&A.  

    Social Media:

  • Storj (SJCX) - core Release v8.5.0

    Support Node.js 8 LTS



  • Storj Bytes Community Newsletter Q4-2017

    Our community commitment to transparency and communication is of the utmost importance to us. As such, we are excited to be issuing our second quarterly newsletter—and the last one of this year! This past quarter has been filled with news about hires on the engineering and marketing teams, technological advances with SIP09, our successful town hall event where we presented our technological roadmap and answered community questions, and so much more. This newsletter will highlight what we’ve accomplished this quarter and what we can look forward to in the next quarter.

    If you are new to Storj Bytes, please check out our last newsletter.  Storj Bytes is your resource for the latest product and technology updates and a look ahead at our roadmap. It also details community feedback and how we’re integrating it into our work.

    TECHNOLOGY IMPROVEMENTS SIP06 has improved our network

    In our last newsletter, we explained how SIP06 works and why we implemented it two months ago. Now we would like to update you on how it has significantly improved the network. Prior to SIP06, the load of Farmers on the Bridge was high: Each time the Bridge sent a contract for each shard upload, more than 1000 Farmers relayed this contract, and then the Bridge had to deal with the same number of OFFER messages. This congested the network and instantiated an overhead for the Bridge. As a result, farmers faced increased timeouts and error messages and were often unsuccessful in storing shards.

    A second significant issue prior to SIP06 implementation was an uneven shard distribution. The first node that sent an OFFER message to accept a contract would receive the shard from the Bridge. The way the network was organized, U.S.-based farmers received the majority of shards, while Farmers in Europe struggled to get any contracts. From the Clients´ perspective, upload and download speeds were slow because they Clients were not utilizing the whole Storj network—just the U.S. Farmer bandwidth.

    SIP06 solves both major problems described above by reducing the CPU load on the Bridge and Farmers.Clients are now receiving fewer error messages and can also upload more files. The shards are distributed ¨more evenly over the world, giving Clients maximum upload and download speeds. The Storj network has increased to 20PB as a result of SIP06!

    STORJ NOW The STORJ token is now accepted as a form of payment. 

    As a big part of our initiative to create more utility for the STORJ token, we’ve released a dramatically improved billing feature that accepts STORJ as a form of payment for storage space. This is only our first step to implementing many other features and requests so that the token can possibly be used in the future to buy other goods like swag. The community has been a great driver to push this feature—and we’re excited to finally put it into production. If you’re not sure where to see the STORJ token as a form of payment, log into the dashboard and navigate to the billing page. You should see it in the bottom right-hand corner.


    Below are 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.

    Storj will offer discounts to users who use the STORJ token for payments

    As a way of giving back to the community and to increase the utility and velocity of the token, we will be releasing a discount program to complement the new billing feature. This program will benefit users who pay with the STORJ token by providing them with discounted pricing. This is our first initiative of many where we will provide added benefits to our community members who pay with STORJ.

    Documentation will be project-oriented and informative so developers, Farmers, users and partners can get onboarded 

    Documentation and UI/UX is critical to our community growth and overall on-boarding experience for developers, Farmers, Storj partners, and users. During the town hall meeting, we gave a sneak peek of some ideas we’ve been working on to enhance your overall user experience. We’ve dedicated resources this quarter to design some UI/UX flows, and starting January 2018, Storj will have a dedicated team to work on documentation and UI/UX improvements. All of January 2018 will be spent on internal research for tools and UI/UX flows to assist in creating a blueprint for how the community will be onboarded. By February/March 2018 you should start to see changes. As these changes happen, we will be soliciting feedback to improve your experience.

    SIP09 accounts for the Bridge’s bandwidth usage and creates a reputation metric between a Client and Farmer on successful transfers

    SIP09 intends to solve two things: Create a reputation metric of Farmers who store shards and account for the Bridge’s bandwidth usage. SIP09 is the initial building block for creating Farmer metrics. It allows us to see if a Farmer was successful in providing a shard for download. As it stands, when the Bridge assigns a mirror shard to the nodes with the fastest response time to the Bridge’s request, the winning Farmer will receive a payout for answering to this request. Whether or not the shard has actually been transferred is irrelevant. As such, this inflates some Farmers’ payouts every month. To address this problem, SIP09 allows the Bridge to create a Storage Event—a JSON object that provides a unique token ID, each time a shard is upload or download as requested. The Client will then send an Exchange Report, consisting of a JSON object that has key information on uploads and downloads, on the SUCCESS or FAILURE of the transfer. Each Exchange Report must have a corresponding Storage Event, otherwise the transfer will not be considered. The Farmers’ report can help confirm whether the Client was able to send the transfer. A SUCCESS report positively affects Farmer reputation, and vice versa for a FAILURE report.

    The overall intention of accounting for the Bridge’s bandwidth usage is to keep Clients accountable for downloads. By doing so, Farmers can receive the appropriate payout for providing the bandwidth for these downloads. The Exchange Report has a unique token value that comes from the Storage Event. The Storage Event object will include the Client and Farmer pair and the hash of the shard. The Exchange Report is signed by the Client and Farmer. If both Exchange Reports indicate a success rate on a download, the Client will pay the Farmer. However, if the Farmer and Client-signed Exchange Reports differ or the Client claims the download was unsuccessful, we can search the Exchange Reports for validation by indexing with the unique token. Another option, in conjunction with evaluating the Exchange Reports, is to investigate the Client and Farmer behavior to determine whether the file download was successful.

    In summary, the aim of SIP09 is to generate accurate transaction events by strongly correlating the Client, Bridge, and Farmer reports. This will improve the interaction between the Client and Farmer. The Exchange Reports are also central for eventually creating incentives to reward reliable Farmers. From there, we can create Farmer reputation metrics based on successful transfers, so that shards can move towards the more reliable parts of the network. We are currently working on this protocol and hope to release it by next quarter.

    STORJ COMMUNITY Storj bounty program will be launched in January 2018

    The Storj bounty program is under development and should be launched in January. We are currently creating a developer support program where developers working on bindings to the libstorj library will get proper support from our engineers. In addition, translations, events, blogs, and much more will be added to this program in stages. Each project submitted will go through a submission and review process. This will ensure all projects will be fairly evaluated. People participating in the bounty program will have to follow our Code of Conduct that will be posted on Rocket.Chat and on the program’s website. Failure to comply will result is dismissal of any future participation in the program.

    Storj community website section in development

    With over 12k members in Rocket.Chat and 145k community members total, it’s about time there’s a portion of the website dedicated to you! Starting January 2018,  Storj will be committed to working on a community section of the website. This will be your go-to-area to see community updates, newsletters, community-featured blogs, and other community programs. It’s our goal to make this portion of the website inclusive. We will update content weekly, and offer opportunities to contribute by being a guest writer for blogs and tutorials, and/or by participating in other projects.

    Thanks for a great year!

    We are pleased to be capping off a very successful 2017. With our Token Sale, the public launch of the Storj platform, user growth on both the Farmer and Client sides of the network, and expansion of the internal Storj team, we are so proud of the progress we have made this year. We thank you, our community, for the continued support you’ve given us throughout 2017 and are looking forward to more advances for 2018!

    While 2017 was wildly successful for Storj, we feel even more confident about the milestones we will achieve in 2018. We expect continued product improvements, increased use of the network, new partnerships and much, much more.

    This past year saw the benefits of decentralized applications take hold in the developer-community. Developers, companies and individual consumers began to see the need for decentralization in a world where we depend so much on data and highly value privacy. We believe in 2018 the demand for decentralization will grow even more, and Storj, in building the foundation to a decentralized world, will be poised to capture the vast majority of the market! 

  • Storjcoin {SJCX} - Getting From Petabytes to Exabytes: The Road Ahead

    Since we launched the Storj network, our growth has been phenomenal. In the last six months alone, we’ve scaled the amount of data stored by about 50 percent each month. Today, we are storing over 30PBs on the network! We anticipate that the recent partnerships we’ve entered into will fuel this growth even further, pushing the use of the network from petabytes to exabytes.


    Before our network can support that many users and that much data, we need to make some updates to the architecture, and those adjustments will take time to implement. To accomplish our growth plan, Storj will gate access for new users to guarantee zero impact to existing users. New users will still be able to register, and will be placed on the waiting list. We expect to open up service to a limited number of users over the next several months.

    We’re committed to supporting our current users and farmers. Users who are building on top of Storj can continue development of their applications uninterrupted, as the library endpoints will remain the same. When we roll out the architecture updates, we will do everything we can to minimize impact.

    For farmers, this change in architecture will establish a foundation for massive growth, as well as additional opportunities to monetize unused storage. When our new architecture goes live, farmers with the best reputations (those who maintain their connections and data integrity) will be poised to reap great rewards.

    Scalability is the biggest challenge that developers focused on decentralized projects have faced over the last decade. We know – we have been working on this for the past four years. The data we’ve obtained, and the insights gleaned as we have grown, have helped us identify this way forward. The network resulting from this shift in Storj’s architecture will lead to increased payouts for farmers, improved performance for users and a completely decentralized cloud storage platform that developers can use to power the decentralized applications of the future.  

    When our architectural updates go live, we are confident the network will be capable of scaling into the exabytes of data stored and able to better support the partners who are currently building on top of our platform.

    The new architecture will focus on these main innovations: rebuilding how nodes that store data communicate with one another; modifying how companies, applications and developers upload and interact with the network; and spreading metadata across individual nodes on the network.

    Through these changes, data will be better replicated across a global geography to ensure that if users have access to the internet, they will be able to access their data – even during a major outage or natural disaster. The architecture will also enhance data audits to better guarantee data integrity.

    The new architecture will deliver enhanced scalability, security and resilience.

    Scalability – we will be able to scale into the exabyte range and satisfy the storage needs of our largest users and partners.
    – the new architecture will improve decentralization, reducing the
    likelihood of cyber security threats like DDOS attacks or hacking.  
    – nodes will better communicate with each other if they go offline,
    ensuring users maintain access to their data even in the event that a
    portion of a file becomes corrupt or is lost.

    We are committed to building and sustaining a platform that can last generations. It’s our commitment to our existing and future customers to do this right.

    Our core values include transparency and trust. The Storj team will share milestones and progress via our town halls and newsletters/blog posts. If you have any questions, reach out to our Rocket.Chat channel. We plan to issue an updated Storj whitepaper in the months to come.

    – The Storj Team

  • Storj Release Wallet v8.7.0

    • Change some error message to hide information about existing contracts #759
    • Use secp256k1 to sign messages #761 #764

    Thanks @littleskunk



  • Storj Core Release Wallet v8.7.2

    • sign and verify contracts with secp256k1 #766
    • bugfix and additional unit tests #767



  •  An Update on FileZilla and Storj


    The FileZilla Project has been busy. In the last few months, the open source FTP application has added new integrations, including one with Microsoft for Azure integration with FileZilla Pro. We talked to Roberto Galoppini, Director of Strategy for FileZilla, about what makes the Storj relationship special.

    How is Storj different from your other cloud partners?

    Through this integration we can utilize Storj as a traditional FTP server. Storj is the only service we integrate with that enables us to provide our end users with a cloud FTP service that is truly private. The team is still making improvements to improve performance and reliability, but people using Storj don’t have to be scared they are sharing their information with the NSA or anyone else. That’s why this relationship is special to us. It’s a unique service that FileZilla users can’t get from anyone else. Thanks to the integration the teams have been working with, for the end-user, connecting to Storj feels no different than using FTP. They can also make some money through Storj if they become farmers on the Storj network. 

    How is FileZilla Pro different from FileZilla, and what kind of integration will we see between FileZilla and Storj?

    We have two products. One is FileZilla. It’s a free—as in beer, and as in speech—open source FTP client that has a huge user base. We have one hundred million downloads per year, and that’s only about FTP. Why are we able to talk to Storj through FileZilla? We’ve created a tool that uses the libstorj library to connect to the Storj service to transfer files. The FileZilla program can talk to this tool and translates its replies into FileZilla’s internal data structures that are used for all supported protocols.

    FileZilla Pro is sold to people who want to use FTP as a protocol and integrate with non-FTP protocols, like Amazon S3, Azure, and very soon Google Cloud, and not too far from today, OpenStack as well. We are on a roadmap where nearly every month we add a new protocol, for people who don’t need just an FTP client—they want a “Swiss army knife” to access different cloud providers’ services, and the more protocols supported, the better. So today, if someone is using Amazon S3 through FileZilla, it doesn’t feel different from using an FTP server. We keep the consistency in the user interface and procedures, so that transferring files with any of the supported protocols will offer the same look and feel.

    How seamless will the experience be for Storj users? Will they have to set up an account separately?

    Right now, it’s seamless if they are already part of the Storj user base. For people not yet part of the Storj network, in phase two of our integration there will be tighter integration between FileZilla and Storj, so people who choose to use Storj will be provided with a very easy way to create an account. Today, they need to go to the Storj site, create an account, and come back. The idea is to make this much easier so that even new users can try Storj.

    For FileZilla as an open source platform, how do you view the Storj relationship as a way to financial sustainability?

    The relationship is aimed at benefiting all stakeholders: our users will get access to an innovative and secure cloud service, plus a way to monetize their free disk space and bandwidth; Storj will tap into a large user base, and we’ll get rewarded for promoting it among our users. Everyone wins!

    What’s your take on the decision to re-architect the Storj network?

    Both Storj and FileZilla want to make sure the partnership can be enabling. FileZilla and Storj have an agreed baseline against which we want to measure the performance. I believe that it won’t take too long, hopefully before the summer to reach that. When your team will be happy with results, we will be happy too. At this point we are going to market strongly the partnership.

    Anything else you would like to add?

    Yes, about the new CEO of the company. For the record, I have been trying to help Storj to find a CEO, and have shared some names occasionally. Being part of this open source business world for a while, I am very happy to see that Ben [Golub] took the role. Given his background in storage and open source and startups, I am sure it will be a great addition to the company. I can’t wait to start seeing the results of this new position filled finally.

    By Jodi Smith

  • Planned Network Testing Ahead of V3 Launch

    As we approach the release of the new Storj V3 platform, we will be performing some tests on the current network related to farmer reputation.

    The purpose of these tests is to verify and validate enhanced network metrics and the reputations of long-term, highly available and reliable farmers. The data gathered throughout the process will be used as part of the evaluation criteria for granting early V3 network access to our current farmer base. During the course of this test, we will only upload first-shard data to locations with a maximum of 5 nodes per IP address. In case you are running more nodes, we advise you to shut down the excess ones to achieve higher per-node-usage and efficiency. We will also be conducting audits and periodic downloads in conjunction with our storage upload testing.  

    As we begin the transition from the current network to our new V3 network, we aim to prioritize farmers with a proven track record of availability, reliability and consistently high reputation.

    We’ll be sending out more communications on the V3 network as we approach public alpha in the coming months.  

    In the meantime, here are a few things to get you up to speed about what we’re building:

    Thank you for your continued support of the network!

    - John Gleeson, VP of Operations

  • Security and Encryption on the V3 Network

    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.

    The encryption algorithm we used for content and metadata is easily configurable between AES-GCM and “Secretboxour whitepaper.

Log in to reply

Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.