Category

Hyperledger Composer

Consensus 2017 is a Wrap!

By Events, Finance, Healthcare, Hyperledger Burrow, Hyperledger Cello, Hyperledger Composer, Hyperledger Explorer, Hyperledger Fabric, Hyperledger Indy, Hyperledger Iroha, Hyperledger Sawtooth

The Hyperledger team (and 40 of our members!) spent a good amount of time in New York for CoinDesk’s annual Consensus conference last week. It was a great event with tons of excitement and enthusiasm around blockchain and its many applications. Attendees were from all walks of life – from developers to architects to financial services professionals to healthcare specialists to investors – all trying to better understand the best and most practical use cases of the technology.
The event kicked off the weekend before with the Building Blocks Hackathon at 30 Rockefeller where many of the world’s top blockchain developers vied to build the next killer smart contract app. Participants could build on top of any blockchain protocol: bitcoin, Ethereum, Hyperledger or otherwise. And through various sponsor challenges, they were encouraged to leverage the software and support made available by our world-class mentors in order to deliver projects.

Hyperledger was a sponsor of the event. The Hashed Health development team ended up winning the Hyperledger challenge, which was to create a game using any of the Hyperledger frameworks

(Winning team of the Hyperledger hackathon challenge and Hyperledger Executive Director, Brian Behlendorf)

Jonathan Levi, an active Hyperledger community member and the founder of HACERA, won 2 hackathon challenges using Hyperledger technology. They won the Enterprise Ethereum Alliance challenge and they were one of the winners of the Microsoft challenge. They called their solution Dutchess – a secure decentralized Chess on the blockchain that allows players to use ETH to pay for an unfair advantage in a sealed-bid Dutch auction. The entry highlighted Jonathan’s and HACERA’s approach of integrating multiple permissioned & public chains.

Dutchess incorporated:

  • Public Ethereum accounts used to transfer money to a sealed-bid Dutch auction
  • Confidential transactions using Solidity on Quorum, deployed on Microsoft Azure
  • A permissioned and public identity chain (Sovrin) for registering identity tokens
  • Hyperledger Indy for implementing secure verifiable claims
  • Hyperledger Sawtooth for transaction processing and validation

The result was a mini HACERA-like workflow that provided secure, auditable, privacy preserving, that prevents impersonation, relying on self-sovereign identity and offers a non-repudiation guarantee – with a playable fun game of Chess on a blockchain.

Early Monday, the Hyperledger team then set up shop on the 6th floor of the Marriott Marquis in Times Square. Crowds of attendees stopped by each day to learn more about the technology.  

 

At the booth several member companies gave demos on different Hyperledger projects including Hyperledger Fabric and Hyperledger Iroha. Cloudsoft demonstrated Deploying Hyperledger Fabric on Kubernetes with Cloudsoft AMP. IBM showed Connect a Cloud, connecting organizations together on Hyperledger Fabric using hosted cloud providers of choice. Soramitsu ran a KYC/user identity demo of Hyperledger Iroha/Android app and video, and Byacco, a local digital currency currently in use at University of Aizu in Fukushima, Japan. IntellectEU together with their customer Telindus (Proximus Group) explained streamlined asset transactions through reconciliation, matching and resolution among multiple parties.

Hyperledger also hosted a Roundtable on Monday on its distributed ledger technologies, Hyperledger Sawtooth and Hyperledger Iroha, each technology had end users speak to their different use cases. Kelly Olsen from Intel spoke to Sawtooth and his user, Pokitdok CTO, Ted Tanner weighed in on how they are utilizing Sawtooth in their healthcare blockchain solution. Makoto Takemiya, CEO, co-founder, Soramitsu discussed Hyperledger Iroha as a blockchain framework for mobile applications and Soichiro Takagi, from the Center for Global Communications (GLOCOM), International University of Japan shared his experience with the technology.

(Hyperledger roundtable participants: Makoto Takemiya, Soichiro Takagi, Kelly Olsen & Ted Tanner)

