Storj

BackgroundThe Basic Identity Token (BIT) team participated in the recent ETHWaterloo hackathon, winning second place with their entry in our Storj Challenge competition, which was part of this hackathon. This blog will share some background on the ... [More] BIT team and the app they built on top of Storj.BIT’s inspiration is to increase accessibility to blockchain-based DApps This year’s ETHWaterloo Hackathon ran from October 13-15. Here, four young hackers from the Waterloo region met up to form the BIT team, aiming to build an awesome app for the Storj Hackathon challenge. The team brought together people from diverse backgrounds - two University of Waterloo students: Jonathan Tsang (a computer science major with experience in game and web development) and Kaustav Haldar (a psychology major with a keen interest in ethereum solidity and blockchain applications), and two software engineers: Eddy Guo (interested in Node.js and Javascript programming) and Steve Veerman (CTO of Flexfinity, with experience in marketing and IT consulting). After some general discussions to refine their approach, the BIT team conceptualized the integration of identity into blockchain applications, namely decentralized apps (DApps).BIT allows users to easily access DAppsBIT makes DApps more consumer-friendly by providing access to the apps through their Facebook login. This simplification is the key to making blockchain-based platforms like Storj and Toshi accessible to the average person, who is likely unfamiliar with the complexities of blockchain technology. The BIT DApp login process automatically associates a user-provided wallet address with an identity token, which BIT generates by verifying the user´s identity through personal information from their Facebook profile.One advantage of using BIT is that it contributes to reducing distributed-denial-of-service (DDoS) attacks and spam by using Ethereum’s core blockchain technology. This can best be explained by comparing this process to how we currently surf the internet. Users can access any website on the internet by entering the URL in a browser to render the web page. Malicious users may want to hinder traffic on sites by performing a DDoS attack, resulting in an overload of the web server which may lead to a crash of the site. Traditional websites are vulnerable to such attacks because they lack identity authentication to validate who is a legitimate user versus a spammer or user with malicious intent. BIT, on the other hand, allows decentralized websites and apps to integrate identity validation, eliminating the threat of DDoS attacks.BIT technological stack includes StorjBIT is built primarily using JavaScript and Node.js, and leverages smart contracts written in Solidity. The BIT team also implemented a variety of libraries, such as Storj’s node bindings  library and Toshi’s “headless bot client”. BIT helps user retention with DAppsBlockchain and virtual token-based ecosystems are growing at an astonishing rate. However, the current barrier to entry is too high for a non-technical mainstream user, as this innovative technology based on complex cryptographic concepts is not easily assimilated.  Regardless, many people rush into the space with little technical knowledge and can easily get discouraged from further participating.  BIT removes this obstacle by providing people access to DApps via authentication, resulting in high user retention when using BIT-enabled DApps.BIT authenticates user identity informationBIT prides itself to be very user-friendly. On almost any internet connected device, one can already connect to Facebook. BIT prompts the user to input an ERC20 compatible wallet address and then requests access to their personal information from their Facebook account. If approved, the user can access DApps like Storj, and gain access to perform actions within the app, such as uploading a file. With BIT, people can take full advantage of blockchain technology using only a Facebook account. As shown by the BIT experimental features developed during the ETHWaterloo Storj Challenge, people can gain access to Storj to store files on the decentralized network, or to use DApps like Toshi. The following is an end-user example of how someone would use the BIT app:Step 1:  Use Facebook to log into BIT Step 2:  Authenticate your profile. After this, BIT retrieves your email address and other personal informations to create your unique ID token.Step 3: Input your address from MyEtherWallet or another ERC20 compatible wallet.After completing these three simple steps, you can access Storj or Toshi. Here is a code snippet of how BIT accesses Storj to upload a file: const storj = new libstorj.Environment({        bridgeUrl: ‘https://api.storj.io’,        bridgeUser: ‘‘,        bridgePass: ‘’,        encryptionKey: ‘anana abandon abandon abandon abandon abandon abandon abandon’,        logLevel: 0    }); BIT improvements include UI and intuitiveness:There are two major areas BIT should address in the future: First, the user interface front-end should be overhauled to ensure it is fully functional and user-friendly. React has already been implemented in some parts of the GUI, but more improvements should be made to further improve intuitiveness. Features for the identity verification modules of the app also need further refinement. Currently, the name and email address is received from the identity token, but much more could be done to create an identity with useful applications. One such feature would be to make uploading and accessing files with Storj easier for the user. The integration would allow users to create a folder to upload and download files using their BIT accounts. This would help position BIT as a central hub of browsing where users can easily find all their files. Also, optimizing the Toshi integration for user login would add another convenient way to validate identity for BIT. The Storj and Toshi integrations are starting points to develop BIT into a comprehensive focal point for browsing DApps in web3.0.Dapp Standard login toolThe BIT authentication feature is a great addition to any size DApp because it lets us scale up to more users through better accessibility, provided by allowing people to login to any DApps with their facebook identity. This lowers the barrier to entry into blockchain technology, driving adoption of the cryptocurrency ecosystem.BIT wants to enable more social media networksWhen creating the BIT project, a lot of people asked us why we chose to use Facebook, considering that it is widely seen as insecure and almost the exact opposite of a blockchain ledger. In our project, we implemented Facebook authentication as a proof of concept, making it possible to log in to all the features of a blockchain app with only a Facebook identity. In the future, we would like to implement all the most popular social media accounts for BIT authentication, including Twitter, Snapchat, WhatsApp, and more. All these apps have large user bases that most likely already include people interested in blockchain. Ending RemarksThe crypto space is a new, emerging frontier. ETHWaterloo was just the beginning - we are the early adopters of this new tech and there is much more to come. To assemble 300 talented crypto-programmers, and organize them into teams to work on Ethereum related hacks, is sensational. We have never seen anything like it before.Our BIT app was a challenging project, but in the end we pulled it off together, as a team. ETHWaterloo was one of the harder hackathons we’ve participated in because of its focus on Ethereum programming.  Despite this obstacle, all of us had an amazing experience, and we hope to attend the again in the near future. All code for our project can be found here:https://github.com/kaustavha/ethwaterloo-bitFrom left to right: BIT team courtesy of @benarnon on instagramJonathan Tsang, Steve Veerman, Kaustav Haldar, Eddy Guo [Less]

Good news for the Storj community! STORJ tokens are being listed on Poloniex for trading. You can begin depositing STORJ tokens to the Poloniex exchange this evening, October 26, around 11:00 pm EDT (3:00 UTC).If you still hold any old, deprecated ... [More] SJCX Counterparty tokens on Poloniex, you will need to immediately convert them to the new STORJ ERC20 tokens on a 1:1 basis using the Storj conversion app before trading them on the Poloniex exchange. After conversion, users can then re-deposit the newly converted STORJ tokens back to their new Poloniex STORJ deposit address or send them to another ERC20-compatible wallet.Users should migrate any old SJCX tokens still held on Poloniex to the new STORJ token ahead of Poloniex’s SJCX delisting, which will happen in the next few weeks. To convert tokens from SJCX to STORJ, take the following steps. You can also use our Storj token conversion guide for reference, which includes more detailed instructions with screenshots: 1. Navigate to https://storj.io/conversion. 2. Enter the required information: your email address and, if you plan to send your new STORJ tokens to a wallet for holding them long-term, an ERC20-compatible wallet address such as MEW, parity or mist (please choose the latest stable release) or, if you are planning to immediately trade your new STORJ tokens again on the Poloniex exchange, you will need to enter your new Poloniex STORJ deposit address. Do NOT use the Poloniex ETH deposit address! You can find the new STORJ deposit address on your Poloniex account page by clicking on “Balances” and selecting “Deposits & Withdrawals” from the drop-down menu, searching for “STORJ” and then clicking on “Deposit” to the right to display the STORJ deposit address which you must enter under “Ethereum Address in the converter app. Note that you need to be careful to search for the “STORJ” and not the “SJCX” deposit address, both of these tokens will still be available on Poloniex so be careful not to enter the wrong address here on the converter app! With the above info, the converter app will generate a SJCX deposit address which will be needed for the next step. 3. Next, go back to search for “SJCX” on the same “Deposits & Withdrawals” page you were on before in your Poloniex account to find your SJCX withdrawal address. Click on “Withdraw” to the right to display the correct withdrawal address.  Fill in the resulting SJCX withdraw form to send your entire SJCX token balance to the SJCX deposit address generated by the converter app in step 2 above.  Note that Poloniex will deduct 3 SJCX from your SJCX balance as they will need to cover the BTC miners fee necessary to send the SJCX transaction. 4. Wait for your SJCX withdrawal to confirm on the blockchain. You should monitor your Poloniex account to ensure that the withdrawal goes from “Pending” to “Complete” state by checking your withdrawal history page.  If you notice after a few hours that the withdrawal is still showing as “Pending” or displays some error, you must file a support ticket with Poloniex Freshdesk and ask them to please resend your SJCX withdrawal. Only once your SJCX withdrawal transaction was fully confirmed will the converter app proceed to initiate the sending transaction of your new STORJ tokens to your personal ERC20 compatible wallet or new Poloniex STORJ token deposit address (depending on which you specified in step 2). This process (assuming there was no delay in the withdrawal from Poloniex) may take up to 72 hours and you will be notified by email when it is completed. If you run into trouble or are unsure how to proceed, please email the Storj team at [email protected]  or contact us on our Rocket Chat for interactive support. [Less]

Today we are happy to announce that we have reached a major milestone for Storj! We now have over 5 PB (5,000 TB) of data stored on our network and that number is climbing fast towards 6PB! We want to thank all our uploaders and stress-testers who ... [More] have helped us achieve this milestone.  We have shown that in addition to being the largest decentralized storage cloud in the world, Storj can also scale to accommodate demand.The map below illustrates the current distribution of Storj farmer nodes around the world:Our team of engineers are hard at work to enable the network to scale a hundred-fold within the next year. The graph below illustrates how the total storage space occupied on the network has increased this year alone.The same exponential growth is also true for our community of farmer nodes, which is approaching the 50,000 mark.We again want to thank all our community members for their continued support. We couldn’t do it without you! To learn more about Storj, get interactive help and stay up to date with releases and events please join our Community Chat! [Less]

Data centralization behind corporate firewalls has long been the canonical pattern of how enterprises manage and store information. Unfortunately, this type of system architecture has some well documented security shortcomings. With recent ... [More] technological advances, hackers are better equipped to breach company private firewalls. However, companies struggle to keep pace and adapt their data infrastructure to an architecture that makes it arduous for hackers to obtain data.  Blockchain technology and data decentralization are advances we at CapLinked believe to be ground-breaking technologies that will protect confidential, proprietary files. Storj is a pioneer in this arena that is changing the landscape of data management. Storj’s decentralized, end-to-end encryption cloud storage is secure, reliable, and efficient. CapLinked is excited to partner with Storj Labs to provide an unprecedented level of data security by combining CapLinked’s access management and security capabilities with Storj’s decentralized and encrypted storage.  CapLinked provides secure enterprise sharing of confidential and proprietary information. Our SaaS platform and API allow users to protect, track, and recall access to files. We let users securely apply custom and dynamic watermarks to documents, implement digital rights management, and share these assets across an organization. Our platform is frequently used in mergers, licensing deals, financings, audits, and other projects that involve sharing data and other content between companies. As an enterprise with an active customer base, we want to ensure that any platform we partner with will not go stale. Storj’s vast Github repository of open source code and constant engagement on Github shows us this is an active project that continues to gain momentum. Furthermore, their active community of over 10,000 members and growing shows us that their health as a company is strong. Along with recent new hires, we know Storj will continue to evolve the product. These metrics tell us that anyone can confidently build applications on top of the Storj data layer and get proper support.As a demonstration of how easy it is to integrate with Storj, I built an application that applies custom watermarks using the CapLinked API to documents stored in Storj buckets. I wrote a Storj document watermarker as a NodeJs module using the storj.js library. Storj’s installation and usage guides were easy to navigate and follow, and well versed for a multitude of different platforms and API SDK flavors. Here are the steps I took to get this project up and running:Step 1 - Obtain API credentials from Storj and CaplinkedStep 2 - Install the Storj library on my development machineStep 3 - Use Storj’s CLI (command line interface) to create buckets and upload filesStep 4 - Make API calls to pull files from StorjStep 5 - Invoke CapLinked’s API to apply watermarks to filesUsers of this custom watermarker can simply supply both Storj Bridge and CapLinked API credentials to start watermarking documents stored in Storj. (CapLinked API credentials are available upon request at the CapLinked developer portal.) Please try out the watermarker and let us know what you think. I hope to hear from you- [email protected] LeeCTO of [email protected] Arons Lee, Chief Technology Officer at CapLinked:Arons is an entrepreneurial minded full-stack developer and engineering architect who loves to build cutting-edge applications. He has an educational background in Computer Science / Electrical Engineering and has previously worked for Yahoo in addition to various startups in the Los Angeles area. Arons has personally overseen the development and expansion of the CapLinked API and SDKs. Arons enjoys to frequent tech workshops and conferences, contribute to the developer community, and sharpen his single-digit golf handicap. [Less]

Welcome to Storj Bytes, a quarterly newsletter from the Storj Labs team. 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 ... [More] our work. Storj Labs is thriving with product and technology adoption because of you, the community. Every single community member is crucial and plays a role in advancing distributed storage in our industry and how Storj grows. Without our ecosystem of Farmers, Renters, Moderators, Contributors, and Developers, many of whom have been with us since the very beginning, Storj wouldn’t be what it is today. We’re now, as a community, in a position to drive the future of blockchain-based storage for all. We’ve finalized our token sale and are poised to accelerate company growth and development of the platform. We’ve aggregated community feedback and are focusing in the near term on improved onboarding and consistent payment plans. Development and services are our priority in Q4, and we hope this newsletter addresses these topics and provides visibility into what we are currently building and what new capabilities are on the horizon.TECHNOLOGY IMPROVEMENTSOur C-library has increased the efficiency and reliability of file transfer and encryption Community members have requested an easier way to integrate with our Node.js core. As a result, the engineering team has largely been focused on migrating the Node.js core and CLI to a C-library called libstorj, with Node bindings called node-libstorj. We wrote libstorj as a replacement for the older JavaScript library with the purpose of interacting with the Storj network. We chose to build the core in C because of its portability, performance and efficiency. The bindings provide a portable way for other languages to interact with the network. Prior to the bindings, developers had trouble implementing a library that can reliably download files. Since developers invested significant time in this implementation, it detracted from the overall main goal of what they were trying to achieve: incorporate the Storj network in their application. Furthermore, by migrating to C, and re-architecting the code base, overall performance has greatly increased. This has directly resulted in an increased efficiency of the network transfer connection initiation time, the general response time for commands, how files are encrypted, and how larger files are transferred.Earlier this year, we improved the network reliability for file downloads, including shard mirroring and reconstructing a file from its partsA distributed storage network utilizes its Farmer community and storage availability. When Farmers go offline, storage space decreases, resulting in an unacceptably low probability of file retrieval. We’ve made great strides to improve retrieval reliability by creating multiple copies of files and implementing an algorithm, “Reed-Solomon”, that is able to reconstruct a file from just a fraction of its data shards.Specifically, one of the issues with Clients receiving a file is that Farmers have had less than a 50 percent probability of being available to serve this data. The node´s (Farmer’s) ability to retrieve data was dependent on the size of the file being received: a larger file size coincided with a decreased probability of data retrieval. Data retrieval issues are directly related to a node’s performance and behavior. Nodes could go offline due to power failures, crashes, intermittent internet connections, and so on. The solution to these unfortunate circumstances was mirroring the node that’s in a failed state, and adding erasure encoding. When a node is inactive, other nodes in its vicinity will voluntarily hold pieces of data that were originally stored on the node that failed. Erasure encoding comes into play in the event that too many nodes that hold data or parity shards have gone offline. The file’s metadata is stored on the Bridge. The metadata contains the order and distribution of the shards stored at various node locations. To be able to reproduce the lost data, the metadata is requested from a Bridge. The missing shards can then be recreated from the remaining shards and parity shards.  Up to two-thirds of the data can be lost and the file can still be reconstructed 100 percent.  Parity shards are used to recalculate missing file shards and are stored on Farmer nodes along with file shards. This solution greatly increased the reliability of file downloads.Bridges and Farmers will show an improvement in the scalability and reliability of file uploads Like file downloads, file uploads rely on a pool of Farmers willing to accept a contract and hold the data for a specified time dictated by the contract. Originally, we implemented the Quasar/Kademlia structure to create a publish-subscribe model due to the promise of decentralized scalability. In this implementation, some Farmers are put at a disadvantage because other Farmers stay online but fail to propagate messages to their neighbors. These issues, along with timeouts, created an opportunity to mature from this model and create a replacement detailed in SIP6. Quasar describes an event routing infrastructure for performing a publish-subscribe system on a structured peer-to-peer overlay network. However, the Quasar model is completely separate from the contract itself. Kademlia describes how a node is mapped in the network and where its neighbors are in relation to it. In this implementation, a Bridge advertises data that needs to be stored. Farmers (nodes) listen to the data and choose to subscribe to the advertisement. A Bridge sends a ‘publish’ message containing a contract to the network of subscribing nodes. The nodes review the contract and choose to accept or decline it. If a node accepts the contract, it sends an ‘offer’ message to the Bridge. If the Bridge accepts the ‘offer’ message, it sends a ‘consignment’ message to the node. The Bridge then receives a token from that node to upload data to it. While this implementation works, with time, we found it to be unreliable. Community issues were also raised that confirmed the possibility of oversights in the design. In the described setup, a Bridge would wait for a certain amount of time to get a response from different nodes to see if any are interested in a contract. Nodes organized via the Kademlia setup relay this information to other nodes in their vicinity. However, not all nodes ideally performed this task. Timeouts increased due to some nodes having bad connections, refusing to relay the data to other nodes they are connected to, and so on. If a node is the last link in the sequence, it most likely will be delayed in sending an ‘offer’ message to the Bridge.  This puts some nodes on the network at an unfair disadvantage and creates a setback for the network. We invested considerable engineering efforts to resolve this issue by creating SIP6. The SIP6 implementation provides a different strategy of how a Bridge communicates to a Farmer. It facilitates direct communication between a Bridge and a Farmer where the Bridge will directly contact a Farmer based on qualitative data. Unlike the first solution described, Bridges are aware of Farmers in its network and their space availability information for holding data.  When a Bridge asks a group of nodes to store data, a node has an option to accept or decline it. This communication is immediate and does not rely on relaying messages between nodes.We are currently working on deploying these changes.  For more background information, please check out Problems with Quasar based publish-subscribe systems in peer-to-peer storage networks authored by one of our engineers.A status page informs the community of any incidentsWe feel it’s crucial that the Storj community is aware of incidents when they happen. They should also know why they have happened, and how they were resolved. We’ve created a status page to enhance the community experience and provide updates around incidents that occur. The status page is our commitment to reinforce confidence in the product and provide an even greater level of transparency to the community.STORJ NOWThe Bridge’s GUI is now more informative The Bridge’s GUI is a key tool that enables users to simplify user account information on the Storj network by providing detailed information and a refined experience. The team is currently working on improving the experience and capabilities within the GUI, and updates will be rolled out in the coming months. The updates will be centered on insights and payment. The improved GUI will add more useful features for Renters to work with their Storj account and files, like the ability to monitor data usage. There will now also be more insights into file storage usage statistics, which will replace the bucket tab on the current GUI. The updated GUI will also deliver an improved experience around billing and payments with monthly invoices, clearer data about how your bill was calculated, and add more types of payment methods. Renters should see an improvement in how they can pay for storage on the network including STORJ tokens, Bitcoin, Ethereum and credit card payment options.Front-end user experience will be enhanced For the initial deployments around the Storj platform, we focused engineering efforts on what made the network better - the security, encryption, performance, and scalability. Largely, we’ve been concentrating on the backend. This leaves work to be done on how users and developers experience the overall product. We recognize that if Storj is going to continue to be successful, we need to have the best, most intuitive experience in the industry. We will be dedicating efforts to making that possible. Some initial changes to look forward to will be focused on how Farmers and developers use and interact with Storj.STORJ FORWARDDocumentation will be more substantial to help onboard users to the networkProduct improvements you can expect to be implemented by December 2017 include crisper documentation. The goal of documentation is to have Farmers, developers, and everyone else onboard to the Storj network at a faster and easier pace. We will provide substantial resources such as detailed getting-started guides, screencasts, projects, and code snippets to enable the community to build and use the Storj platform. You should start to see improvements of how documentation is constructed and organized by the end of this year. Through 2018, you should see even bigger improvements. User-friendly software and documentation are one of our main priorities and will be an ongoing project late this year and into next year. Part of our initiative with documentation is to also update the Storj GitHub repositories. We will be removing unnecessary files and repositories. Furthermore, we will adopt a consistent naming convention. These changes should help developers intuitively search through the Storj repos.Ethereum integrationFinally, we will internally begin integrating with the Ethereum network for Farmer payments and other use cases. Some of the issues raised within the community, such as the monthly Farmer payouts, can be improved through this integration. This will enable Storj to potentially pay farmers in real time for the data contracts they are fulfilling.  Ethereum smart contracts will also enable new Bridge operators to have a requirement to lock up STORJ tokens so they are there to be distributed to farmers at payout time. STORJ COMMUNITYCommunity will have frequent company updatesMoving forward, watch for regular updates from the Storj Labs team. Storj Bytes will be a quarterly release that details updates on company direction and product improvements. Following the release of the newsletter, will be a townhall meeting with live Q&A sessions in an open forum.You can also expect frequent new posts on our Storj blog. Here, we will continue to share detailed accounts about our engineering team developments, insights on the industry, and so much more. Finally, we hold weekly developer meetings for discussion of ongoing projects on wednesdays at 11am EDT in the #dev channel of our rocketchat. Our goal is to be as transparent as possible as we continue to work together to strengthen and drive network adoption. Community members will have perks Storj deeply values its community members.  To show our appreciation to you, we will be developing a bounty program for those of you who are active and/or contribute to the community. You should see the bounty program roll out within the coming month. Also, we will be planning out contests, hackathons, and the likes where community members can participate and win prizes. Stay tuned - you should see announcements regarding this very soon.Building the Storj community through Partnerships An important part of growing our community is leveraging partnerships to expand the Storj ecosystem. Through integrations with our partners, we can accelerate adoption of the platform. One of these partners is FileZilla. FileZilla is helping us by providing a GUI experience with data management and file transfer on the Storj network. Watch for further updates regarding this partner and future partnerships. Our partner ecosystem continues to grow stronger every day and as it does, it strengthens the Storj community and network. If you have questions about partnerships, please reach out to [email protected] .Growing the Storj team With our token sale completed, the Storj Labs team has the resources to accelerate product and technology development as we enter the next iteration of our product evolution. We are searching for smart individuals who are passionate about decentralization, blockchain and free and open-source software. Open positions include roles on our products, design, marketing and operations teams. To see the positions available, please visit the Storj Labs Careers page. We’ve already hired several talented team members.  James is our developer; Nadine is our developer evangelist; Garrett is our junior data analyst; Dan is our head of PR; and John is our head of customer success. These team members will support the development of the Storj platform as well as our community and partner ecosystems. Check out our team page to see the new members.Lastly, we want to share that Tome Boshevski has resigned from the company. On behalf of the entire team at Storj Labs, we thank Tome for his contributions as Chief Design Officer. His state-of-the-art design has helped us stand out within the community and we wish him the best in his future endeavors. Our team is excited for the opportunities on the horizon! We couldn’t be more grateful to the community leaders and members who make up so much of what Storj Labs is. As we move forward, we want to assure you that we are prioritizing product features and improvements based on your feedback. As this community continues to grow, we are excited to work together on our next phase of development of blockchain-based decentralized storage. [Less]

Where are all the tokens?There were 500 million STORJ tokens created to replace the 500 million SJCX that were already in existence. This chart represents where they have all been allotted.What is the current status of our tokens?The following is the ... [More] breakdown of the token status in each bucket: Token Sale (Main) - 28.74MM Token Sale (Pre-Sale Total) - 43.34MM Token Sale (Pre-Sale Claimed) - 32.97MM Token Sale (Pre-Sale Frozen) - 10.37MM Converted (as of Sept 13, 2017) - 29.35MM (20.65MM SJCX still unconverted) As SJCX tokens are converted to STORJ, they come out of the Storj Labs Unlocked Tokens which means that the circulation numbers will not change Allocated to Service Providers - 2.99MM This includes Farmer payments, vendor payments etc… Storj Labs Unlocked - 54.92MM Storj Labs Reserved for SJCX to STORJ Converter - 20.66MM I purchased STORJ Tokens in the pre-sale. When will the freeze be released?Not including our 245MM locked tokens mentioned prior, there were a total of 43.34MM tokens in time locks. Here is the breakdown… 1 Month Time Lock - 28.56MM (Freeze ended July 20th, 2017 GMT) 3 Month Time Lock - 3.94MM (Freeze ends September 20th, 2017 GMT) 6 Month Time Lock - 10.37MM (Freeze ends December 20th, 2017 GMT) The 1 month time lock tokens freeze has already ended and they have all been distributed.Were all STORJ tokens delivered and in the correct amount and rate?Yes. However, we are aware of certain cases where users did not receive their tokens or the correct number of tokens. These situations have been corrected as they were reported. We are still in the process of doing a deep audit of every transaction related to the token sale and in the event that there are errors are found, they will be proactively corrected.Storj stated that an equivalent number of tokens to the number of tokens sold in the token sale would be burned. Has this happened?Yes. There were nearly 75MM tokens sold in the token sale. We have already burned 75MM tokens to match this number as promised prior to the sale.You can see that here…https://etherscan.io/tx/0xfac1371bf41c1bde0317a3120d2f73736cab2e057298cf3feec4a3bbc81c5263What is being done with all of the old SJCX now that it has been replaced with STORJ?The SJCX that has been sent to the converter will all be burned once the converter is shut down.We will also burn all of the remaining SJCX that is held by Storj Labs.When will the converter be shut down?The SJCX to STORJ Token converter will stay active until 11:00 AM EDT on October 25th, 2017.Originally we announced that the converter would be shutdown on October 19th. We have extended the time that it will stay active to account for the down time from the Bitcoin fork precautions.Can SJCX tokens still be converted after the Token Converter is shut down?No. If you do not convert your tokens while the token converter is still active, there will be no options to convert them afterwards. Please make sure to convert your tokens before the converter is taken offline.How is Storj Labs planning on using the funds raised from the Token Sale?Storj Labs will utilize the funds raised in the token sale as stated in the Token Sale Terms document under section B item 8 (Use of Proceeds from Token Sale), which you can find at the link below. https://storj.io/sale-terms.pdf [Less]

Where are all the tokens?There were 500 million STORJ tokens created to replace the 500 million SJCX that were already in existence. This chart represents where they have all been allotted.What is the current status of our tokens?The following is the ... [More] breakdown of the token status in each bucket: Token Sale (Main) - 28.74MM Token Sale (Pre-Sale Total) - 43.34MM Token Sale (Pre-Sale Claimed) - 32.97MM Token Sale (Pre-Sale Frozen) - 10.37MM Converted (as of Sept 13, 2017) - 29.35MM (20.65MM SJCX still unconverted) As SJCX tokens are converted to STORJ, they come out of the Storj Labs Unlocked Tokens which means that the circulation numbers will not change Allocated to Service Providers - 2.99MM This includes Farmer payments, vendor payments etc… Storj Labs Unlocked - 54.92MM Storj Labs Reserved for SJCX to STORJ Converter - 20.66MM I purchased STORJ Tokens in the pre-sale. When will the freeze be released?Not including our 245MM locked tokens mentioned prior, there were a total of 43.34MM tokens in time locks. Here is the breakdown… 1 Month Time Lock - 28.56MM (Freeze ended July 20th, 2017 GMT) 3 Month Time Lock - 3.94MM (Freeze ends September 20th, 2017 GMT) 6 Month Time Lock - 10.37MM (Freeze ends December 20th, 2017 GMT) The 1 month time lock tokens freeze has already ended and they have all been distributed.Were all STORJ tokens delivered and in the correct amount and rate?Yes. However, we are aware of certain cases where users did not receive their tokens or the correct number of tokens. These situations have been corrected as they were reported. We are still in the process of doing a deep audit of every transaction related to the token sale and in the event that there are errors are found, they will be proactively corrected.Storj stated that an equivalent number of tokens to the number of tokens sold in the token sale would be burned. Has this happened?Yes. There were nearly 75MM tokens sold in the token sale. We have already burned 75MM tokens to match this number as promised prior to the sale.You can see that here…https://etherscan.io/tx/0xfac1371bf41c1bde0317a3120d2f73736cab2e057298cf3feec4a3bbc81c5263What is being done with all of the old SJCX now that it has been replaced with STORJ?The SJCX that has been sent to the converter will all be burned once the converter is shut down.We will also burn all of the remaining SJCX that is held by Storj Labs.When will the converter be shut down?The SJCX to STORJ Token converter will stay active until 11:00 AM EDT on October 25th, 2017.Originally we announced that the converter would be shutdown on October 19th. We have extended the time that it will stay active to account for the down time from the Bitcoin fork precautions.Can SJCX tokens still be converted after the Token Converter is shut down?No. If you do not convert your tokens while the token converter is still active, there will be no options to convert them afterwards. Please make sure to convert your tokens before the converter is taken offline.How is Storj Labs planning on using the funds raised from the Token Sale?Storj Labs will utilize the funds raised in the token sale as stated in the Token Sale Terms document under section B item 8 (Use of Proceeds from Token Sale), which you can find at the link below. https://storj.io/sale-terms.pdf [Less]

As we wrap up work on and around our token sale, we are aware that there are a number of outstanding questions. We are currently in the process of building a report covering the details of the sale and will have the results to share with the ... [More] community in the coming weeks. We will be including data such as… Total STORJ in circulation Number of tokens that have been burned How the time locks for the remaining tokens are structured We appreciate your continued patience and support.   [Less]

We have re-enabled the SJCX to STORJ converter. Thank you for your patience and support! Please send any questions to [email protected].

We recently announced that we are actively monitoring the possible Bitcoin fork, or coin split, and its impact on the Storj ecosystem. We have reached the point where it is necessary to temporarily disabled the SJCX to STORJ converter. This change ... [More] will go in effect tonight, July 31st between 11pm and midnight EDT. We are taking this action to ensure the safety of users’ funds during conversion, as SJCX is a Counterparty token running on the Bitcoin blockchain.On August 1st, 2017 there is a proposal to make changes to the bitcoin software. This proposal, known as Bitcoin Cash, may create a fork in the Bitcoin network. This means that after August 1st, 2017 at 8:20 am EDT there could be two versions of the Bitcoin blockchain and two separate digital currencies. In the event of a coin split, Counterparty will only continue to support one side of this fork as they will continue to run on the Bitcoin core blockchain (BTC) not Bitcoin Cash (BCH).The converter application will be brought back online when we make the determination that it safe to do so, and there is no further risk of loss of users’ funds.Note: If you already had an SJCX transaction in progress at the time this blog post was published, the converter app will still process your conversion, provided that the transaction completes at least 6 confirmations before the expected time of the coin split. Please direct any support questions you may have to [email protected] so we can best assist you. [Less]