Category

Blog

[VIDEO] Hyperledger Interviews Ozgur Akdeniz, ANZ Bank

By | Blog

We spoke with Ozgur Akdeniz, Head of Transaction Banking at ANZ. By being an active member in the Hyperledger community, ANZ is ensuring that Hyperledger has the best chance at developing an underlying code base that is fit for enterprise use. ANZ believes the Hyperledger community will produce the platform technologies of choice for the finance industry in the future.

ANZ has used Hyperledger Fabric for a successful nostro reconciliation POC with Wells Fargo. According to Ozgur, being able to leverage the expertise within the Hyperledger community and problem solve issues as they arise in POCs gives ANZ the ability to move faster, and continue to experiment and learn about this new tech to deliver business value. ANZ is focused on two areas with distributed ledger tech: expanding  their nostro reconciliation POC with Wells Fargo in terms of scope and number of participating banks. They also want to expand use cases because most have been focused on internal issues to date but they want to tackle external issues with trade guarantees, trade finance etc.

Watch the full interview:

You can visit this page to watch all the videos in this member video testimonial series, as well as follow us on YouTube.

Blockchain-based digital identity: How Hyperledger is helping to turn hype into reality

By | Blog, Hyperledger Fabric

Guest post: Andre Boysen, Chief Identity Officer, SecureKey Technologies

Identity has never been easy, but it’s particularly tricky in the digital age. For too long we’ve been forced to use outdated processes to prove who we are when we’re trying to get things done. It shouldn’t take a half-day off work and a trip to a government office to renew a passport, or an entire evening to update a smartphone plan, yet we’re being forced to do so because companies need controls to prove we are who we say we are and the gold standard for doing this today is a counter visit.

Thanks to blockchain, that’s changing. Distributed ledger technology is giving us the opportunity to do what we haven’t been able to do so far – prove with greater certainty that you are you, to immediately access the services you want online, in person or on the phone. Utilizing this approach, we can develop a digital identity and attribute sharing network designed to allow consumers to use digital credentials they already have with organizations they already trust (like their banks), and verify their identity quickly to access services from trusted institutions (like telcos, government services, even sharing economy companies) instantly and with certainty. No more need to create another username and password combination that will be easily forgotten, or dedicate hours on end to perform a simple task, like updating a driver’s license, setting up a new phone or checking your credit score.

SecureKey changed consumer single-sign-on for the better when we introduced the concept of triple-blind authentication with SecureKey Concierge. The simple idea was that using a single credential could actually increase privacy, because none of the transaction participants got a complete picture of the user’s transaction. The bank does not see your online destination, the government does not see which bank you used or your account details and SecureKey does not know who you are. The challenge for us when we moved beyond accessing services to registering for new ones was how to implement the triple-blind model for identity information.

While it was technically possible to do this with public key infrastructure (PKI), there were some difficulties. For example, if the receiver had to check the signature on the data for verification, the blinding broke. A possible solution to this was the introduction of a key exchange that effectively blinded the receiver. However, this created a fourth factor in the transaction system, which increased complexity and made it much harder to trace a transaction in the event of a compromised account.

Enter blockchain. The advent of this technology adds some key capabilities and allows us to solve our service registration challenges.  Among its many benefits, blockchain  allows us to implement triple-blind attributes, data signing for service integrity and resiliency to mitigate against a single point of failure.

The benefit goes beyond the individual citizen to the businesses they choose to use. In an age where everything is hackable and millions of customer records are stolen or dumped online every month, organizations are realizing that one of their most toxic assets can often be customer records. Organizations that can confidently verify the identity of their customers quickly without the need to store that customer’s data on their own networks experience a twofold benefit: not only is there a real world cost savings for their IT infrastructure, but there is also a massively reduced risk of being financially accountable in the event that bad actors attempt to steal their customer data, namely because the data never needs to reside on their servers in the first place. This greatly reduces the risk of customer data becoming toxic and negatively impacting a company following a breach or leak – something we’re seeing become much more frequent each and every month.  

