Category

Blog

DLT in Decentralized Identity

By | Blog, Hyperledger Indy

Guest post: Dr. Phil Windley, Sovrin Foundation

Since the dawn of the World Wide Web, we’ve been fixated on the concept of place. The entire language of the Web is about location: we visit Web sites using Web addresses. Consequently, it’s almost impossible for us to think there’s any other way. We build places where we expect people and machines (via APIs) to come, meet, and transact. The place metaphor leads to centralization. Facebook, Google, and Amazon are all places. The interactions on them are centralized and under the control of whoever owns the place.

Another way to think about online interaction is in terms of methods—ways of executing actions . Methods for interaction are called protocols. The Internet, domain name resolution, and email are familiar examples of systems based on protocols. Protocols define ways or methods for things to interact. They give the interaction a script, as it were, defining how an interaction plays out. “If you do X, then I’ll do Y.” “If you do X and then do Z, that’s an error.” and so on.

Protocols foster decentralization. By describing the method for interaction, a protocol gives anyone a way to participate. In addition, protocols naturally support interoperability and substitutability. Protocols are largely responsible for what Doc Searls and Dave Weinberger call the three virtues of the Internet:

  • Nobody owns it
  • Everybody can use it
  • Anybody can improve it

This contrast between place and protocol is evident in online identity. We treat identity as if it were something linked to a place. Every online identity you have was given to you by someone else.

This simple fact makes every online identity completely different from identity in the physical world where you exist first, independently, as a sovereign human being. In the physical world, identity emerges from relationships. Over time, humans have developed interaction patterns around how we identify ourselves to each other. In other words, identity in the physical world is a protocol.

Online identity systems are rigid and can only be used in the way their designers allow because places are prescriptive. In contrast, an identity protocol is fluid and flexible, supporting use cases the protocol designer never imagined. As an example, a protocol for identity could give rise to decentralized apps that let anyone share rides in their car without the overhead of a Lyft or Uber because the identity system would let others vouch for the driver or the passenger, independently, using a universally recognized standard.

How can we move online identity from place to protocol? A protocol for online identity would define how identifiers work and how anyone can create, manage, and exchange attributes and claims for those identifiers. A protocol for identity must be private, secure, interoperable, and open to everyone. The result is an identity network.

A protocol for identity relies on the combination of three important standards: decentralized identifiers (DIDs), verifiable claims, and a ledger that is available to all.

Decentralized Identifiers—DIDs allow anyone to create identifiers for anything. Furthermore, they are standard and interoperable. DIDs link to public keys and service endpoints. And because DIDs are pairwise pseudonymous to prevent correlation and preserve privacy, people will have hundreds or thousands of DIDs representing all of the various digital relationships to which they’re a party. These relationships might be with organizations they do business with, friends they interact with, or things they own.

Verifiable Claims—verifiable claims allow trustworthy assertions to be made about anything that has an identifier. Like DIDs, claims are standard and interoperable. Furthermore, they’re based on strong cryptography to bind the claim issuer, the claim subject, and the claim itself. Verifiable claims are combined with zero knowledge proofs for minimal disclosure. For example, when I need to prove to the bank that I’m employed by BYU, I don’t give them the claim. Instead I generate a proof—an incontrovertible certification of some fact—from the claim. The proof discloses only the information the bank needs. All this is done cryptographically so that no party to the transaction has any doubt whether or not the information is correct.

A Distributed Ledger—the ledger links a DID to associated keys and endpoints in a way that’s publicly discoverable. The ledger records information about claims (although not the claims themselves or any other private data). The ledger also supports claim and key revocation. The ledger is foundation for identity transactions.

A protocol for identity allows for ad hoc, decentralized online interactions that follow the patterns humans have developed for establishing trust in the physical world. This promises to unleash countless new decentralized products and services that will transform how people interact online. Joel Monegro wrote in his post on Fat Protocols:

By replicating and storing user data across an open and decentralized network rather than individual applications controlling access to disparate silos of information, we reduce the barriers to entry for new players and create a more vibrant and competitive ecosystem of products and services on top.

