ETHWaterloo Hackathon Second Place Winner for Storj Challenge: BIT

The 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 BIT team and the app they built on top of Storj.

CapLinked Partners With Storj Labs

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

Using the Storj Add-on with Heroku

We recently announced a partnership with Heroku to make it easy for developers to use Storj’s distributed object storage. Heroku is a cloud platform that enables app developers to spend their time on application code rather than managing server infrastructure, and it’s one of the largest developer ecosystems in the world. You can find the Storj add-on in Heroku’s Elements marketplace.

Try Storj on Heroku

Dear Storj supporters,

We are excited to announce that Storj is in beta testing on Heroku’s Elements marketplace. Heroku is a cloud platform that lets app developers spend their time on application code, not managing server infrastructure, and it’s one of the largest developer ecosystems in the world.

How To DDoS Yourself

We’ve been dealing with some backend issues recently. Something has been making our Bridge servers hang, which caused even simple requests to time out. This impacted everything from user registration to file retrievals. These time outs manifested as “502 - Bad Gateway” errors from our API as the servers accepted connections, and then failed to do anything with them. We spent a lot of time and effort tracking down the root of the issue. Turns out one overlooked variable assignment caused it all.

Submit your Ideas