We’re still in the early days of blockchain, but through communities like Hyperledger Fabric, hosted by The Linux Foundation, we’re seeing how its applicability can be endless. From currency to identity and further afield, blockchain is moving quickly beyond the buzzword stage and becoming critical to the evolution of services in the digital age.  There is a lot of blockchain hype to be sure, but for identity blockchain is going to be really helpful.

Developer Showcase Series: Aram Barnett, Vergo

By | Blog, Hyperledger Composer, Hyperledger Fabric

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 Aram Barnett, Blockchain Engineer and Managing Partner at Vergo.

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

First, identify why you need blockchain. With all the hype surrounding the technology, it’s easy to think you can capitalize on the hype by sprinkling some blockchain into your app. Without a well-defined plan on how and why you are going to apply it, you are simply wasting your time and money.

Second, I want anyone interested in the technology to commit to learning about the details surrounding the progress blockchain has made rather than just the media hype that surrounds it. According to Gartner Hype Cycle, blockchain is at the peak of the technology hype cycle, and soon blockchain will be transitioning into the “trough of disillusion” where people outside of the development community will think that all of the promises of blockchain are not possible. However, unlike many new technologies on the hype cycle, blockchain will quickly escape the trough of disillusionment and grow exponentially when businesses realize the value of private ledgers. It’s is not easy but with enough dedication and a thorough understanding of the fundamentals, a developer can contribute to the blockchain community and create world changing applications. Third, get familiar Go and Javascript.

Hyperledger Composer, the tool that we use to rapidly build and test business networks, uses Javascript to enable the creation of business actions. Once you dive in the technology, be mindful of the difference between permissioned versus non-permissioned ledgers (a.k.a. public versus private blockchains, respectively) and what they offer. We will soon be releasing our own teaching resources for developers get up to speed on Hyperledger and the best practices on developing blockchain based business networks.

Aram Barnett, Blockchain Engineer and Managing Partner, Vergo

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?

I first heard about blockchain when I purchased my first bitcoin in 2011. I was so infatuated with bitcoin I dedicated 3 years of my life to running an alternative asset management fund that exclusively traded cryptocurrencies, learning everything I could about bitcoin and blockchain. I always knew that the real value of bitcoin came from the blockchain and in 2015 I began focusing all of my efforts on developing smart contracts on ethereum and coming up with business use cases.

I am currently working on Vergo, a company I co-founded to create blockchain-based business networks for open source and enterprise use.We’re working to make existing corporations more efficient by cutting excess expense associated with business transactions. To further support this community, we are open-sourcing some of our business logic to help other developers learn about this unique technology. We believe that this technology will allow developers to create turnkey businesses in which open-source business logic is easily deployable. This will increase access to entrepreneurship around the globe and empower people to start their own businesses.

More importantly, we believe we have the ethical responsibility to help transition the world to this new era in a responsible manner in which participants understand the consequences of enhanced business network efficiency and automation. We strive to ride the new wave of technological innovation by giving equal attention to corporate efficiency and social well-being.

If you look at  the Gartner Hype Cycle, mentioned earlier, blockchain is at the peak of public hype about its potential. This new wave of technology is scary to some and at peak hype it can seem like anything is possible. I made the choice to ride the blockchain wave. Since I first got involved with bitcoin and subsequently blockchain in 2011, I knew that it would be a promising technology that needs to be developed and implemented globally. We are currently at peak hype, so public interest will decline in the next few years. However, the underlying technology will still be revolutionary and over time the corporate sector will realize how truly valuable it is to their networks.

As Hyperledger’s incubated projects start maturing and hit 1.0s and beyond, what are the most interesting technologies, apps, or use cases coming out as a result from your perspective?