Moving online identity from place to protocol creates an open and decentralized network that reduces barriers to entry for new products and services that rely on identity to establish trust.

Meet the TSC: Kelly Olson, Intel

By | Blog, Hyperledger Sawtooth

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.

Kelly Olson, Director of Distributed Ledger at Intel Corporation

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.

 

[VIDEO] Hyperledger Interviews David Treat, Accenture

By | Blog

David Treat is the global lead for Accenture’s Distributed Ledger Blockchain Practice Financial Services. As a services company, Accenture is an integrator of capabilities and wants to bring the best of innovations to clients. Hyperledger is the perfect place for them to be connected with all facets of participants in the blockchain innovation space. David believes being at that heart allows Accenture to bring the best to their clients.

According to David, blockchain has huge potential to move the financial services industry away from messaged based models, slow reconciliation processes and inefficiency of fragmented data stores. With blockchain, financial services can move to a shared data construct, driving down costs, increasing efficiency and opening up entirely new business models.

Blockchain is going to change the way Accenture does business with clients as they think about the network effect and the ability to share data among participants. It changes the model and the entire dynamic for consulting – to not just think about serving a single client but multiple clients and the wider industry.

If you want to be at the heart, innovation and progress of blockchain, Hyperledger is the place to be. The best conversations are happening here. Accenture wants to take the power of this diverse community and bring something truly transformative to all industries, according to David.

Mentorship at Hyperledger: Four Interns Share Their Appreciation for Great Mentors

By | Blog, Hyperledger Fabric, Hyperledger Iroha, Hyperledger Sawtooth

If you read about the projects that Hyperledger’s summer interns have just completed, you’ll quickly see that these are serious internships that come with the prize of greater knowledge, skills, and connections with the technical community. One of the most important of these connections is the connection to a great mentor.

As part of our efforts to foster the development of blockchain talent globally, we pair each of our interns up with an expert to mentor and guide them. Here are all the ways that the mentors involved with Hyperledger’s 2017 summer internship program made a difference, in the words of our interns.

    • “My mentor, Baohua Yang from IBM, helped me in the project to understand and contribute.” — Indirajith Vijai Ananth
    • “My mentor, Jiang Feihu from Huawei Technologies, is one of the most supportive mentors I’ve come across to work with. Right from my selection for the internship, he started mentoring me and strategizing everything, although it was still a month difference from the official beginning of the internship. He’s a good mentor who helped me at every single difficulty that struck my way.” — Nikhil Chawla
    • My mentor was Makoto Takemiya from Soramitsu, and his mentorship helped me understand how Hyperledger Iroha and similar projects worked. We had meetings every week where progress on projects would be presented and where I would ask questions regarding details on Hyperledger Iroha and what the best way of achieving certain tasks would be. Makoto is a very skilled developer and he guided my research and development process to make sure everything was on track.” — Ezequiel Gomez
    • My mentor was László Gönczy from the Budapest University of Technology and Economics (BME), and Quanopt Ltd. His profound knowledge in business process modeling was a continuous source of guidance and support for my work. Firstly, he helped me to select of the BPMN elements to be implemented in the experimental prototype. The BPMN has an extremely large variety of notions in its metamodel (the standard being hundreds of pages long), but the important elements commonly used in the industry form only a smaller subset. Secondly, he helped to refine my approach by providing common, yet complex use cases/sample models. The expert guidance of my mentor played a significant part in successfully completing the project. Our work enjoyed a huge benefit of the professional advices of Imre Kocsis (BME).” — Attila Klenik

Thank you to all of Hyperledger’s mentors for fostering new blockchain talent and ensuring a successful 2017 summer internship program!

Meet the TSC: Arnaud Le Hors, IBM

By | Blog, Hyperledger Burrow, Hyperledger Fabric, Hyperledger Sawtooth

