The 2019 Hyperledger Summer Mentorship program has come to an end. During this program, my project was Design Effective OS to Manage Blockchain Networks. It was an amazing experience to work and get involved with the Hyperledger community and the Cello community. I had a wonderful time working with my mentors and the community members, who were all really helpful during the whole course of this internship.

Goals of Project

This project aimed at:

• Implementing a new governing module to join blockchain networks together
• Adding advanced capabilities to manage blockchain networks, including life-cycle, chaincode and permission
• Developing other open objects that align with the existing roadmap

What was Accomplished

During the internship duration, we were able to implement a fully functional agent that makes Cello even more versatile than earlier. We were able to 

• Create a base for an operator agent for Fabric in the Cello codebase
• Create custom resources and APIs for CAs, peer and orderer
• Implement the operator controllers for CA, peer and orderer
• Integrate the agent with the Cello API and dashboard
• Generate documentation for the new agent so that it can be used by the users

Project Progress

During my project, we successfully created an agent for Hyperledger Cello that can be used to create peer, CAs and orderers for Hyperledger Fabric. This agent can handle user inputs from the frontend as well as the certificates needed for running these nodes. The agent was developed using Kubernetes and uses the Operator SDK Framework to create Kubernetes Operators. 

The agent has been linked to the frontend and APIs and documentation has also been created to make sure that it is ready to be worked upon.

What I learned

• The project used Kubernetes and Golang for its creation, and it was really good to learn the tools needed to complete my projects.
• I learned to collaborate in an open source project, working remotely and successfully communicating with other members of the community.

Future Plans

• I’ll be continuing my work with the Cello project, contributing code in the future to help with the other parts of the project.
• This project has laid the groundwork for additional features that can be added to the agent and Cello itself, which can make it fully ready for the production usage.

For the full details, see my complete project report here.

I am very grateful for the support from my mentors, Baohua Yang, Haitao Yue, Tong Li and Jiahao Chen, as well as Hyperledger and for the opportunity to learn and contribute to open source Hyperledger projects.

I will also be speaking at Hyperledger Global Forum 2020 in Phoenix, Arizona, talking about my project and work and also Hyperledger Cello. Please do come if you’re attending the conference.

This year, I had the opportunity to contribute to the open source Hyperledger Indy community as part of the 2019 Hyperledger Summer Mentorship program. This experience also helped me collaborate with other open source communities, mainly the git community.

Project presentation

Currently git supports signing/verifying commits and tags using GPG only. The goal of this project is to make the git signing interface compatible with external signing tools and with DIDs (Distributed Identities) using programs such as bettersign, for example.

This project is the continuation of the work already done by David Huseby on the subject. His previous work is here:

• https://github.com/dhuseby/did-git-spec
• https://github.com/dhuseby/did-git-impl

This project’s working fork:

• https://github.com/ibrahimel/did-git-impl

The main sections of the project are updating the user configuration and the command handling when a signing or verifying operation occur. 

Another aspect of the project is getting the changes accepted in the git community:

• The request for proposal has been sent to the git mailing list and can be tracked here.

• The commits that will be submitted as a patch can be found here.

What was accomplished

Milestones

The project had many steps involved:

• Updating the git code base with a new generic signing interface
• Sending the first RFC to the git mailing list and receiving feedback
• Incorporating the changes depending on the received feedback
• Sending a second RFC to the mailing list
• … Still waiting for feedback
• Creating wrapper tools for signing (Indy signing tool and a template script)

Challenges

Getting to know the git code base from scratch and figure out which parts needed changing was a challenge at first. But the primary challenge we faced was getting the proposal pushed upstream in the git community. We have sent two RFCs and are still waiting for additional feedback.

Technical Overview

The following figure illustrate modification of git and the expected outcome of the project:

What comes next

This project can open the door to future signing tools integrations and maybe extended to projects other than git.

The mentorship project can be extended in many ways:

• Create wrappers for additional signing tools like signify for example
• Write a wrapper for the Assuan protocol to add support for tools that use the Assuan library (like GPG & GPGSM for example)
• Broaden the project idea to tools other than git (Docker image signing for example)

David Huseby will be creating a Hyperledger Lab for the continuity of the project. It will be used to track future milestones and help other persons contribute and broaden the project perspective.

For more details, please see my complete project report here.

Project Description

Construction management configuration of blockchain is a project of the Hyperledger Summer Mentorship Program 2019 that provides a way to apply Hyperledger technologies to construction and engineering (C&E) since literature research and practical simulation prove Hyperledger Fabric as one of the best platforms for C&E. 