In addition to the robust line-up of Hyperledger activities in the main Consensus program and on the show floor, Hyperledger hosted a series of talks that ran all day Monday and Tuesday in the Hyperledger Mini Summit room. Attendees interested in how to best collaborate and get involved in the Hyperledger initiatives and learn where they can provide the most value had their bases covered in Monday’s “Meet the Hyperledger community” sessions. Speakers included the new technical staff, and diverse representation from the Technical Steering and Marketing committees, Governing Board, Identity Working Group and our fearless leader, Brian Behlendorf, Hyperledger’s executive director.

In Tuesday’s Hyperledger Mini Summit sessions, members dove a bit deeper into the impact of blockchain technologies on their businesses with field reports on how they are using Hyperledger to solve their business objectives. Attendees heard technical insights from Norbloc on the KYC process, IntellectEU together with their customer Telindus (Proximus Group) on streamlined asset transactions, as well as Cloudsoft on deploying and managing global blockchain networks.

Our members reinforced that blockchain is not only impacting business on a global scale, but also across industries through blockchain talks from Huawei on telecom, Daimler on the industrial enterprise, Deloitte on regulation, Energy Blockchain Labs on reversing China carbon emissions, and a panel of speakers from Accenture, BanQu and Leading Directions on blockchain for good applications.

Hyperledger hosted three different panels on Tuesday moderated by Executive Director, Brian Behlendorf and Security Maven, Dave Huseby. Those panels were “The Role of Open Source in Blockchain,” “Blockchain in the Wild, PoCs, Pilots & Deployments” and “Security, Privacy and the Enterprise Blockchain.”

(The Role of Open Source in Blockchain panelists: Dan Middleton, Intel, Casey Kuhlman, Monax, Makoto Takemiya, Soramitsu & Amber Baldet, J.P. Morgan)

 

(Blockchain in the Wild, PoCs, Pilots & Deployments panelists: Jesse Chenard, MonetaGo, Ashwin Kumar, Deutsche Boerse, Ram Komarraju, CLS Group, Corey Todaro, Hashed Health & David Treat, Accenture)

The panels were very well attended and there was great discussion on all three topics. It was most interesting that identity on the blockchain turned out to be the main topic of conversation during the security and privacy panel. And on that note, we’re excited with Hyperledger Indy just recently getting accepted into incubation under Hyperledger. Indy provides tools, libraries, and reusable components for providing digital identities rooted on blockchains.

(Security, Privacy and the Enterprise Blockchain panelists: Justin Newton, Netki, Drummond Reed, Sovrin Foundation, Jeff Garzik, Bloq & Astyanax Kanakakis, Norbloc)

We ended Consensus with a member party atop a NYC hotel rooftop. It was such a pleasure to see everyone and we are extremely grateful for all the support our community has provided around this event and overall. We’re looking forward to next year’s event – we hope that you can join us!
For those interested in additional information about Hyperledger technologies please reach out to: info@hyperledger.org. As always, we encourage developers to join our efforts via GitHub, Rocket.Chat the wiki or the mailing lists. You can also follow Hyperledger on Twitter.

Hyperledger’s Monthly Technical Update

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

As our incubated projects continue to mature, we’d like to update the community monthly on the progress we make. Below are May updates on Hyperledger projects.

Hyperledger Explorer

  • We are currently understanding the Node SDK provided by Hyperledger Fabric
  • Created basic project setup with front end using popular react.js framework
  • Added two new developers and are busy getting them up to speed on contributing to Hyperledger Explorer

Hyperledger Burrow

  • We moved and renamed former eris-db v0.16 into Hyperledger Burrow v0.16 (logistics) to initiate Hyperledger Burrow
    • We upgraded Tendermint v0.8.0 (Burrow v0.16) to Tendermint v0.9.2 (on develop Burrow v0.17)
    • Initial design work completed on user interaction with Hyperledger Burrow’s EVM from within Hyperledger family, specifically looking at Hyperledger Composer for UI/UX (replacing monax/legacy-contracts.js) and Hyperledger Indy for identity
  • Started collaboration with Hyperledger Sawtooth to use Hyperledger Burrow’s EVM as a transaction processor on the Hyperledger Sawtooth platform