As promised, we’re kicking off a new blog series that focuses on the motivations and backgrounds of the individuals that make up Hyperledger’s Technical Steering Committee (TSC).

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 model has worked for The Linux Foundation for 15+ years and therefore has been purposefully passed down to each open source project to offer an even playing field for all those involved – coming as close as possible to pure technical meritocracy as one can get. The TSC is responsible for all technical decisions – from which features to add, how to add them and when, among others.

With that background, let’s introduce Hyperledger TSC member, Arnaud Le Hors from IBM. 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?

I’m Senior Technical Staff Member of Web & Blockchain Open Technologies at IBM. I’ve been working on open technologies for over 25 years, focusing on standards and open source development, both as a staff member of the X Consortium and W3C, and as a representative for IBM. I was editor of several key web specifications including HTML and DOM and was a pioneer of open source with the release of libXpm in 1990. I participated in several prominent open source projects including the X Window System and Xerces, the Apache XML parser. I currently am the main representative for IBM at W3C, an elected member of the Hyperledger Technical Steering Committee, and a contributor to Hyperledger Fabric.

My main goal is for Hyperledger to not merely be successful technically but be successful as a true Open Source project with an active, vibrant, and diverse community. There are too many projects out there that claim to be open source but fail to have an open governance. In my role on the TSC I will continue to strive to make this community truly open.

Arnaud Le Hors, Senior Technical Staff Member of Web & Blockchain Open Technologies at IBM

How are you or your company currently using Hyperledger technologies or how do you plan to?

IBM Blockchain offering is based on Hyperledger Fabric. After a period of development of proof of concepts we’ve now entered a phase in which we see more and more projects going into production. Some of these like Everledger and Maersk have been highly publicized already with the tracking of diamonds and shipping containers respectively. What I find interesting is that these projects show how broadly applicable blockchain technology really is. This goes way beyond cryptocurrencies.

What are the benefits of Hyperledger’s open governance model?

The power of Open Source is to make it possible for people with different backgrounds and skills to come together and work collaboratively to everybody’s benefit. Everyone gets more out of the project than they individually contribute. This model however only reaches its full potential with an open governance where all contributors are treated equally and have a say in the direction of the project. Without open governance, developers are merely treated as cheap resources willing to give their time and IP without any say as to where the project goes. Sadly, many projects typically led by big corporations do function like that. As I said earlier, it is my goal for Hyperledger to be truly open and part of my role at IBM has been to help our development team to switch from a closed development environment to open source. This doesn’t just happen. One needs to understand what it takes and apply themselves to it.

What’s the most important technical milestone for Hyperledger to reach by the end of 2017?

We’ve already seen the release of Hyperledger Fabric 1.0 earlier this year, Hyperledger Sawtooth and Hyperledger Iroha are working towards their own 1.0 release. I think it would be a great achievement to see those three projects, which were the first to start within Hyperledger, reach that major milestone by the end of the year.

What advice would you offer other technologists or developers interested in getting started working on blockchain?

Blockchain is a new technology. In many respects everybody’s still learning so it is a great time to get started. As more and more companies launch projects leveraging blockchain they will be seeking developers with the needed skills. Those who already worked on developing these skills will become valuable resources. Because all of the Hyperledger technologies are open source there is no cost to getting started. It is merely a matter of being willing to invest your time. Practically speaking, I would advise people to start by familiarizing themselves with the different projects to get some general understanding of the characteristics of the different frameworks. They all include documentation and tutorials that are can be used to get started.

What’s the one thing you hope to accomplish by being a part of Hyperledger’s TSC?

As mentioned before, if there is one thing I hope to accomplish it is to continue driving the project towards being truly open, with not only code in open source but also with an open governance. For example, last year, I took a leading role in the development of the Incubation exit criteria. These are criteria the TSC uses to gauge whether a project is ready to move out of Incubation into Active status. The fact that the criteria we defined are focusing on the maturity of the project – how the project is run, how diverse the community is, etc – rather than the maturity of the software that is developed is a reflection of that goal.