The most interesting project to come out of is Hyperledger Fabric. We are excited about the progress of Fabric 1.0 and what it has to offer to large and medium enterprises. I met with the lead developers at the Hyperledger hackfest in Washington DC to learn more about Fabric and help contribute to the project. Vergo is very interested in this because we see the long-term impact that Fabric will have on how companies deploy blockchain solutions. We are very excited to be building applications and business logic on top of the Fabric ledger that these talented developers have built. We are currently discussing the possibility of cooperation between Vergo and some IBMers to display our business applications running on the IBM z mainframe. Another exciting application called Hyperledger Composer, the application we use to model, build, and test our business networks very quickly using their  business development language. After speaking with  Simon Stone, one of the maintainers of Hyperledger Composer, we are very excited for the future of Composer as a development tool and the services they plan to integrate into it.

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

Blockchain has the ability to solve a lot of problems. The ability to capture the nature of “businesses” and their “workers” and digitizing those relationships could lead to efficiency increases across almost every industry.

I think what I am most interested in, in regards to public-facing blockchain solutions, is the possibility of interoperability between chains and the assignment of an identity to every person. For instance, imagine from the very day you are born you were assigned a bank account, a verified identity and trackable health records all stored on a government ledger. From here, your financials, health records, and identity would be immutable and secure and would follow you over the course of your life. The interoperability between your identity and your financial records, for example, would verify you exist while not disclosing your personal data every time you make a transaction. By solving the problem of identity, many other possible solutions arise.

Where do you hope to see Hyperledger and/or blockchain in 5 years?

Let me answer your question with another question: Where do I not see it?

Blockchain-based business networks are inevitable. I think there will be varied solutions for individual businesses and sectors that provide accessible solutions to problems associated with the analysis of big data and efficiency of transactions. Blockchain will be easier to collect and analyze data, which will enhance our understanding of business practices and markets.

Additionally, I hope that turnkey businesses will emerge across the world using open source logic developed out of the Hyperledger framework. The ability to replicate businesses with extreme ease will increase access to opportunities for economically disadvantaged peoples. I hope that the pool of open source logic is such that it allows anyone with enough emotional intelligence and work-ethic to provide a valuable product to a customer even without understanding underlying business logic.

[VIDEO] Hyperledger Interviews Ram Komarraju, CLS Bank

By | Blog, Hyperledger Fabric

We spoke with Ram Komarraju, Chief Architect at CLS Bank. CLS Bank is a founding member of Hyperledger. Having an open source initiative that is industry wide like Hyperledger is vital to the adoption and success of distributed ledger technology (DLT), according to Ram.

CLS Bank’s major focus is to work with the Hyperledger community to make sure the design of Hyperledger Fabric meets the requirements and needs of the enterprise including resiliency, security and scale. Ram believes a key value of being a part of Hyperledger is building an open source DLT solution that is accepted across industries for a wide variety of use cases including financial services and others.

Watch the full interview:

Winning HyperProperty Project at Consensus 2017 Uses Hyperledger Fabric as Banker and Deed Manager

By | Blog, Hyperledger Fabric

Blockchain enthusiasts from around the world recently attended the Consensus 2017: Building Blocks Hackathon where sponsors issued hackathon challenges to competing teams. Hyperledger issued the challenge to “implement any board game as a blockchain app with one or more Hyperledger projects.”

The winning team: HyperProperty

HyperProperty by De’on Summers, Zhenting Zhou, and Kyle Tut won the Hyperledger challenge with an online property acquisition and banking game utilizing Hyperledger Fabric and deployed with IBM’s Bluemix. The project provides a fantastic example for how Hyperledger technology can facilitate transactions without a middleman.

Pictured left to right: De’on Summers, Brian Behlendorf, Zhenting Zhou, and Kyle Tut

 