This project was conceived to test the potential of blockchains. To do this, a prototype system is used to model real-world commercial process by defining the properties of participant attributes superimposed with algorithms that describe their trading relationships. These are implemented using so-called smart-contracts that make use of the latest features of Hyperledger Fabric  and Hyperledger Composer to model commercial relations between traders in a trust network.

Using Fabric delivers a variety of benefits. For example, the scheduling, confirmation and commissioning of installed components at a construction site can be recorded and, therefore, managed. But management of a Fabric network is a demanding job and good design is essential to allow confidential trading to take place. The access control list (ACL), included within Composer, provides the tools to create, read, update, or delete elements within the commercial network’s domain model. The project has advanced this control by making use of an application programming interface (API) to connect to Web servers that in turn can provide analysis and management applications. This links to common project management tools, notably Gantt charts and other projects metrics such as individual work rates, cost and budgetary items that can be used in reports and figures. 

Tools: Hyperledger Fabric, Hyperledger Composer, Node.js, javascript.

Analyze real construction process

System architecture

Access control for participants

Accomplishments

• Created a system design for a construction management blockchain implemented on Hyperledger Fabric and Hyperledger Composer.
• Built an access control list for manipulating access rights of individuals in the blockchain system.
• Developed an API for connecting Hyperledger Fabric with web services.
• Built a website for easily making transaction from customer and exchanging information.
• Created algorithms that are able to analyze data inside a blockchain and represent results in the form of statistics figures such as Gantt chart, line chart and pipe chart.
• Developed a tutorial on github for installing and using the system.
• Wrote science publications.

Plan for the future

• The project is only implemented in localhost for testing functions of blockchain system because of limited budget and computer power. If the project is funded for a free account of cloud and computers, a blockchain system can be deployed on a cloud by using docker and tested in real conditions.
• With detailed documents and source code, the project would equip developers to convert business needs to algorithms and implement them to chaincode, generate APIs for exchanging data between user and blockchain system, create user interface, make statistics and apply machine learning algorithm for data in transactions. Furthermore, the project’s system architecture defines a method  to combine blockchain, statistics and machine learning based on smart contracts, which would be helpful for Hyperledger to develop extend modules.

For more details, please see my complete project report here.

During the last six months, I had the chance to work as a part-time intern for the “Hyperledger Fabric-Based Access Control” project. It was my first contribution to an open source project, which was a great learning experience for me. I believe that contribution to an open source project leads to better understanding and more in-depth knowledge by accessing unlimited resources. I also had the chance to work with two amazing mentors from Universidade Nova de Lisboa, Professor Rui Cruz and  Rafael Belchior. 

Project Introduction and goals

The project goal was to create an attribute-based access control system on top of Hyperledger Fabric. We presented a system architecture with an implementation based on Hyperledger Fabric. We used the Google Cloud Platform to run a Virtual Machine instance and test our application and collect performance analysis data. The proposed solution was validated through a multi-stakeholder use case of independent digital libraries. Our preliminary evaluation based on Hyperledger Caliper shows that the system can achieve around 200 access control requests per second, with a latency of around 0.3 seconds. 

Project accomplishments

• Developing System modelling and architecture (Figure 1)
• Implementing the attribute-based access control components as Hyperledger Fabric ChainCode (smart contracts) and creating a simple front-end interface to interact with blockchain application
• Conducting performance analysis based on Hyperledger Caliper
• Analyzing performance data and graph visualization using matplot library
• Presenting the project in the format of academic paper

Figure 1. System architecture

Future works

Currently, our project only addresses the authorization components. This project can be expanded to be integrated with the authentication component as well, for example, it can be integrated with Hyperledger Indy, as Hyperledger Indy provides a powerful structure for decentralized identity and systems authentication. 

I want to thank the Linux Foundation and Hyperledger team for providing this opportunity for me and all the other mentees. I also want to especially thank Min Yu. I greatly appreciate her kind assistance during the whole internship program. Lastly, I want to thank my two fantastic mentors, Professor Rui Cruz and Rafael Belchior. I truly appreciate and value everything I have learned from you. 

For more details, please see my complete project report here.

What I worked on

I’m Hengming Zhang, a member of this summer’s Hyperledger Mentorship Program.

The general goal of my project was extending the security scope of the Hyperledger Fabric SDK for Node.js. Key objectives included:

• Fix integration test failures on various operating systems.
• Refactor the key store class design by object-oriented method.
• Enhance the compatibilities of Hardware Security Module (HSM).
• Construct an applicable offline signing scheme.

After having the first talk with my mentor, David Liu, I set out the milestones and deliverables with this project:

1. Completing a list of checklist items that were established before the beginning of Hyperledger Mentorship Program. The checklist contains preparing:
   • AWS cloud account
   • Virtual machine snapshot for the on-premise desktop
   • Mobile devices
2. Fixing  the integration test failures on macOS and Ubuntu by the 1^st Quarter Evaluation.
3. Refactoring Key store class design by the Midterm Quarter Evaluation.
4. Enhancing HSM compatibility by the 3rd Quarter Evaluation.
5. Offline signing of a client by the Final Evaluation.

Once I had finished the initial set up from the checklist, I started development for this project. During the development, the proudest of experience were using the right Hyperledger channels:

• Technology – Hyperledger Fabric, Hyperledger Fabric CA, and Hyperledger SDK for Node.js.

• Tools – Hyperledger Wiki, Hyperledger Gerrit, Hyperledger Chat and Hyperledger Jira.

By the end of this internship, I had finished 6/7 of the deliverables I had created above.

In conclusion, I think my work on the offline signing scheme could have the most impact on the Hyperledger or larger communities. I have constructed an applicable client offline signing scheme using Flutter as the client for the fabric-client-flutter project and Node as the server for the fabric-server-node project.

At last, there are our mentor and mentee’s information for this summer’s Hyperledger Mentorship Program:

Mentor	Email	Organization
David (Yuxiang) Liu	david-khala@hotmail.com	MediConCen

Mentee	Email	University
Hengming (5sWind) Zhang	fiveswind@gmail.com	Fudan University

What I learned or accomplished

As I mentioned in the “What I worked on” section, the six deliverables I completed include:

• Setting up an AWS cloud account
• Creating a virtual machine snapshot for the on-premise desktop
• Preparing mobile devices
• Fixing the integration test failures on macOS and Ubuntu
• Enhancing HSM compatibility
• Offline signing of client

However, there are no such shortcut path as things moved forward. Below are some of the issues I had to overcome: 

• Running AWS CloudHSM on EC2 instance: Ubuntu 18 / Windows Server 2019 / Red Hat Enterprise Linux
• Installing SoftHSM on Windows 10 virtual machine snapshot
• Constructing a PKCS#8 standard RSA asymmetric keys that can be used to interact with Hyperledger Fabric network as the user’s local key store
• Constructing a Certificate Signing Request (CSR) using RSA keys on the client side
• Building an interactive model between Hyperledger Fabric and Flutter mobile client
• Refactoring current CryptoKeyStore mixin class to an object-oriented class model

Plus, there are also some of the insights I got and lessons I learned from the Hyperledger community:

1. Communicate with others (e.g., project maintainers, mentors)
2. Connect and work remotely
3. Document ideas, issues, and reports
4. Clean code and use state-of-the-art technologies

So, at this time, I would like to share with you some advice regarding working in an open source community:

1. Clean code and annotations are necessary: it means when others look at your project, they can quickly understand what your code does.
2. Communication is important: it can help to deduplicate works, find solutions, and so on.

For example, in my internship experience, leveraging the second piece of  advice, I found out that the community was refactoring the code base that I was working on. Therefore, the duplicated work could be avoided.

What comes next

The ending of the internship journey is not the destination. I have some recommended next steps for the project:

• Advancing and improving the fabric-client-flutter project, such as extend it to support other platforms: Windows, macOS, and even IoT devices for them to use Hyperledger Fabric.

• Refactoring and improving the fabric-server-node project to common Hyperledger Fabric servers that can be serving any request from any Hyperledger Fabric client.
• Continuously contributing to the fabric-sdk-node project.

In the future, I would like to be a long-term contributor to the Hyperledger or the larger open source community.

With this internship experience, I hope I can move forward as a recognized engineer and cryptographic researcher.

For more details, see my project report here.

What I worked on

The simulation research internship during the summer of 2018 led to the creation of the Hyperledger Umbra Lab. Due to the overall difficulty of getting Hyperledger blockchain frameworks running under the Shadow simulation tool, work on the Umbra lab had slowed to a crawl. A different network (si)emulation tool called Mininet had been proposed as an alternative to using Shadow with the potential to drastically reduce the startup cost of getting a network simulation tool running Hyperledger blockchains. My research project was to test the feasibility of running Hyperledger blockchains under Mininet for the purposes of running scalability and consensus mechanism experiments.