What’s a missing feature or spec that you hope Hyperledger can add in the soon future?

As we see more and more projects reach their 1.0 release, I hope we get more cross pollination happening between projects. For instance, an effort was recently put into integrating Borrow – a permissioned Ethereum virtual machine – with Sawtooth. I hope we get to see more of that kind of efforts happening moving forward.

What’s the biggest struggle or challenge you see Hyperledger having to overcome?

As understanding of the different major components of a blockchain framework improves, with help from the Architecture Working Group, it would be great to be able to identify pieces that can be externalized and shared by the different frameworks rather than have every project host its own. This is however not an easy task and with each project focusing on advancing its own framework it is difficult to get resources allocated to this kind of cross project effort. Once all the projects become more mature it should be easier to find resources for this but it will be harder to make significant changes to frameworks that have already been deployed in production.

What use cases are you most excited about with Hyperledger and/or blockchain?

Voting. Blockchain provides a distributed, secure, and audit-able record that fits perfectly the need of voting processes. What is more important than protecting our democracies?

Interning with Hyperledger: 4 Interns Share Their Experiences and Advice

By | Blog, Hyperledger Cello, Hyperledger Iroha, Hyperledger Sawtooth

Just recently, four talented individuals finished summer internships with Hyperledger. We’re proud to congratulate them on a job well done!

Here, they share details about their projects and advice for students considering an internship in open source software.

About the Projects

Nikhil Chawla from India, mentored by Jiang Feihu from Huawei Technologies, worked on deploying Hyperledger Fabric on Kubernetes using Hyperledger Cello. Nikhil’s approach was twofold. First, it involved manually running Hyperledger Fabric on Kubernetes. Second, it involved automating the deployment using Hyperledger Cello. Nikhil says, “There were a long trail of issues I got to address via this internship. But identifying the levels was a good idea and subdividing the tasks helped me a lot. Moreover, the community channels like Slack and Rocket.Chat were a huge help. I used a variety of measures that can be adapted to reach each sub-task and eventually, solving them optimally.”

Indirajith Vijai Ananth from Italy, mentored by Baohua Yang from IBM, worked on improving and implementing features in Hyperledger Cello. Indirajith says, “The approach can be categorised into three major steps. First, to learn basics and get acquainted to the technology and the domain. Then, to learn deeper by going through the code to understand where and what to work on. The last step was to get involved from writing code and reporting bugs. The outcome of my project was the implementation of a health check feature in Hyperledger Cello for Hyperledger Fabric v1.0 network. This involved restructuring and updating image downloading scripts for Hyperledger Fabric and the respective documentation.”

Ezequiel Gomez from Mexico, mentored by Makoto Takemiya from Soramitsu, worked on anonymous transactions in Hyperledger Iroha. Ezequiel says, “The approach was to first look at how projects that currently have the ability to issue anonymous transactions work. Given that there is a small number of projects that achieve this efficiently, we based our work on Zcash and their usage of zk-SNARKs. The next step was to fully understand the different parts in the Zcash protocol and how this could be implemented on top of the Hyperledger Iroha ledger. I became acquainted with the development community of Zcash Company which helped me understand the academic papers that motivated the project. Given that the core of the project was usage of different cryptographic protocols, most of my research was focused on things such as key establishment, digital signatures and zero knowledge proofs. Since one has to be very careful when working with cryptographic protocols, researching the specifics on each part of the protocol was necessary to avoid mistakes when implementing cryptographic primitives.”

The project depended on staying in sync with the team of developers working on Hyperledger Iroha. Ezequiel says, “The outcome of the project was a standalone service with the functionality needed to implement anonymous transactions into the Hyperledger Iroha distributed ledger. Given that v1.0 of Hyperledger Iroha is still under development, the team decided to have me work on the anonymous transaction part as a standalone service while the team implements an unspent transaction output (UTXO) transaction model into Hyperledger Iroha after v1.0 is released. Without a UTXO model anonymous transactions would not be possible, since the current account model has no way of hiding who the owner of the assets is. The standalone service is not yet finished, and some parts of this service will be developed depending on how the UTXO model gets implemented into Hyperledger Iroha but it currently has two contributors on GitHub working on finishing its components.”