Hyperledger Cello

  • Added new user-dashboard to support multi-tenant
  • K8s support has been discussed and will make documentation on jira
  • Hyperledger Fabric 1.0 support script are submitted
  • Summer intern students were trained to get familiar with the project

Hyperledger Composer

  • Made great progress with our move to Hyperledger:
    • Moved all source code and builds into GitHub and Travis CI under the Hyperledger organization
    • Moved the main website and documentation to https://hyperledger.github.io/composer
    • Substantial rebranding effort of main website, documentation, and playground
  • Delivered support for deploying Hyperledger Composer to Hyperledger Fabric v1.0 alpha:
    • New version of the getting started guide and related documentation
    • Continuing to keep in step with the latest Hyperledger Fabric v1.0 changes
  • Delivered connection profile and identity management support in the playground:
    • Use connection profiles to connect to Hyperledger Fabric v0.6 and v1.0.
    • Use identity management to switch between different Blockchain identities.
    • Removed and deprecated the old, superseded UI
  • Upgraded the Angular generator to generate Angular 4 applications.
  • Began work on being able to model, publish, and subscribe to business events.

Hyperledger Fabric

  • We agreed to a feature/code freeze at the Hackfest in DC, and selected co-release managers for the v1.0 release: Chris Ferris (IBM) and Jonathan Levi (Hacera).
  • At the hackfest, we also discussed and agreed on some changes to the development process proposed by Dave Huseby, which we will implement as a function of creating the release branch for v1.0.0-alpha2.
  • The TL;DR: of the proposal is that we will manage change through feature branches that will be merged into a development branch to undergo the full gauntlet of testing, and reverted if they still need work. Once the development branch has merged the set of features agreed for a release, the develop branch will be fast forward merged into the release branch (also the master branch), tested once more, and then published. The release/master branch which will always have the most recent stable release as the default on GitHub (as opposed to the head of development as is the case today).
  • Hyperledger Fabric added three new maintainers to help keep reviews up with the pace of change requests.
  • The rate of bug fixing has consistently outpaced reporting for the past 3 weeks, with in excess of 50 defects resolved per week.
  • The unit test coverage has seen steady improvement, now more than 70% (it had been 61%) with many key areas of the code at 100%. The integration test framework is taking shape and we expect to have regular testing (daily, performance/scale and long running) operational shortly.
  • Maintainers cut a v1.0.0-alpha2 release the week of May 8

Hyperledger Indy

  • Hyperledger Indy team is currently planning Jira migration from Sovrin to Hyperledger and working on configuration post-Jira Upgrade
  • Planning migration of code from Sovrin GitHub to Hyperledger GitHub
  • The team is identifying participants for Healthcare, Performance and Scaling WGs as well as collaborators for Hyperledger Burrow and Hyperledger Composer

Hyperledger Iroha

Hyperledger Sawtooth

  • Hyperledger Sawtooth graduated to Active status, announced at Consensus
  • Good hacking at the DC Hackfest, getting started integrating the Hyperledger Burrow EVM and Hyperledger Sawtooth.
  • On track for 0.8 feature complete (one condition for 1.0 release this summer).
    • Updated PoET to Hyperledger Sawtooth 0.8 architecture
    • Implemented PoET Z, C, & K admission policies
    • Threaded peering code
    • Added docker compose features and docs
    • Automated binary package and docker images
    • Improved serial scheduler to take advantage of new context manager functionality
    • Implemented client-side Javascript SDK (Transaction/Batch creation)
    • Implemented Go SDK
    • C++ SDK in progress

That’s it for the updates! We encourage developers to join our efforts on these projects. You can plug into the Hyperledger community at github, Rocket.Chat the wiki or our mailing list. You can also follow Hyperledger on Twitter or email us with any questions: info@hyperledger.org.

Happy coding!

 

Hyperledger Hyderabad Meetup Explores Blockchain’s Applicability to Healthcare

