CEO of OpenOrchard, Developers of Koinos
In the article on the upgradeability crisis I explained how the fact that decentralized computing (i.e. “blockchain”) is still in its infancy means that early efforts did not have access to preexisting platforms or tools that developers could use to build their apps.
I’m Andrew Levine, the CEO of OpenOrchard where we are developing the Koinos blockchain.
Engineering Koinos is a group of battle-hardened blockchain developers with unrivaled experience as core developers and architects of the Bitshares and Steem blockchains, two of the most used blockchains ever. It was through our first hand experience working with some of the most performant blockchains, and their shortcomings, that we learned about the most serious problems facing the mass adoption of this technology.
Our mission is to empower people through ownership of their digital selves and blockchain is the most promising technology for accomplishing this mission. Blockchain-based applications can add value to people’s lives in an infinite variety of ways but building such applications is far too difficult, time consuming, and expensive. Not only that, but existing blockchain platforms make it impossible for developers to deliver pleasant user experiences.
The Three Crises
I’m currently publishing a series of articles on Cointelegraph in which I describe what we (the OpenOrchard team) see as the three crises holding back blockchain adoption. But that isn’t the best for more technical discussions and at the end of the day, a blockchain is only as good as the developers who use it. That’s why I’ll be publishing companion pieces (starting this one to Hackernoon), the best place on the internet for developers!
If you’d like to read the first two articles in the Cointelegraph you can find them here:
In the article on the upgradeability crisis I explained how the fact that decentralized computing (i.e. “blockchain”) is still in its infancy means that early efforts did not have access to preexisting platforms or tools that developers could use to build their apps. Instead they have to build their stack from the ground up. Because these developers are usually trying to solve a specific problem which they believe the new technology is uniquely suited for, they design their stack as a monolith that is optimized for their specific application.
Some of these applications can be quite successful, which leads other developers to model their application designs after these early applications which seem to be prospering. The problem is that while these apps appear successful they are actually incredibly fragile, which is why it is so exceptionally rare for the applications developed in the early stage of a new computing paradigm to survive more than a few years.
But why are they so fragile? To answer that question we can turn to the leading expert on fragility, Nassim Taleb, who explains that antifragility is a property that emerges from multi-layered, hierarchical systems that contain fragile sub-units which, by breaking/dying/blowing up, result in an overall healthier system. To put it simply: evolution. Evolution is when a species replaces one implementation of a trait with another that improves fitness. In computing we call these “upgrades.”
All the major blockchains weren’t designed to be upgraded, so they aren’t capable of evolution. This means that when a Black Swan event occurs, the system is likely to blow up.
The answer is clear; we need multi-layered, hierarchical systems that contain fragile sub-units. This is why operating systems emerge. They provide a massive competitive advantage to application developers, but they still suffer from the same upgradeability problem of the first generation applications. They provide core features, security, and a shared user base, but there is no layer beneath them, so they eventually become feature-bloated, complex, and difficult to upgrade.
The solution to this problem is an abstraction layer below even the operating system; a BIOS (basic input/output system). An operating system for the operating system, designed not to make application development easier, but to make it easier to boot up and upgrade the operating system itself. While seemingly simple, this enables the operating system to evolve. Operating system developers can now rapidly respond to the changing needs of developers by releasing software upgrades and bug patches to the network piecemeal while minimizing downtime.
This explains why none of the general purpose blockchains that have launched after Ethereum have managed to displace it, despite its slow pace of progress. I contend that the reason for this is that no blockchain has taken the analogy of the operating system seriously enough by creating a genuine BIOS-equivalent.
So what will Koinos bring to the table? Well, we’re not quite ready to divulge all the secrets of how Koinos quit yet, but that will all be changing very soon :). I’ll be releasing more articles on Cointelegraph and related articles onto Hackernoon, so be sure to subscribe, follow me on Twitter, and for super important Koinos updates, be sure to join our mailing list by going to openorchard.io.