The HyperProperty team had the perfect combination of back-end, front-end, and prototyping experience. De’on Summers built the backend and chaincode for HyperProperty. De’on is a blockchain developer from Nashville, TN at Hashed Health. Zhenting Zhou built the front-end interface for HyperProperty. Zhenting is a front-end developer from NYC that became interested in blockchain technology through cryptocurrency. The team also leveraged prototyping expertise from Kyle Tut who is the founder of Kyna, a blockchain patent exchange increasing the liquidity of global innovation. Kyle has previously spent time building IoT blockchain prototypes for logistical applications.

The team’s design goals

The HyperProperty team chose to apply blockchain technology to the game of Monopoly because it provides a good representation of economics, properties, and financial systems. Since everyone already knows the rules of Monopoly, the team felt confident that they could showcase the gameplay with Hyperledger Fabric — ensuring players can’t cheat on dice rolls and tracking board moves, banking transactions, and property purchases on the ledger.

The game of HyperProperty

The architecture of HyperProperty consists of three types of objects:

  1. Properties
  2. Players, which contain each property that the player owns and the player’s account balance
  3. The game board, which consists of all properties and each player’s position

The game demonstrates a tokenized economy because each property exists as a token on Hyperledger Fabric. When a player buys a property, the token for that property gets assigned to the player and his or her account balance goes down.

Coding the game involved taking the initial game of Monopoly and using Hyperledger Fabric to create a trustless, immutable environment so that players don’t have to worry about cheating or the bank paying someone under the table.

The game works by writing four types of events to the ledger:

  1. Game start
  2. Dice roll
  3. Buy property
  4. Pass

At the start of a game, a new board is written to the ledger with all the initial data about properties and players. It’s a clear slate. When a player rolls the dice, a request goes to the backend for the dice to be rolled and the outcome of the dice roll is written to the ledger. This includes an update with the player’s new position. When a player buys a property or passes, the state of the board is updated again with anything that has changed such as the properties that the player owns, the player’s new account balance, and whose turn it is.

The gameplay for HyperProperty is really simple because Hyperledger Fabric acts as the banker and deed manager. The game begins when player 1 aka “MoneyDude” and player 2 aka “Doge” show up to the game. Player 1 rolls the dice. Player 1 can then decide to either buy the property or pass. Once player 1’s turn is over, player 2 rolls the dice. This process is repeated until someone goes bankrupt. Throughout the game, each player’s cash on hand is automatically tracked and written to the ledger.

Next steps for facilitating transactions with Hyperledger Fabric

Lessons from the HyperProperty project can be applied to any tokenized economy where assets are represented by tokens on a blockchain. The project shows that Hyperledger Fabric can be used to guarantee who owns what properties, which is perfect for things like land registration. When assets need to be traded, the participants in the trade can exchange value for the token and accomplish transactions without a middleman. This has the potential to facilitate more efficient and less costly transactions for a lot of things in the real world, including real estate transactions.

If you’re looking to facilitate transactions with Hyperledger Fabric, be sure to play the HyperProperty game at https://peaceful-lake-75705.herokuapp.com/ and get the code from GitHub at https://github.com/Dsummers91/HyperProperty-server and https://github.com/zhenpanda/hyperledger_property_app.

Techno-Legal Standards Are Needed for Smart Contracts

By | Blog

Guest post: Houman Shadab, Co-Founder, Clause.io

As the potential benefits of blockchain-based “smart contracts” become widely understood, a lingering question remains: how will they gain widespread adoption?

In the past, fundamental changes to the technical and legal aspects of markets were adopted  not just by market forces but also by overt cooperation and coordination to develop standards. For example, in 1947 the International Organization for Standardization formed and since then has become a universally recognized source for providing standards that drive quality assurances and harmonization across a wide range of industries and business practices. Likewise, the International Swaps and Derivatives Association in the 1980s catalyzed the global market for financial derivatives by establishing standards for contract structures important practices such as risk management — which would be all but impossible without the standards.

In technology, standardization is one of the many benefits and drivers of open source software development, which proceeds by using widely shared code that serves as the basis for developers to build on and ultimately customize. As digital transformation increases the need for businesses to interconnect their systems, the value proposition of open source becomes all the greater.