By Blog, Healthcare, Hyperledger Composer

Guest post: Sai Tejo Kiran E, Co-organizer, Hyperledger Hyderabad Meetup

The Hyperledger Hyderabad Meetup has been growing! Recently, we decided to have a combination of tech sessions and workshops combined with talks from meetup members who have implemented proof of concepts and built prototypes using Hyperledger. Blockchain is a revolutionary technology with the potential to disrupt the way things are currently functioning in many industries from financial services, to healthcare to technology. Specific to healthcare, blockchain has the potential to improve efficiency leading to massive cost reduction.

To give some perspective about the stakes at play for pharma companies, for every 10,000 molecules, just one of them becomes a drug. It takes about 10 years from the time a patent is awarded to the time the drug comes to the market. The process is marred by regulations, audit and compliance, data management etc. A patent is awarded for 20 years, so the scope for monetization is limited to about 8 years until it moves to the generics market and starts being sold it at low rates. So, in this context, if we can reduce the inefficiency in the go to market strategy and reduce the 12 years to 4-5 years, it is a big deal. Eventually it will lead to reduction in cost of the medicine.

A few weeks ago we had an Enterprise Architect from a major international pharma giant in Hyderabad give a talk pertaining to blockchain use cases in the healthcare sector. Below are specific use cases where the benefits of blockchain technology could help improve healthcare he discussed:

  1. Consent management

A patient could provide his medical history into the blockchain, enrich it with the EHR and make it accessible as and when required to the right stakeholders. Consent management using blockchain was a large topic at our last meetup. Enriching the EHR with personal health records from fitness devices/trackers and making it accessible to the doctors with the consent of the patient makes a case for better diagnosis of symptoms. Blockchain could give the control and meditation of data to the true actor, the owner of the data (patients in this case).

  1. Efficiency driving

Blockchain could be used for inter-organizational record keeping (audit and compliance) since a lot of data movement happens between regulators, manufacturers, regulators etc. Data can go stale since a copy is maintained independently by all the players. Tracking the integrity of the content is an important aspect.

  1. Data Integrity and Traceability

Imagine a clinical trial is going on and a patient is going to get some analysis done. The test data comes out as a lab report. Every lab report is maintained in a system managed by the pharma company. All the lab reports data is collated and is sent to the regulatory authorities to communicate the outcome. As part of audit and compliance, the authorities are not confident if the data is being tampered or not which might lead to mistrust. So the auditors visit the premises and validate the data. Blockchain could be a potential solution to improve this process. Every time a vital is collected and the data is taken can we create a hash and store it in the blockchain. Do this for all the patients. Share this with the authorities and send it with link to the hashes on the blockchain. If the data is being modified, then the hashes would not match which indicates discrepancy.

The other benefit which is an outcome of this process is that the data movement, access and ledger maintenance across lab Systems becomes smoother. This in turn will also lead to a process upgrade to the submission system for patent approval in addition to the Legal hold system on the data in case of disputes.

  1. Supply chain tracking of drugs

Blockchain based track and trace, improves provenance and traceability across the supply chain. Counterfeit medicine is a big issue pharma companies face in their everyday operations since there are many stakeholders involved in the supply chain. So the problem statement at hand is,“Can we track the medicine from the source to the destination, working with all the stakeholders using blockchain?” Recall of drugs and avoiding counterfeit drugs from entering into legit marketplaces will help in reducing the losses and improving service delivery to the end customer. Patient access programs also form a very important business proposition for pharma companies. Most of the companies conduct drives around vaccination programs and administer drugs free of cost. They are not running well due to lot of practical reasons involving multiple mediators. Blockchain could be used to maintain the entire supply chain in healthcare.

How is Hyperledger helping?