Project Objectives:

1. Build reference architecture (Logical View and Process View)
2. Evaluate Fabric project with reference architecture
3. Build Stimulus, Monitoring, Dynamics
4. Build Analysis
5. Extend architecture to other Hyperledger project(s)
6. Document the project

What I accomplished

By the end of my project, I had completed the design of a generic event-oriented platform that can be modularly extended  to reproduce any Hyperledger blockchain platform. The main difficulty was getting a clear understanding of working with Fabric as integration with this tool was not well documented. The documentation, especially,for how to create an example of extending Umbra for another blockchain project, is still going on.

Project Deliverables:

1. Generic platform for running Hyperledger  blockchain platforms 
2. Reproducible Ad-hoc Hyperledger Fabric Network (main achievement)
3. Reproducible Ad-hoc Hyperledger Iroha Network (almost finished)
4. Documentation (ongoing)
5. Accepted for Hyperledger Global Forum 2020

What comes next

This is the beginning of reproducible academic work on Hyperledger blockchain projects (i.e., the development of comparable methodologies for consensus, gossip, security, etc.). Now, the most interesting work is running Umbra at scale as a cloud with hundreds/thousands of blockchain nodes.

For more details, please see my complete project report here.

Many Thanks to the Hyperledger MentorshipCommunity!

#umbra via labs@lists.hyperledger.org
https://github.com/hyperledger-labs/umbra

Raphael Vicente Rosa
https://intrig.dca.fee.unicamp.br/raphaelvrosa/
https://www.linkedin.com/in/raphaelvrosa

This year, I had the amazing opportunity to contribute to the open source Hyperledger community as part of the 2019 Hyperledger Mentorship program. Participating in the program also gave me valuable experience in working on open source projects!

What I worked on

I primarily contributed to Hyperledger Iroha, a permissioned decentralized ledger technology. Iroha is capable of creating and managing assets, identity, and more. Behind the scenes, the efficient ed25519 signature scheme is used for securing transactions, blocks, and consensus votes.

I also worked with Ursa, a Hyperledger project that aims to provide a reusable cryptographic library for other projects in the Hyperledger ecosystem.

Working with both the Iroha and Ursa communities was a very rewarding experience. After completing this project, the thought of making contributions to open source projects no longer feels daunting. Additionally, I had extraordinary guidance from my mentor, Andrei Lebedev, who is part of the Iroha team. Without his mentoring, I do not believe my project would have been as successful as it turned out!

What I accomplished

Goal

The main goal of my work was to enable Iroha to call Ursa for verifying and creating cryptographic signatures. 

Accomplishing this goal required the following major steps:

• Integrating Ursa into Iroha’s build process
• Interfacing with Ursa’s ed25519 signature functions 
• Maintaining support for both the original Iroha crypto and Ursa crypto
• Making it easy to choose a cryptography provider through the configuration file

Challenges

The primary challenge we faced was a slight difference in the original Iroha ed25519 code and the Ursa ed25519 code, preventing Ursa from being a simple drop-in replacement. Overcoming this challenge meant maintaining compatibility with both the existing Iroha crypto library and the Ursa library.

Integration Overview

The following figure illustrates the architecture of the Ursa integration.

What comes next

I’m very excited about the potential of this integration. Moving Hyperledger projects onto a standard cryptographic library is beneficial for increasing security, reducing duplicated efforts, and improving the overall ecosystem. I also hope that my work may serve as a reference for other Hyperledger projects that may be interested in integrating Ursa cryptography.

The internship project can be extended in the following ways:

• Support compiling Ursa through Iroha’s build system in non-Unix environments
• Improve documentation for using Ursa cryptography provider
• Support Ursa-compatible ed25519 in Iroha’s client libraries 

As someone interested in working on distributed systems, cryptography, and other areas related to core blockchain development, this was the perfect internship for me. Working on it only solidified my passion for these areas of software engineering, and I plan to continue my career working on blockchain systems and security.

More details about the implementation of my project are available here; I encourage anybody interested to read more about it!

Introduction

Hyperledger Indy is a public and permissioned chain platform designed for identity-related usage. In this project, we use Decentralized Identifiers (DIDs) and Verifiable Credentials combined with Indy ledger to realize Self-Sovereign Identity concept for IoT devices. Specifically, we designed a Decentralized Ledger Technology (DLT) architecture for supply chain process of telecom devices and implemented this architecture.