Attila Klenik from Hungary, mentored by László Gönczy from Quanopt and Budapest University of Technology and Economics (BUTE), worked on contract-based business process execution. Attila says, “The goals of the project were 1) to evaluate whether Hyperledger Fabric smart contracts (chaincodes) can fulfill the roles of a business process execution engine, and 2) to develop a methodology for the (almost) automatic migration of business process models (BPM) to the Hyperledger Fabric framework. This approach will enable the merge of existing sophisticated methods in business process modeling with the sound basis of blockchain frameworks.”

The complete coverage of Business Model Process and Notation (BPMN) is still a future work but according to Attila’s expectations, it can follow the approach and technology developed. Attila says, “The core result of the project is a conceptual proof of concept of using BPMN for designing smart contracts. This complements evolving technologies like incorporating business rule systems into blockchain applications by using the Hyperledger Fabric for communication and synchronization purposes. The feasibility of the general approach is proven by a pilot transformation of core BPMN elements to chaincode frames and an ongoing activity targets the re-use of the code developed in traditional BPMN frameworks. The subset implemented is sufficiently rich to support the most common applications.”

Advice to Students Considering an Internship in Open Source Software

As you can see from the experiences above, summer internships in open source software are serious internships that come with the prize of greater knowledge, skills, and connections to the technical community.

If you, or someone you know, is planning to pursue an internship in open source software, here’s a collection of tips they can use from Hyperledger’s 2017 summer interns: Nikhil, Indirajith, Ezequiel, and Attila.

  1. Starting work on an open source project can be a little overwhelming. It’s easy to lose yourself in the details due to a desire to know everything. This is a good thing of course, but not right at the start. To get around this, use a top-down approach when exploring such a project. Focus on the parts you need to work on (or use), and treat everything else like a black box. Once you get familiar with the top, you may take a step toward the bottom.
  2. Don’t be afraid to jump into chat rooms with the project community and ask away! Open source project communities are eager to help new developers and work very hard to make sure future contributors have the resources necessary to understand the codebase. Reading white papers is a good first step before diving into the code. Large open source projects may seem intimidating at first because of their size, but after a higher-level understanding on how the project works, looking at its individual parts will become much easier!
  3. Another way to get started is by cloning the repository of the particular project of interest and start fixing the basic bugs. Slowly, progress can be made by submitting patches and test codes. Eventually, this leads to contributing to an open source project that is going to leave a mark of its own in this technology-driven world.
  4. Before contributing to open source, look at the guidelines for contributing. Going through each and every document is a must, without it you’ll definitely fall into trouble.
  5. There’s a huge variety of projects for all different genres in open source, so choosing the right project is must. Never follow the crowd.
  6. Don’t lose hope if you struggle at first. Soon, you can master open source!

There is plenty of work to be done in open source. Be sure to let the talented students in your life know about this exciting career path.

ABCs of Open Governance

By | Blog, Hyperledger Burrow, Hyperledger Cello, Hyperledger Chaintool, Hyperledger Composer, Hyperledger Explorer, Hyperledger Fabric, Hyperledger Indy, Hyperledger Iroha, Hyperledger Sawtooth

Today, most people understand the concept of Open Source – certainly we expect most readers of this blog understand it. View the code, use the code, copy the code, change the code, and, depending on the license, contribute back changes or not.

What many people don’t get, and something we here at Hyperledger and The Linux Foundation pride ourselves on doing well, is Open Governance.

The Linux Foundation, and all of our 60+ open source projects, are not-for-profits building the greatest shared R&D investment in history. Open Governance is central to this promise.

Open Governance means that technical decisions -– which features to add, how to add them and when, among others – for a given Open Source project or projects are made by a group of community-elected developers drawn from a pool of active participants. It is as close to the ideal of pure technical meritocracy as one can get and we strive continuously to reach that ideal.

