Back to our blog series that focuses on the motivations and backgrounds of the individuals that make up Hyperledger’s Technical Steering Committee (TSC). As a reminder, the TSC is a group of community-elected developers drawn from a pool of active participants and is a core element of Hyperledger’s Open Governance model. The TSC is responsible for all technical decisions – from which features to add, how to add them and when, among others.
Now let’s introduce our next Hyperledger TSC member, Kelly Olson from Intel. Let’s see what he had to say about Hyperledger, his role in the TSC and the community!
Describe your current role, background and why you wanted to be a part of the Hyperledger TSC?
My current role is as Director of Distributed Ledger Technology at Intel. Hyperledger is the leading organization in the open source development of blockchains for enterprise. I’m looking forward to advancing this cause and encouraging collaboration among the many Hyperledger projects.
How are you or your company currently using Hyperledger technologies or how do you plan to?
Intel is leveraging Hyperledger Sawtooth for a number of internal and external deployments.
What are the benefits of Hyperledger’s open governance model?
For technology to be trustworthy it is important that not only the source code be open source, but also the process by which it is managed. It is important that anyone can contribute to the process so that the best ideas can be used.
What’s the most important technical milestone for Hyperledger to reach by the end of 2017?
I’d like to see more projects mature to a 1.0 release in the remaining few months of 2017.
What advice would you offer other technologists or developers interested in getting started working on blockchain?
The best way to understand the benefits blockchain provides, and how it can be used is to start experimenting. I’d recommend that anyone interested start with one of the getting started tutorials provided by most Hyperledger projects.
What’s the one thing you hope to accomplish by being a part of Hyperledger’s TSC?
I hope to ensure that software coming out of Hyperledger is secure and developed with best practices.
What’s a missing feature or spec that you hope Hyperledger can add in the soon future?
I think that interoperability and privacy are two elements that have yet to be solved in an adequate way for blockchain software. I’d like to see more collaboration between the projects with a goal of achieving some level of interoperability.
What’s the biggest struggle or challenge you see Hyperledger having to overcome?
I think we are in the very early stages of blockchain deployment. Today blockchains have limitations around privacy and scalability that need to be addressed before widespread adoption.
What use cases are you most excited about with Hyperledger and/or blockchain?
Blockchains provide a few unique capabilities not provided by traditional distributed databases. These include the ability for multiple organizations to securely share a common record in a more ‘democratic manner’ and they also provide strong guarantees around immutability. The best use cases I’ve seen leverage one, or both, of these properties.