Helping A Community Grow By Pruning Inactive Projects read more >

Skip to main content
Hyperledger Foundation
search
Menu
  • Learn
    • Case Studies
    • White Papers
    • Training & Certification
    • Training Partners
    • Webinars
    • Research
    • Blockchain Showcase
    • Wiki
  • Use
    • Distributed Ledgers
    • Domain-Specific
    • Libraries
    • Tools
    • Tutorials
    • Hyperledger Certified Service Providers
    • Vendor Directory
  • Participate
    • Collaboration Tools
    • Contribute to Coding
    • Academic Collaboration
    • Find a Meetup
    • Regional Communities
    • Speakers Bureau
    • Join a Community Group
    • Labs
  • Events
  • News
    • Blog
    • Announcements
    • Newsletter
  • About
    • Join Hyperledger
    • Members
    • Leadership
    • Charter
    • Job Board
    • Contact Us
  • Join
  • English
    • 简体中文
    • Português
    • Français
    • Malayalam
    • 日本語
    • Español
  • search
Close Search
Category

Hyperledger Bevel

Jan 11
Love0

Hyperledger Mentorship Spotlight: Upgrade Fabric network from 1.4.x to 2.2.x using Hyperledger Bevel

By Mohit Vaish Blog, Hyperledger Bevel, Hyperledger Fabric, Hyperledger Mentorship Program

What did you work on?

Project name: Upgrade Fabric network from 1.4.x to 2.2.x using Hyperledger Bevel

Objective:

Hyperledger Bevel is an automation framework for rapidly and consistently deploying production-ready DLT platforms. This mentorship project enhances Hyperledger Bevel to perform a live upgrade of a Hyperledger Fabric network from version 1.4.x to 2.2.x and provide an operations guide to perform the steps. This project uses Ansible, Kubernetes, Helm, Hashicorp Vault and Hyperledger Fabric. 

My mentors for this project were Sownak Roy and Jagpreet Singh Sasan. Their support and guidance has been immensely helpful for implementation of this project. 

This development work has automated the steps to upgrade the Hyperledger Fabric network, which shall increase the productivity to carry out such upgrades.

What did you learn or accomplish?

Learnings:

Before the start of this project, I had a basic understanding of setting up a Hyperledger Fabric network using Docker Compose. Hyperledger Bevel provided insights on how to automate and set up a production grade Hyperledger Fabric network on Kubernetes platform in various cloud providers.

I learned how Ansible, Helm charts and Flux are tied together for this implementation. Ansible does the automation for deployment pipeline, Helm charts are the reusable packages for Kubernetes components, and Flux implements the GitOps model so that current Hyperledger Fabric Network state is available for the operator.

Accomplishments:

My mentors validated my approach and provided feedback. I learned about multiple orderer organizations in a Hyperledger Fabric network and improved the upgrade automation for such scenarios. I was able to set up the network in a local minikube environment and will be updating the Hyperledger Bevel documentation for the same. This will provide new developers who do not have a cloud Kubernetes environment to set up and learn Hyperledger Bevel.

The code can be accessed here.

The documentation is available at this link.

What comes next?

I worked primarily on SharePoint development during my career but last year started looking into blockchain technologies as it provides immense potential to bring trust to the internet. There are so many use cases in real-life scenarios that ultimately can be solved by these technologies

The productivity that blockchain solutions bring to the table will be a win-win solution for enterprises as well as customers. This is an evolving technology that is community driven and, being open source, provides opportunity for all to learn and contribute. This mentorship program provided me a similar opportunity and now, along with Linux Foundation certification, my work is noticed by employers. I wholeheartedly thank my mentors and Linux Foundation for this opportunity and wish to keep contributing to this ecosystem.

Oct 05
Love0

Climate Action and Accounting Special Interest Group (CA2SIG) wins The Hyperledger Challenge 2022!

By Hyperledger Blog, Climate, Hyperledger Besu, Hyperledger Bevel, Hyperledger Cacti, Hyperledger Fabric, Special Interest Group