One of Hyperledger’s incubated projects, Hyperledger Composer, offers a set of APIs, a modeling language and a programming model to quickly define and deploy business networks and applications that allow participants to send transactions that exchange assets. It is more like an IDE tool like Eclipse, but specific to Hyperledger. It is useful for developers since they need to work with models and visuals and let the tool manage the underlying smart contracts and networks. Hyperledger Composer uses extensive, familiar and open development toolset. It is very useful for solution developers and looks at blockchain through three aspects:

  •         Participants – patients, doctors, insurance companies etc.
  •         Assets – patient data, stakeholder data etc.
  •         Transactions – Business rules which govern the exchange of assets

Conclusion

Blockchain technology has the potential to transform healthcare, placing the patient at the center of the healthcare ecosystem and increasing the privacy and interoperability of health data. This technology could provide a new model for health information exchanges (HIE) by making electronic medical records more secure by removing the need for multiple intermediaries.

With greater transparency, trust, and access to data, stakeholders can then also garner insights for better safety, effectiveness, quality, and security of drugs, vaccines, and medical devices. The promise of blockchain has widespread implications for stakeholders in the healthcare ecosystem. While it is not a solution for all the health care technology issues, this new, rapidly evolving field provides fertile ground for experimentation, investment, and proof-of-concept testing showing good promise in terms of impact.

For those interested particularly in healthcare and blockchain, please join the Hyperledger Healthcare Working Group here. You can also plug into the Hyperledger community at github, Rocket.Chat the wiki or our mailing list. Be sure to follow Hyperledger on Twitter or email us with any questions: info@hyperledger.org.

 

(5.3.17) SD Times: Hyperledger Composer accepted into incubation

By Hyperledger Composer, News

Hyperledger Composer, the collaboration tool for building “blockchain business networks,” has been accepted into incubation by the Technical Steering Committee at Hyperledger. Hyperledger is an open source blockchain technologies organization. The project would like to work on Composer with the community in order to develop it into a powerful and complete development framework.

More here.

(5.3.17) International Business Times: Hyperledger Project announces business blockchain Composer

By Hyperledger Composer, News

The Linux Foundation-affiliated Hyperledger Project, an open source provider of blockchain technologies, has placed its Hyperledger Composer into incubation by the group’s technical steering committee. Composer is a collaboration tool for building “blockchain business networks,” accelerating the development of smart contracts and their deployment across a distributed ledger, stated a blog post.

More here.

(5.3.17) CoinDesk: Hyperledger Adds ‘Indy’ and ‘Composer’ Blockchain Projects

By Hyperledger Composer, Hyperledger Indy, News

The Linux Foundation-backed Hyperledger blockchain project got a little bit bigger this week.

Yesterday, the group’s blog showcased Project Indy, which is focused on digital identity tools for blockchain ecosystems. Indy is being spearheaded by a group called the Sovrin Foundation, founded last year to provide solutions for decentralized identity.

More here.

Meet Hyperledger Composer

By Blog, Hyperledger Composer

Today, we’re proud to announce that Hyperledger Composer has been accepted into incubation by the Technical Steering Committee. Composer is a collaboration tool for building “blockchain business networks,” accelerating the development of smart contracts and their deployment across a distributed ledger.

All work done on Composer to date has been done on top of Hyperledger Fabric. However, Composer has been designed so that it can be ported to run on other distributed ledger technologies, such as Hyperledger Iroha or Hyperledger Sawtooth.

Why?

All “blockchain business networks” share certain elements  – namely assets, participants, identities, transactions, and registries. With existing blockchain or distributed ledger technologies, it can be difficult for organizations to take a blockchain business use case and map these concepts into running code. In the same way that the software world was accelerated by the arrival of software modelling tools, the primary goal of the Composer project is to accelerate the development of business networks built on blockchain technology.

Technical details of Composer