Hyperledger recently concluded the 2017-2018 Technical Steering Committee (TSC) election, and so we thought it an opportune time to explain the ABCs of Open Governance. Please note that this is one Open Governance implementation and clearly not the only way to do it, but rather one proven and effective way.

What does the Hyperledger TSC do?

The TSC charter spells out the group’s responsibilities.

The TL;DR is that the TSC is the ultimate authority on technical decisions. This includes which new projects are admitted to Hyperledger , which current projects graduate from Incubation to Active , and the rules by which each Hyperledger project will operate.

Participation in Hyperledger through becoming a Contributor and/or Maintainer is open to anyone.
Hyperledger Charter Section 4C

As a developer or maintainer, this translates into one thing: trust. You know how decisions will be made and the process by which people will be selected to make these decisions. Hyperledger is vendor-neutral and technical contributions are based on meritocracy. We will always remain immune to the commercial interests of any single company.

The TSC election process consists of three simple steps:

  1. Identification of eligible participants
  2. Nominations
  3. Voting

Who is really eligible to be on the TSC?

The charter spells out that the TSC voting members shall consist of eleven (11) elected Contributors or Maintainers chosen by the Active Contributors.

So, how do you determine an active contributor, you may ask? As part of the current election, every project maintainer and Working Group leader was asked to provide a list of all the people that have contributed to their work in the past year. In addition, a review of all code and other contributions was conducted.

This year, 424 active contributors were identified as eligible to participate in the TSC election process.

Bring It (your nomination that is)

The Linux Foundation maintains an expert staff with decades of combined experience managing the operations of large scale, Openly Governed Open Source projects.

For Hyperledger, the Sr. Program Manager Todd Benzies ensures the trains run on time.

Below is Todd’s email calling for TSC nominations:

This nominating process produced 32 candidates for the 11 TSC spots. These 32 come from 20 different organizations, across a spectrum of industries, from technology vendors to foundations to end users from a variety of industries. They include people who work at Hyperledger members and non-members and some are standing as individuals.

A policy whose importance is hard to overstate is that anyone elected to a seat on the TSC is elected as a person unbound to the company for which they presently work. Should any TSC member during their tenure leave an employer for another, this would have zero impact on their standing as member of the Hyperledger TSC.

Cast your vote

Here is Todd’s email sent to the same list announcing the nominees and opening voting.

The arrow highlights one of the things that we’ve learned along the way as a trick to the trade of running open governance well. The voting system has to be unquestionably secure and fair (something by now truly everyone can relate to…).

We use the Condorcet Internet Voting System to safeguard the privacy of this election and voting process. CIVS can only be accessed by authorized voters, who receive a unique URL tied to their email address. Voters rank a set of possible choices and individual voter rankings are combined into an anonymous overall ranking of the choices. One vote is allowed per IP address.

Results

This process yields a fairly and openly-elected technical decision making body pulled from the community that cares about Hyperledger. We know they care not because they said so, not because the company they work for has joined Hyperledger, but because they invested their time to make contributions to Hyperledger code bases. Or, as Hyperledger Executive Director Brian Behlendorf says, “it’s a do -ocracy.”

Meet the New Hyperledger TSC (listed in alphabetical order)

Arnaud Le Hors
Baohua Yang
Binh Nguyen
Christopher Ferris
Dan Middleton
Greg Haskins
Hart Montgomery
Jonathan Levi (new)
Kelly Olson (new)
Mic Bowman
Nathan George (new)

If you’re interested in learning more about the Hyperledger TSC and its elected members, we’ll be kicking off a “Meet the TSC” blog series in the coming weeks. Be sure to look out for it!

You can plug into the community at github , Rocket.Chat the wiki or our mailing list .

Developer Showcase Series: Andy Berti, Tradeix

By | Blog

Our Developer Showcase blog series serves to highlight the work and motivations of developers, users and researchers collaborating on Hyperledger’s incubated projects. Next up is Andy Berti, CTO at Tradeix.