In the world of legal contracts, the structure of modern, commercial agreements has come to be relatively standardized. Commercial contracts usually consist of recitals, definitions, the exchange of value, representations and warranties, conditions and ancillary obligations, and boilerplate clauses such as indemnification and choice of law. Businesses around the world benefit from this implicit consensus on structure. But drill down deeper into contracts used even within the same industry and one will find a plethora of specific approaches. This lack of uniformity causes persistent problems and inefficiencies in business, and has spurred several initiatives to develop contract standards.

All of which brings us back to smart contracts. In order to realize the potential benefits of legally binding contracts that use blockchain technology, widespread agreement must reached on a far greater range of issues than required to overcome the costs of proprietary approaches with traditional contracts. These issues range from foundational ones, including the usage of templates and the proper interface for legally binding text, to issues unique to smart contracts, including the suitability of data to confirm contract obligations to security, storage, and execution with a blockchain.

Without standards, smart contracts may improve businesses, but they won’t transform them.

The need for standards and open source tools to usher in a change to the nature of legal contracts and business relationships is why we at Clause (www.clause.io) are launching the Accord Project. Accord will not only develop consensus on smart legal contract structures and associated technical issues, however. It will also establish a set of open source software development tools, which will be proposed to the TSC as new projects at Hyperledger, so that a broad community of developers and users will be able to collaborate directly on the future of contracting.

If you are interested in learning more about the Accord Project, please get in touch at: admin@accordproject.org. Or if you’d like to contribute, our code will be hosted at https://github.com/accordproject.

 

[VIDEO] Hyperledger Interviews Chris Ferris, CTO Open Technology, IBM

By | Blog, Hyperledger Fabric

We spoke with Chris Ferris, Chair of Hyperledger’s Technical Steering Committee, and CTO of Open Technology at IBM.

Blockchain is already changing how IBM does business with its Global Finance System. It is a $4B system and at any time about $100M is in dispute but IBM has reduced that down to $40M by applying blockchain technology.

According to Chris, blockchain will help drive process improvement for their customers’ business interactions, and could have meaningful change in how those processes actually work. The collaboration IBM gets in Hyperledger’s very diverse community is the biggest advantage. It’s not just technologists, there’s leaders from finance, supply chain, automotive, and even aerospace. Chris believes it’s the diversity of thought, technologies and use cases that are the best aspect of participating in Hyperledger.

You can watch the full interview here:

Developer Showcase Series: Vipin Bharathan, BNP Paribas

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 Vipin Bharathan, Blockchain Strategist for BNP Paribas. Here’s what he had to say about working on blockchain and Hyperledger:

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?

I had been leading a small team developing front office applications for Fixed Income Products in a major financial institution for some years. The work was technical, but it needed expertise in social and political aspects of the enterprise as well. We had to deliver solutions to highly demanding internal clients in a high risk environment. We, the developers, were communicating directly with the clients and had an agile program in place that turned around solutions in a highly iterative way. Although we could engineer our solution to be highly reactive using a distributed data fabric, we found that the interactions that we had with other enterprise systems severely constrained our capabilities and made our software appear brittle and incomplete.

Our front facing systems had to cope with temporal, service level and quality mismatches between electronic trading systems, reference data, pricing and other internal services. Recognizing the integrated nature of the systems, we relied on two or three simple concepts like autonomous systems, traceability and decoupling to improve matters. We also proposed a high level design for a bus that held both data and code and had simple interface contracts that would bridge the services and increases the integration and resilience; keeping the systems loosely coupled. This was an abstract design, but resources were not available for such an ambitious project, especially since it broke horizontally through silos.  Enter the blockchain!