During this project, my mentor, Laura Spinaci, and I work on a design based on the proposal of Global System for Mobile Communications (GSMA), and utilized the unique properties of Hyperledger Indy.

Accomplishments

1. Designed a DLT architecture for supply chain process of telecom devices.
2. Implemented this architecture with DIDs, Verifiable Credentials and Hyperledger Indy Python packages. In this protocol, we have multiple Schema issuers and multiple Credential issuers due to the different roles of mobile network operators, manufacturers, quality assurance teams, and end users.
3. Created the docker test environment (to be completed by 12/20/2019). In the test environment, we use different port in single computer to act like different nodes in the entire network.
4. Provided API documents for telecom devices companies, and a simple front-end demo (to be completed by 12/20/2019)

What comes next

For IoT devices, the device-to-device access and communication can enhance the entire systems ability of, for example, using Google voice kit to automatically control the smart home devices. Additionally, design details for privacy and user-device interaction also need to be refined.

However, as the project timeline is quite limited, these parts are left for the further development. I am happy and willing to make further open source contributions to them, and to Indy and the entire Hyperledger ecosystem.

For detail project information, please check this wiki page.

I always wondered how it is like to be an open source contributor. I always wanted to work in an open source project, but I was hesitant about where to start. The Hyperledger Mentorship Program provided me with an opportunity to begin my journey in the open source world.

I had an enjoyable experience working with my mentors Swetha Repakula, Morgan Bauer and Jay Guo. They were really encouraging and very supportive throughout the period.  Although I was very new to the tech stack we used in this internship, my mentors helped a lot and were always there to resolve my doubts. 

Project goals

Hyperledger Fabric chaincode shims are only available in Golang, javascript, and java, which may limit developers around the world. For some, learning those languages and associated skill sets are a barrier to adoption of Hyperledger Fabric. 

My internship project Fabric Chaincode Wasm enables developers to use a wide variety of source languages for developing chaincodes by introducing a WebAssembly run time to Fabric users. WebAssembly exposes lots of languages for development, including C, Rust, and many more, because they can directly compile to WebAssembly.

You can find more information, reports and demo video here: https://wiki.hyperledger.org/display/INTERN/Running+Web+Assembly+Smart+Contracts+in+Fabric

Quick Technical Summary

As part of the project, we focused on creating an integration layer for deploying WebAssembly based chaincodes on Hyperledger Fabric without having none to minimal effect on Hyperledger Fabric core code. We achieved this by creating a Golang based chaincode named as wasmcc with an embedded WebAssembly Execution VM. This chaincode also exposes shim functions for WebAssembly chaincode developers to interact with Hyperledger Fabric networks and ledgers.

Here are some quick flow diagrams on how a WebAssembly chaincode is deployed and executed using this project.

Accomplishments

• This project gave me a great chance to really learn WebAssembly and Golang.
• My mentors guided me on various tools and best practices for open source community such as multiple Github features, which I never knew, the thinking process and creating CI/CD pipeline for open source projects. 
• The most challenging part would be researching on WebAssembly and looking for a feasible WebAssembly based execution engine.

What comes next

This project has vast potential. It will allow people to quickly start adopting Hyperledger Fabric who were not able to due to technical language. Likewise, businesses can quickly start using Hyperledger Fabric without having to add to their teams’ existing available skill sets. By lowering these barriers to adoption, we’ve helped make Hyperledger Fabric an even more appealing choice as a blockchain platform. These features could also help in expanding the Hyperledger community.

Few of the technical improvement for future roadmaps:

• Create minimal interfaces for languages that can be compiled to WebAssembly
• Expose all other shim functions such as ACL for WebAssembly chaincodes
• Try other WebAssembly execution engines as this area is evolving daily.
• Create more examples using languages such as python, dotnet etc.

For all my fellow aspiring open source beginners, I only have one message for you: stop thinking and start engaging. You will find lots of encouraging people to guide you further. Take that Leap of Faith!

Lastly, I would like to thank the Linux Foundation committee for starting this mentorship program. I am sure it will be a life-turning experience for all my fellow mentees like me. I am also very thankful to Min Yu, my mentors and open source contributors for making this a smooth journey for me.

Please feel free to connect with me if you are interested in contributing to this project. You can find the repository under hyperledger labs, and you can always ping me at @shubham_aggarwal at rocketchat.