The Hyperledger Climate Action and Accounting Special Interest Group (CA2SIG) has just taken first place in the Hyperledger Challenge 2022 for its prototype for Reducing Methane Leakage and Flaring with Supply Chain Tokens. 

The Hyperledger Challenge 2022 took into careful consideration the following factors: 

1. Technology advancement and research objectives
2. Impact to the blockchain ecosystem
3. Value addition through social benefits
4. Process followed to build an open-source community around the proposed project
5. Activities outside the Hyperledger community to build the ecosystem
6. Bring in innovation in the marketplace
7. Headway into the community that is not represented well within the ecosystem.

This Hyperledger Challenge 2022 award follows the recent announcement of another award from IBM’s 2022 Call for Code Green Practices Accelerator, where the CA2SIG team also took first place for its prototype. 

“The team would like to thank the Hyperledger Challenge 2022 team for supporting our project. These recent wins/awards provide our team with added momentum and validation for the solution we are developing and the larger problem we seek to solve. Moving forward our focus is on marketing our solution to the energy industry and helping to scale auditing services, crucial to achieving climate targets by mid century. ” – Bertrand Rioux, Director, Two Ravens Energy & Climate Consulting

This prototype, which is built using Hyperledger Besu, Hyperledger Fabric, Hyperledger Bevel and Hyperledger Cactus, represents an important step towards creating an open climate accounting system that can be used to decarbonize corporate supply chains. By building a solution that can provide a free flow of trusted environmental data, we can create a more efficient marketplace that can unlock the power of green finance, consumer demand and government regulation to work together to decarbonize corporate supply chains. `

Click the CA2SIG One-Pager to learn more. We also invite you to visit the Climate Action and Accounting Wiki or join one of our bi-monthly meetings to learn about the different opportunities to get involved!

Apr 06
Love0

Call for Applications: 2022 Hyperledger Mentorship Program

By Hyperledger Blog, Hyperledger Aries, Hyperledger Besu, Hyperledger Bevel, Hyperledger Cacti, Hyperledger Fabric, Hyperledger Indy, Hyperledger Mentorship Program, Hyperledger Ursa

Want to jump start a career in blockchain development? Ready to build hands-on skills developing leading-edge open source technologies? Looking to work directly with mentors who are invested in you and your work? Then the Hyperledger Mentorship Program is for you. 

Now in its sixth year, the Hyperledger Mentorship Program provides a structured and guided learning opportunity for anyone, at any career stage, looking to get started in the open source movement. With full and part time options, fully remote work and a stipend, the projects are designed to be a pathway to becoming a contributor to the Hyperledger community that work for students, people in career transition and anyone else who wants to develop or sharpen their knowledge of cutting-edge blockchain technologies. Applications are now open.

This year, the Hyperledger Mentorship Program has grown to 30 planned part and full-time projects covering a range of technologies, challenges and technical difficulty levels and includes non-development projects such as Ecosystem Analysis and Developer Marketing. Each project is designed and proposed by active members of the Hyperledger community. Those who propose the projects serve as the mentors and work closely with their mentees on developing a project plan, setting milestones and solving problems. Mentees can expect regular evaluations and feedback. For more about the program, including the schedule and stipend details, go here.

Over the last five years, more than 70 mentees have completed Hyperledger Mentorship projects. Each of these mentees have made concrete contributions to Hyperledger projects and built important connections in the community. Some, like Bertrand Rioux, have gone on to become mentors themselves:

“I was accepted into the Hyperledger mentorship program last year after seeking a community to help advance my professional goals of developing software for climate action. I was fortunate to find a diverse group of mentors that helped me build the knowledge and skills I needed to effectively contribute to the Hyperledger open source community and to have the opportunity to develop technical expertise in a field I was actively working in. In addition to delivering a secure identity management solution for a Hyperledger Fabric Network, I started contributing my own ideas to the open source operating system for climate action. As a result, I am now taking a leadership role in the community. In addition to serving as mentor in this year’s program, I proposed a project on reducing waste emission in the oil & gas industry that was accepted.” – Bertrand Rioux, Independent Energy Consultant and Mentor for the Multiple Data Integration to Hyperledger Fabric Climate Accounting Network project

To learn more about the Hyperledger Mentorship experience and outcomes, check out these  spotlights on last year’s projects with highlights from both the mentors and mentees.

Read on for descriptions of some of the projects planned for this year:

Multiple Data Integration to Hyperledger Fabric Climate Accounting Network

The Hyperledger Labs blockchain-carbon-accounting project includes a Hyperledger Fabric network for recording the carbon and Greenhouse Gas (GHG) emissions that cause climate change.  Since there are many activities that cause such emissions, the network is designed to accept data from multiple sources of measurements.  In this project, we will demonstrate integrations from measurement sources with blockchain networks by integrating the ThoughtWorks cloud computing emissions calculator, the NREL OpenPath mobile application, and other web- and mobile-based API’s sources to turn instrumented readings into emissions measurements. It will leverage previous projects involving Hyperledger Cactus, Vault security engines, and client security for Hyperledger Fabric.

The expected outcomes of this project are

  • Successful integration of the mobile apps and API’s with Hyperledger Fabric
  • Benchmark comparison of Hyperledger Fabric and alternatives
  • Documentation and tutorials for integrating future data sources

Demonstrate Interoperability using Hyperledger Bevel and Cactus

Hyperledger Cactus support ledger Interoperability but use a local deployment for testing; Hyperledger Bevel supports production-worthy deployments. This project aims to support Cactus deployment using Bevel to demonstrate production-like usage of Hyperledger Cactus. 

The steps will be following:

  1. Deploy a Hyperledger Fabric network using Bevel on a Managed Kubernetes cluster
  2. Deploy a GoQuorum network using Bevel on a Managed Kubernetes cluster (can be the same cluster for simplicity).
  3. Make changes in Hyperledger Bevel code to deploy the Cactus connectors in both the above networks.
  4. Run Cactus test cases.

The expected outcomes of this project are

  • Successful Interoperability testing using Cactus on  production like DLT networks.
  • Update to Hyperledger Bevel code to automatically deploy the Cactus plugins.
  • Update to Documentation of Bevel and Cactus.
  • Detailed tutorials and learning materials which would benefit Bevel and Cactus communities.

Hyperledger Fabric-Ethereum token bridging

One of the key use cases of blockchain integration is asset bridging: in essence, “locking” an asset (typically, a native coin or token) in a smart contract on its authoritative ledger and making available corresponding, newly minted (wrapped/shadow/…) assets on another. By now, bridging is supported by quite mature solutions in the cryptoworld; however, the same is not true for “consortial” distributed ledger technologies. At the same time, such functionality can be expected to become an important requirement in the not too distant future: for instance, a central bank may choose to create a high performance, Hyperledger Fabric-based Central Bank Digital Currency (CBDC) ledger with a strongly controlled set of “smart contracts,” but allow controlled “bridging out” of the currency to dedicated distributed ledgers of industrial/enterprise cooperations. 

Last year, a CBDC prototype with such functionality was created at the Dept. of Measurement and Information Systems of the Budapest University of Technology and Economics (BME), in a research project supported by the central bank of Hungary (MNB); our initial experience with a custom Hyperledger Cactus and TokenBridge based solution showed that this is a problem worth more targeted experimentation and systematic R&D.

The expected outcomes of this project are

  • Report on asset representation in Hyperledger Fabric and mapping approaches to standard Ethereum tokens
  • Report on bridging approaches and technologies and their applicability for bridging from/to Fabric
  • Requirement specification
  • Design specification
  • Prototype implementation and small demo of bridging at least ERC-20 or ERC-721 to Ethereum – and back

Client Connector for Hyperledger Besu

Develop a connector that provides both synchronous and asynchronous modes of interacting with a running Hyperledger Besu node. The connector would act as an interface between an enterprise application and the Hyperledger Besu node for data ingestions and it could provide event subscription options.

The scope of the project would also include an end-to-end test on a sample network.

The expected outcomes of this project are

  • Design and implement the connector.
  • A new Hyperledger Labs project is proposed with a documentation.

GVCR: Secure Verifiable Credential Registries (VCR) for GitHub & GitLab

As conceptualized and standardized by the W3C, the Verifiable Credentials protocol is one of the three pillars of Self-Sovereign Identity, together with the Decentralized Identifiers protocol (DIDs) and Distributed Ledger Technology (or Blockchain). The project aims to design and build a verifiable credential registry (VCR) on GitHub repository, namely GitHub-based Verifiable Credential Registry (GVCR), by leveraging existing GitHub APIs, and other open-source tools provided by other Hyperledger projects, such as Hyperledger Aries, Hyperledger Indy, and Hyperledger Ursa. The basic architecture is already built. For more details about the conceptional design and workflows, please refer to the GitHub repository GitHub-VCR.

The expected outcomes of this project are

  • A verifiable credential registry based on one or more GitHub repositories.
  • Command-Line utility to automate the process of verification of a credential.
  • Proper test cases and documentation.
  • Codebase maintained with proper read me document.

The Hyperledger Summer Mentorship Program is part of the Linux Foundation’s overall commitment to mentoring. The application process is being managed through LFX Mentorship, a platform created by the Linux Foundations to train future open source leaders. 

Check out the full list of mentorship projects and start your application today. The deadline to apply is May 10. Mentees from diverse communities are encouraged to apply. All are welcome here!

Dec 13
Love0

Hello Hyperledger Bevel; bye-bye Blockchain Automation Framework, a Hyperledger Lab

By Sownak Roy, Hyperledger Bevel Maintainer, and Tracy Kuhrt, Hyperledger TSC Chair Blog, Hyperledger Bevel

We are excited to announce that Blockchain Automation Framework has been accepted as the latest Hyperledger® project and has been renamed (and rebranded) as Hyperledger Bevel™. The project is now formally being incubated as a top-level project in the Hyperledger Foundation™, hosted by the Linux Foundation, and has support from multiple sponsors. 

What a journey this has been! Even as a Hyperledger Lab, Hyperledger Bevel had significant interest and has often been quoted as a lab that is executed as a top-level project. Hyperledger Bevel has already been used to deploy many production and proof-of-concept DLT platforms and is also used to operate them. We are very excited that the acceptance as a top-level project will allow more interest and expand the community so that we can support new DLT platforms and add new operation features for existing platforms. 

What is Hyperledger Bevel? 

Hyperledger Bevel is an accelerator/tool that helps developers rapidly set up and deploy secure, scalable and production-ready DLT network(s) that also allows new organizations to be easily on-boarded on the network. Bevel accelerates DLT network deployment and lets developers focus on building blockchain applications without having to waste precious time standing up the environment or worrying whether the network will scale and meet production requirements. Bevel facilitates a safe and secure way of deploying and operating different DLT platforms. 

It includes: 

  • Helm charts to deploy different DLT nodes and to generate the related crypto/identities. 
  • Helm charts for various operational features like adding new nodes, and deploying smart contracts. 
  • Ansible playbooks and modular role definitions to automate the deployment of Helm charts. 
  • Integrated CD using GitOps so that once the network is set up, all changes can be done via git PRs/merges. 
  • Configuration for Ambassador Edge Stack and HAProxy (for Hyperledger Fabric) to act as Ingress Controller. 
  • Sample application that follows microservice architecture to enable developers with a blueprint for application development and deployment. 

It does not include cloud Infrastructure as Code; a working and accessible Kubernetes Cluster and Hashicorp Vault server are basic pre-requisites. 

How does it work? 

Hyperledger Bevel uses a single configuration file to deploy the DLT platform on a chosen cloud infrastructure. It consumes the single configuration file where we enlist all details such as the DLT platform of choice, cloud infrastructure of choice, network details, the node and application details, etc. to deploy a working distributed network. 

The architecture pattern is an implementation of DLT Reference Architecture, hence, conforming to best practices and providing a consistent way of deployment regardless of cloud provider and the underlying DLT platform. Thus, making it easy for developers to focus on application development.  

Diagram

Description automatically generated

 

Created by the open source Hyperledger Bevel community.

What’s Next? 

We are actively searching for potential contributors, maintainers, and partners who understand the value of Hyperledger Bevel and share the vision of building and owning well architected solutions. We welcome interest from all groups and organizations, including enterprises and standards organizations. The current roadmap is available at https://hyperledger-bevel.readthedocs.io/en/latest/roadmap.html.  

Want to Learn More? 

Check out Hyperledger Bevel source code and documentation. If you’re interested in learning more Hyperledger Bevel, consider visiting https://hyperledger.github.io/hyperledger-hip/HIPs/bevel.html or #bevel on Hyperledger chat at https://chat.hyperledger.org/channel/bevel.

Dec 15
Love1

Blockchain Automation Framework – the journey

By Michael Klein, Architecture Lead for Accenture Blockchain & Multiparty Systems, with contributions from Priyanka Vats, maintainer and project manager for Blockchain Automation Framework Blog, Hyperledger Bevel, Hyperledger Labs

In the early days and excitement of blockchain, we saw the proverbial ‘hammer looking for nail’ application of the technology across nearly every use case.  With a few years behind us, we now see a maturity in the understanding of the technology and the use cases it can best address. The ecosystem has evolved, and we even see live production implementations with enhanced understanding of where blockchain is the best solution to the problem vs. where it is an overkill.

However, it is not wrong to say that the adoption hasn’t been anywhere near to what was predicted. There are some clear barriers that have hindered the adoption of blockchain. Let’s bring the focus on our own technology journey and barriers in adoption from a technology lens that led us to conceptualize and then bring  Blockchain Automation Framework to Hyperledger Labs as an open source project.

Situation in 2018

In early 2018, we made a conscious decision to steer clear of the blockchain hype that filled news cycles and instead focus on development and architecture work. By this time, we had completed over 100 proof-of-concepts and pilots with customers, and the architecture challenges of security, scalability and performance had surfaced with these implementations. We had by then built a reference architecture that communicated the full suite of capabilities necessary for a full production scale implementation. We had also built deep knowledge in multiple platforms and implementing in mixed cloud and on-prem environments. But we knew we could do more to ensure consistency and speed for our customers. 

Disruption, the need for a change

The need was acutely apparent. Various teams across the globe pursued their own disparate ways of architecting and implementing, thus reinventing the wheel. Our team at Accenture had yet to become a collaborative ecosystem where we could learn from others’ mistakes or follow best practices uniformly.

We also saw multiple projects (inside and outside of Accenture) attempt to automate DLT deployments. The complexity around setting up a network, deploying it successfully and ensuring that network is up and running with all nodes communicating to each other seemed to be a challenge for the developer community. 

But each project within the blockchain ecosystem focused narrowly on their chosen DLT platform or cloud provider. Many focused only on quickly deploying development or proof-of-concept environments. Almost all wanted to commercialize their narrowly focused solution.

Outcome

We decided to start a project codenamed “Fulcrum” to simplify use of best practices and accelerate DLT deployments. Our vision was to bring down the technology barriers and thus drive adoption. From the very beginning we had open source in mind. 

We decided on some principles:

  • Design for security: Keys and other credentials are not stored in source, configuration files, environment variables, or filesystems
  • Modular Design: In order to provide an “enterprise” version, we should ensure that we are providing interfaces for modules where we might want to plug in a different component 
  • Conform to DLT Reference Architecture: When making decisions, conform to Accenture’s DLT Reference Architecture non-functional requirements and principles
  • Open Source Components: Ensure that we are using open source licensed products in our solution so that it may be contributed to Hyperledger, favoring Apache 2.0 licensed components
  • Infrastructure Independent: Choose tools and components that do not limit lock-in to an infrastructure configuration or cloud provider 
  • Choose Tools with Internal Expertise: Choose tools where Accenture has internal expertise to support and maintain

We then wrote down the problems we needed to solve while complying with the principles:

  1. How do we abstract the network complexities to let a developer majorly focus on application development? 
  2. How do we make it easy and consistent for the developers to deploy different blockchain networks? 
  3. How do we make it easy for the architects working on their first blockchain projects to design something secure, scalable, performing and easy to maintain?  
  4. How do we reduce the time taken in manual deployment from days to automated deployment in minutes?

Our customer conversations and Hyperledger community engagements helped us understand that these questions need to be answered not only at an organizational level but also at an industry/ecosystem level. For those familiar with building consortiums, it will be no surprise to hear that intellectual property concerns and fears of vendor lock-in can present major roadblocks in collaboration. Hence, we designed a solution that would not just accelerate adoption of the technology for Accenture customers, but would also be open source and accessible to all, simplifying  the deployment of the technology and accelerating adoption for the entire market. It was renamed to “Blockchain Automation framework” from its earlier name “Fulcrum” before it was open sourced. 

Now, as a Hyperledger Labs project, Blockchain Automation framework delivers automation for rapidly deploying production ready DLT platforms on a chosen cloud infrastructure. It consumes a single configuration file where we enlist all details such as the DLT platform of choice, cloud infra of choice, network details, the node details and application details etc. to deploy a working distributed network.

The architecture is basically an implementation of DLT reference architecture, hence conforming to best practices and providing a consistent mean to deploy regardless of cloud provider chosen, type of vault chosen and even the underlying DLT platform. Thus, making it easy for developers to focus on the application development. 

With multiple client implementations we have found out that it has on an average reduced 80% on the deployment time required through the automation. A single deployment that would take sometimes a couple of days can now be done in hours if not minutes, thus significantly accelerating the project implementation time.

What next?

There are many blockchain-as-a-service (BaaS) solutions available across the market, from the major cloud service providers, to well-known software companies, to a host of new startups. Many of the solutions have been limited to a single cloud provider and/or a single DLT platform, and we see many are crossing the bridge in supporting multiple DLT platforms and interoperating across many clouds. We share this vision of a thriving community of BaaS providers built upon standards and interoperable platforms. 

Unfortunately, that vision is not quite a reality in all places today, and we see the Blockchain Automation Framework as an excellent complement to the existing BaaS solutions, providing more deployment options across a multi-cloud landscape. This is just the beginning of the evolution of a project within the Hyperledger greenhouse that simplifies the accessibility of many multiparty system technologies and allows organizations to select the best platform for their specific needs, with the ability to change over time. 

We welcome all suggestions, contributions and collaborations to take Blockchain Automation Framework to the next level. To learn more about the lab, check out our previous blog for a tutorial overview. Ready to get started? Please visit our landing page on Wiki to get all the details on how to collaborate with us.

Copyright © 2022 The Linux Foundation®. All rights reserved. Hyperledger Foundation, Hyperledger, and the other Hyperledger Foundation trademarks are trademarks of The Linux Foundation. For a list of Hyperledger Foundation trademarks, please see our Trademark Usage page. Linux is a registered trademark of Linus Torvalds. Privacy Policy and Terms of Use.

Close Menu
  • Learn
    • Case Studies
    • White Papers
    • Training & Certification
    • Training Partners
    • Webinars
    • Research
    • Blockchain Showcase
    • Wiki
  • Use
    • Distributed Ledgers
    • Domain-Specific
    • Libraries
    • Tools
    • Tutorials
    • Hyperledger Certified Service Providers
    • Vendor Directory
  • Participate
    • Collaboration Tools
    • Contribute to Coding
    • Academic Collaboration
    • Find a Meetup
    • Regional Communities
    • Speakers Bureau
    • Join a Community Group
    • Labs
  • Events
  • News
    • Blog
    • Announcements
    • Newsletter
  • About
    • Join Hyperledger
    • Members
    • Leadership
    • Charter
    • Job Board
    • Contact Us
  • Join
  • English
    • 简体中文
    • Português
    • Français
    • Malayalam
    • 日本語
    • Español