It was around this time that I read about bitcoin, purely as a crypto-currency; intrigued, I read the initial bitcoin paper by Satoshi Nakamoto. I had also been attracted to bitcoin because of my work in cryptography harking back to the eighties and nineties. At first, the solution for our dilemma was not visible in the bitcoin framework. Further reading helped me understand the direction taken by Blockchain, soon to be christened DLT (Distributed Ledger Technology) and the work being done in R3, Hyperledger and other consortia. I attended the first calls of the Hyperledger TSC and attended the R3 steerco. Listening to the many talks, reading papers, going to meetups, meeting and talking to the many devotees of the technology, I was convinced that adoption of Blockchain Technology could help solve the fragmented landscape of Financial Enterprise software. I also saw that this would not happen in a short period of time, it would take implementations in the real world for the ideas to get shaken out, for hardened solutions to emerge. This is a sociotechnical effort, to be addressed on both those fronts, so evangelization was necessary.

I created an internal techno-social blog focused on chronicling of the fast developing space. I also made some presentations; first to technical audiences and soon to broader audiences. Within about a year, I was offered a different role in our organization; to function as a Blockchain Strategist and Coordinator for North Americas. I see my job as that of a catalyst, a translator, and a bridge; between the past and the future; business and technology, external entities and the organization, ideation and execution especially in the Blockchain space.

Vipin Bharathan, Blockchain Strategist at BNP Paribas

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

Blockchain is a generic solution; a way to mutualize the source of truth. The truth could be about currency, the truth could be about Assets: registration, issuance and exchange. The setting could be completely trustless or semi trusted. This opens up varied use cases; this is evident from reading about the efforts by startups, established enterprises and consortia. If I said Blockchain would solve world hunger, measure dark matter & energy, effect nuclear fusion or make immortality possible that would be a stretch, but aside from these, the possibilities in the transaction space are many.

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

Hyperledger as an umbrella and a community needs to focus on providing an environment to experiment, to measure, to fail, to get input from a wide variety of folks , to improve and to execute securely on the DLT frameworks. In the short term, we seem to be agreeing to focus on building standards around composable components. We are also working on Identity and other foundational concepts and generalizing these.  The other area we can collaborate on is providing tooling for development, testing, measurement, deployment and monitoring. We have a choice group of DLTs incubated and developing under the Hyperledger. Pressure is also on to move from PoCs to MVPs and beyond in many enterprises. In the next year we must focus on improving and polishing the DLTs we incubate, as well as influencing and learning from publicly available data on other open-source DLTs.

Where do you hope to see Hyperledger and/or blockchain in 5 years?

Hyperledger continues to grow in membership. Charters for most working groups have been written. In the short term, the next year or so, we will produce White Papers specific to each Working Group. This will move towards the creation of Standards for Interaction and the possibility for composability. This could bring about a situation in which users can easily create a bespoke solution to their use case by mixing and matching components from different implementations of DLT. The broad community in Hyperledger can also help build tools and other peripherals around adoption in multiple industries.

In the five year horizon, we hope to see several production systems in play. Techniques for Interoperation in the cross-self (across hard forks), cross-chain and cross-over (legacy systems) will improve. The confluence of practices in Big Data and RPA (Robotics Process Automation) under the Blockchain umbrella is inevitable. This is because the Blockhain could have access to huge quantities of Transaction and other Data, Smart Contracts would enable analytics and automation on top of this data. These currents coupled with TEE (Trusted Execution Environment) will strengthen the cryptographic guarantees around attestation and processes. Privacy around activities and side channel revelations are another area that will be improved.

The current work on DLTs reveals that this is not a magic bullet. Lots of effort will be needed to incubate and foster DLTs in the Enterprise. Inevitably, somewhere in five years, the hype-cycle would be in its downward slope before mass adoption. It would be necessary to keep the eyes on a longer timeframe not to be disenchanted.

There could also be public and costly failures; we have to be ready to learn from them, design now to limit their damage, to adapt and to move forward.

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