The main components are:

  • The modelling language; simple but expressive business-centric (the language features keywords such as asset and participant) language that allows non-developers and developers to model their business network. The modelling language also supports modelling of relationships and data validation rules.
  • The ability to encode business logic as transaction processor functions that are written in standard JavaScript. We chose JavaScript because it is a modern, rapidly evolving programming language that is used by millions of developers around the world, as well as giving us the ability to run the code anywhere that supports standard JavaScript.
  • Declarative access control using access control lists, that allows developers to describe what resources can be accessed by which participants. Access control is automatically enforced by the runtime.
  • Client and administrative APIs, as well as a “composer” CLI application that allows developers and operators to deploy and interact with business networks from Node.js applications or automation scripts.
  • A web based “playground” that allows new and experienced users to learn the language, model their business network, and test that network from the comfort of their web browser. The playground can work in both “disconnected” mode, using a simulated network, and when connected to real running network.
  • REST API support and integration capabilities; a LoopBack connector for business networks has been developed that exposes a running network as a REST API which can easily be consumed by client applications.
  • Syntax highlighting support for two popular open-source editors, Atom and VS Code, with future plans about how we could include testing/debugging capabilities.
  • Application generation using the Yeoman framework; client application developers can quickly generate a skeleton Angular 2 or CLI application to use as a starting point, allowing them to focus on UI/UX rather than business network interactions.

Who will work on Composer?

The initial maintainer community is comprised of Simon Stone, Daniel Selman and Kathryn Harrison of IBM, and Cong Tang and others from Oxchains. Of course everyone is encouraged to get involved, we want to see the contributor and maintainer community grow. There is a bi-weekly Hyperledger Composer community call. Please join the mailing list https://lists.hyperledger.org/mailman/listinfo/hyperledger-composer to receive notifications about Composer.

Getting started

Documentation for Composer, including a tutorial for first time users, is available from the public website: https://hyperledger.github.io/composer/

Composer is currently hosted under the Hyperledger organization on GitHub: https://github.com/hyperledger?q=composer. All of our work, both planned and in-progress, is managed using GitHub issues: https://github.com/hyperledger/composer/issues

The current list of repositories is:

  • composer – the majority of the code (including APIs, runtime, and UI)
  • composer-sample-networks – a collection of sample business network definitions
  • composer-sample-applications – a collection of sample applications
  • composer-sample-models – a collection of sample model files
  • composer-atom-plugin the plugin for the Atom editor
  • composer-vscode-plugin – the plugin for the VS Code editor
  • composer-tools – additional tools that are not part of the Composer “core”

The project was initially called “Fabric Composer”, and was renamed to simply “Composer” so as to encourage the other DLT framework efforts at Hyperledger to take a look and consider helping us implement support for them. However you will likely still see the terms “Fabric Composer” used in the documentation and source code until we get around to cleaning that up.

The majority of the Composer source code is JavaScript, and can be built and tested using the standard npm toolchain (“npm install” and “npm test”). We have aimed to use standard JavaScript tools as part of our development process: npm, Mocha (test driver), Chai (test assertions), Sinon (mocks), Istanbul (code coverage), etc.

What’s next?

By working with the community, we would like to continue to develop Composer to be a powerful and complete development framework that allows users to easily and rapidly build blockchain business networks.

Future work that the community is currently considering includes:

  • First class support for events; being able to model the structure of events, being able to publish events from a blockchain and allowing client applications to subscribe to and receive those events.
  • Links between multiple running business networks; for example, allowing one network to reference assets that are stored in another network.
  • Complex and historical query support, to allow powerful queries over assets, participants, and transactions and the relationships between those resources that have been recorded.
  • Investigate adding support for Iroha and Sawtooth Lake. Composer already includes a pluggable adapter layer that makes this possible. The majority of the Composer codebase is runtime agnostic. The runtime specific code is restricted to the connector implementations (client to blockchain) and the runtime container implementations (blockchain to common runtime).
  • Automatic, formal verification of Composer business logic. The smart contracts generated by Composer would be analyzed against the user-specified requirements written in the modelling language. The verification tool would output a statement that the smart contract is correct, or it would output a counterexample, explaining some way in which the smart contract does not meet its specification.

For those interested in additional information about Composer or any of the other frameworks or modules under Hyperledger, please reach out to: info@hyperledger.org. As always, we encourage developers to join our efforts via GitHub, Rocket.Chat the wiki or the mailing lists. You can also follow Hyperledger on Twitter.