2022 Q2 Hyperledger FireFly

Created by Ray Chen, last modified by Jim Zhang on Aug 25, 2022

Project Health

We achieved a significant milestone this quarter with the release of Hyperledger FireFly 1.0.  In case you missed it, check out the launch blog .  Here is a quick recap of the 1.0 stack from the launch webinar:

The FireFly SuperNode: a complete stack for enterprises to build and scale secure Web3 applications. 

The 1.0 release includes a rich set of functionality that is hardened for production use and represents a major step in the development of the complete FireFly stack:

  • FireFly Core - Support for multiple protocols across public and private chains with a powerful orchestration engine backed by a scalable event bus. Manage private data, on-chain data, and shared storage. Track state across networks, chains, and internal back office systems.
  • Apps - Accelerate development with tools that make building on Web3 familiar to any Web2 developer, including an API Gateway, Event Streams, and the Smart Contract API Generator.
  • Flows - Coordinate how data, value, and processes flow both on-chain and off-chain in decentralized networks, while maintaining privacy and security.
  • Digital Assets - Manage tokens at institutional scale with APIs that simplify the creation, transfer, and tracking of fungible and non-fungible tokens. Simplify custody with robust wallet and key management integration capabilities. 
  • Tools - Monitor transactions, messages, and events in the FireFly Explorer. Test out key FireFly functionality and generate example code snippets in the FireFly Sandbox. Run apps with a rich set of DevOps tools on modern, scalable cloud architecture.

We hosted 2 webinars and 3 meetups on Hyperledger FireFly that had over 1,000 registrants and generated over 14,500 views on their recordings.  

We’ve also seen an uptick in new community members this quarter participating in discussions in Discord with 71 people versus 23 the previous quarter.

Contributors are very active in the project and in the month of May, excluding merges, we’ve had 8 authors push 144 commits to main.

There are currently 370K lines of code for Hyperledger FireFly across 11 repositories, with a total of 4.6K commits to date.

Required Information

  1. Have you switched from master to main in all your repos ? Yes
  2. Have you implemented the Common Repository Structure in all your repos ? Yes
  3. Has your project implemented these inclusive language changes listed below to your repo? You can optionally use the DCI Lint tool to make this a recurring action on your repo. Yes
  4. master → main
  5. slave → replicas
  6. blacklist → denylist
  7. whitelist → allowlist
  8. Have you added an Inclusive Language Statement to your project’s documentation and/or Wiki pages? No

Questions/Issues for the TSC

No questions for the TSC

Releases

April:

FireFly 1.0

May:

FireFly 1. 0.1

FireFly 1. 0.2

The full list of releases can be found at: https://github.com/hyperledger/firefly/releases

Overall Activity in the Past Quarter

The Discord is very active and project maintainers answer questions regularly. Some metrics for the last 90 days of activity.

Dimension

Link to Insights

PR Activities

https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Ffirefly/dashboard;subTab=technical;v=pull-request-management%2Fgithub-pr%2Foverview

Contributor Strength

https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Ffirefly/dashboard;quicktime=time_filter_3M

Commit Activities

https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Ffirefly/dashboard;subTab=technical;v=source-control%2Fcommits%2Foverview

Current Plans

  • Active: Enhanced connector framework structure 

    • active development on new public chain connectors for Ethereum and Bitcoin

  • Active: Namespace isolation

    • Allows single FireFly SuperNode to talk to multiple blockchains 

  • Major step towards multi-tenancy support

  • Active: New operation modes for Gateway and Consortium 

    • Explicit multi-chain support

  • Active: Revamped docs site

    • Major updates throughout for v1.0
  • Top level version toggle
  • Multi-language support starting with Chinese

  • Automated API and object reference sections

  • Queued: Enhanced API Security model

Please see the GitHub project board for our most updated plans: https://github.com/orgs/hyperledger/projects/4/views/7

Maintainer Diversity

No new maintainers in this quarter.

Contributor Diversity

Contributions in Q2 including code, documentation, or other contributions:

Active contributors from Kaleido: 10

Active contributors from other organizations: 1 (Built Technologies)

Additional Information

Various enterprises are already using FireFly for their business products and live deployments. 

These include the following:

Riskstream - The largest enterprise-level blockchain consortium in risk management and insurance uses Hyperledger FireFly for First Notice of Loss (FNOL) data sharing between companies, Mortality Monitor which offers a single source of digital decedent information required to process life insurance claims, Surety Bond Verification for Power of Attorney, and Licensing and Appointments micro credentialing.

Synaptic Health Alliance - A coalition of US healthcare leaders leveraged Hyperledger FireFly to create a blockchain-based decentralized Provider Data Directory. This directory tackles the challenge of providing access to care via accurate provider data.

TradeGo - A global commodity trading consortium that uses Hyperledger FireFly to get its Digital Presentation product to production much quicker and lower cost than initially expected. Digital Presentation enables highly efficient and transparent sharing of original, confidential trade documents in a digital format. 

AscendBit - AscendBit is a company owned by CP Group that is using Hyperledger FireFly to launch initiatives in Supply Chain as well as its own company coin.

The leaders of the Riskstream and Synaptic consortiums spoke at our FireFly launch and the CEO of TradeGo and CTO of AscendBit recently spoke at our FireFly 1.0 AP webinar .

Technical metrics from March 15, 2022 to June 15, 2022 may be found here

Reviewed By

Submission date

08-Jun-2022

Comments:

Have you added an  Inclusive Language Statement  to your project's documentation and/or Wiki pages? No

Do you have a plan for when you will do this?

Posted by tkuhrt at Jun 09, 2022 15:55

The last time I had heard anything about the Inclusive Language Proposal, it was still early in the proposal state. I read the Wiki pages and see that it has now been finalized so we'll go ahead and get this added. I'll take care of this next week.

Posted by nguyer at Jun 16, 2022 13:35