Read and understand Satoshi Nakamoto’s bitcoin paper, the founding document of the Blockchain. Familiarize yourselves with the federated DLT environment and the difference with the public, trustless, peer-to-peer public Blockchains like Ethereum and Bitcoin. Get yourself some new grounding in distributed computing, cryptography, data stores and other important components of the ecosystem. Even if you are familiar with some of these concepts; there are some nuances in the context of Blockchain which will require changes in your mental models. Get ready for lots of discussions with Bitcoin maximalists and Enterprise skeptics.

There are many free online courses from Coursera, Udacity and EdEx specific to cryptography, bitcoin and DLT technology. In terms of smart contract programming; most permissioned platforms use languages similar to JavaScript or Java and in the case of bitcoin, Forth. The most important idea here would be to create systems that are resilient as the data is immutable. Revive your interest in Functional Programming as some platforms embrace Haskell or its variants to implement strong guarantees of halting and determinism. In addition to seeing where DLT could be used, it is necessary to see what should not be solved by DLT, this requires a critical assessment of the suggested use cases.  It is a rewarding journey, and we are just starting out on it.

 

 

Hyperledger Fabric 1.0 is Released!

By | Blog, Hyperledger Fabric

Chris Ferris, Chair of Hyperledger Technical Steering Committee, CTO Open Technology, IBM and Jonathan Levi, nominated release manager of Hyperledger Fabric 1.0, creator of HACERA

Today, we are pleased to announce Hyperledger Fabric 1.0.0 is now available! But what does the 1.0 designation really mean?

This is a huge milestone for the community. 159 engineers from 27 organizations contributed to Hyperledger Fabric and 57 engineers, writers and testers contributed to the post-beta cleanup effort. It is amazing to see what this highly collaborative community with more than 145 members has achieved in a little over a year. Just 16 months ago, Hyperledger Fabric became the first of the now eight Hyperledger projects to be incubated. Hyperledger Fabric was also the first of the Hyperledger projects to exit incubation to “Active” status in March, after a year in incubation.

The efforts around Hyperledger Fabric have grown into a true, vibrant community including engineers from: Arxan, Cloudsoft,  CLS, d20 Technical Services, The Depository Trust & Clearing Corporation (DTCC), Digital Asset, Fujitsu, GE, Gemalto, HACERA, Hitachi, Huawei Technologies, Hyperchain, ImpactChoice,  IT People, Knoldus, The Linux Foundation, Netease, Passkit, State Street Bank, SecureKey, IBM, SAP, Thoughtworks and Wanda Group. There were also contributions from 35 unaffiliated individuals. In total, 159 developers have contributed to Hyperledger Fabric.

Along the way, we published two developer preview releases, and we learned a lot from the feedback from the many users developing proofs of concept/technology built using those releases. With that important feedback, we undertook a significant refactoring of the architecture and re-wrote much of the code, as you can see with the visualization of the commit history.

No open source project is ever “done,” and the same can be said for Hyperledger Fabric. There’s much that we want to do, including improve delivery of a Byzantine Fault Tolerant orderer capability, explore integration with other Hyperledger projects such as Sawtooth, Iroha, Indy and Burrow, add support for Java and other chaincode development languages, deliver additional SDKs for Go and Python, provide a recipe(s) for deployment to Kubernetes, deliver proper installers for the various development platforms, and much, much more.

We also have more work to do on performance and of course we have plans to add more comprehensive performance, scale and chaotic testing to our continuous integration pipeline to continue to add to the robustness of the platform.

However, the project’s maintainers felt that the time was ripe to deliver a robust initial major release with the objective of allowing consumers and vendors of technology based on Hyperledger Fabric to advance to the next stage: production deployment and operations.

Over the past two months, we locked down feature development and focused on static and dynamic security scanning and linting, testing, reducing technical debt and fixing defects. We increased the unit test coverage by 70% and continue to automate our manual SVT integration tests. We have honed our release process by releasing four interim releases (alpha, alpha2, beta, and rc1) and with each, we have been taking user feedback and worked to improve our documentation and initial UX.