What advice would you offer other technologists or developers interested in getting started working on blockchain?

Have a goal. Look for how blockchain can help your business idea, rather than how you can mould your business idea around blockchain. I believe that developing technology for technology’s sake is rather futile. You need to have a strong business idea to execute and while doing that leverage the advantages that a great blockchain solution gives.

Give a bit of background on what you’re working on, and let us know what was it that made you want to get into blockchain?

We at Tradeix are managing a trade finance platform, called TIX which allows organisations and developers to create their own trade finance eco-systems. We utilize blockchain to provide the irrefutable source of truth for our digital assets (invoices). My first blockchain experience was with Bitcoin where I dabbled with proof-of-existence models. The thought of stamping obfuscated or encrypted content into a public blockchain was a bit of fun. After I lost out in the MtGox debacle, my thoughts turned to blockchain for the financial services industry and how permissioned ledgers in particular could be utilized.   

Andy Berti, CTO at Tradeix

What do you think is most important for Hyperledger to focus on in the next year?

Low barriers to entry are important. We can all sometimes get lost in the details especially when we are on the leading edge of technology. With Hyperledger being successful it is important to be very easy for the average developer to pick up and use as well as simple for the average business person to understand.

What’s the one issue or problem you hope blockchain can solve?

Voting. It may take a while, but the path toward a secure, irrefutable, electronic voting mechanism for all our democracies would be a beautiful thing. No more paper ballots, hackable machines, just vote from your phone and you’re done.

What is the best piece of developer advice you’ve ever received?

Think of the poor devil who has to support this code.

 

[VIDEO] Hyperledger Interviews Makoto Takemiya, Soramitsu

By | Blog

We spoke with Makoto Takemiya, Co-CEO of Soramitsu. The benefits of being a member of Hyperledger for Soramitsu include the networking capabilities and the sharing of information with many other companies.

In 2017, Soramitsu is using Hyperledger technologies to create real life systems as well as prototypes. According to Makoto, blockchain will affect their customers by increasing possibilities with throughput and data analysis. Blockchain will also change the way they do business with their customers by allowing them to create more decentralized platforms where they can all play at the same level.

Makoto says the main reason to join Hyperledger is for the connections you can build but also the ability to have a say in how this emerging technology is built.

Watch the full video here:

Congratulations to the Hyperledger Interns and Mentors on Completed Summer Internships

By | Blog, Hyperledger Cello, Hyperledger Iroha, Hyperledger Sawtooth

As part of Hyperledger’s mission to advance cross-industry blockchain technologies, we strive to foster talent globally. One way we do this is through a summer internship program.

The Hyperledger summer internship program pairs talented university students with blockchain experts from the technical community. Each intern takes on a specific project that will benefit the Hyperledger community and his or her mentor provides guidance to help the intern be successful.

This month, interns from Mexico, Hungary, Italy, and India have completed their internships and will be returning to their university communities to use and share what they have learned.

  • Attila Klenik from Hungary, mentored by László Gönczy from Quanopt and Budapest University of Technology and Economics (BUTE), returns to BUTE. Attila worked on contract-based business process execution.
  • Ezequiel Gomez from Mexico, mentored by Makoto Takemiya from Soramitsu, returns to Boston University. Ezequiel worked on anonymous transactions in Hyperledger Iroha.
  • Indirajith Vijai Ananth from Italy, mentored by Baohua Yang from IBM, returns to University of Rome Tor Vergata. Indirajith worked on improving and implementing features in Hyperledger Cello.
  • Nikhil Chawla from India, mentored by Jiang Feihu from Huawei Technologies, returns to Northern India Engineering College. Nikhil worked on deploying Hyperledger Fabric on Kubernetes using Hyperledger Cello.

Here’s a snapshot of our accomplished interns across the globe:

In upcoming posts about interning at Hyperledger, we’ll share details about the projects and advice for students considering an internship in open source software. We’ll also discuss the important role of mentorship.