So, is it soup yet? We think so, and we’d love for you to give Hyperledger Fabric 1.0 a try. Are we done? Not at all. There’s still much to be done on the journey to delivering on the promise of blockchain in the enterprise. However, to drive the continuous improvement, we need your feedback. Why not join us on this exciting journey to transform how the industry thinks about business network transactions!

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.

Hyperledger’s Monthly Technical Update

By | Blog, Hyperledger Burrow, 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 June updates on Hyperledger projects.

Hyperledger Burrow

  • Implementation of dynamic memory on the Ethereum Virtual Machine
  • New type-safe Application Binary Interface package for translating data to Ethereum contracts into packed Ethereum bytes for transaction formulation (logical requirement for Ethereum chain; but all package implementations thus far have been GPLv3 licensed, as such in tooling code not included in Burrow; this new package will be able to go into Hyperledger Burrow under Apache license)
  • Alpha of batching client for new API with high transaction throughput (> 400 tx/s)
  • Various bug fixes
  • First prototype of Burrow EVM to run as transaction processor on Hyperledger Sawtooth Ledger

Hyperledger Cello

  • A user dashboard was added to support seeing blockchain status and chaincodes.
  • The k8s support features was started with intern students; Upgrade swarm support to latest version (17.04).
  • Refine the installation scripts to support multi-os-distributions.
  • Fabric 1.0-* supported scripts was added.

Hyperledger Composer

  • We completed all rebranding activities as part of the move to Hyperledger – we moved to the Hyperledger Docker Hub organization, and renamed the Yeoman generator module.
  • We added support for modelling and publishing events from a transaction processor function, allowing client applications and existing systems to respond to events from a deployed business network.
  • We made extensive changes to our new user and getting started documentation, including reworked installation guides and tutorials which are available in the docs: https://hyperledger.github.io/composer/introduction/introduction.html
  • We delivered a set of nodes for Node-RED which allow developers to easily build outbound and inbound integration between a deployed business network and external system using IoT/MQTT, WebSockets, TCP, etc.
  • We added experimental support for invoking external HTTP APIs from within a transaction processor function, allowing external data such as share prices to be used within business logic.
  • We are currently focusing on delivering Hyperledger Fabric v1.0 beta support, complex query support (by exploiting CouchDB), and a new vehicle lifecycle demo that shows off the power of Composer.

Hyperledger Explorer

  • No major updates to report this month.

Hyperledger Fabric

  • Hyperledger Fabric v1.0.0-beta was released, and the maintainers plan on weekly releases until we have a demonstrably stable release candidate. We hope to be able to release in late July if all goes well.
  • The project’s engineers have significantly increased test coverage (+82%) and reduced its open defect count (~130 -> 22) since the 1.0.0-alpha2 release. It has been encouraging to see the diversity of contributions. It the past month alone, we have had contributions from 73 individuals representing 12 companies (including IBM) and 12 unaffiliated individuals.
  • The project is seeing a steadily increasing stream of downloads of the milestone releases with global coverage (US, Brazil, China, India, UK, Germany, France, Croatia, Russia, Japan, Indonesia, Australia and even Pakistan). There is an abundance of interest in China, India and Japan, nearly rivaling the US.
  • The remaining focus is on improving the documentation, continuing to test and fix bugs, and complete the various license, crypto-export and security scans.

Hyperledger Indy

  • No major updates to report this month.

Hyperledger Iroha

  • No major updates to report this month.

Hyperledger Sawtooth

  • Graduated to Active status! 
  • Project page new and improved, now with demo networks: https://www.hyperledger.org/projects/sawtooth
  • Collaborating with Hyperledger Burrow to integrate EVM with Sawtooth.
  • Added “State Delta Subscriptions” for pub/sub feature
  • Added Supply Chain Transaction Family
  • Providing Hyperledger Sawtooth features for Open Music Initiative Summer Lab.
  • Completed Linux Foundation Core Infrastructure Initiative badge requirements.

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!