Hyperledger Fabric https://github.com/hyperledger/fabric

Project Health

Hyperledger Fabric has stabilized with an LTS release process and incremental new features being added in minor releases. There is less churn and fewer commits than in years past, with continued focus on quality and support. New features get proposed, approved, and implemented based on a community RFC process. Mailing list activity is down compared to prior years. PRs and mailing list questions are generally turned around quickly.

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.

Questions/Issues for the TSC



v2.2 is the current LTS releases with patch releases quarterly.

Releases past quarter:

  • v2.2.4 - September 8, 2021
  • v2.3.3 - September 8, 2021
  • v2.4.0-beta - August 12, 2021

Upcoming releases planned this quarter:

  • v2.4.0

Overall Activity in the Past Quarter

The project delivered v2.4.0-beta with two significant new features:

  • Fabric Gateway - The Fabric Gateway will remove much of the transaction submission and query logic from the client application and shift it to a common gateway running within the Fabric peer, enabling each of the various client SDKs to be slimmer, more consistent, and require less maintenance. Applications will interact with a trusted peer (e.g. at their organization) and the peer will coordinate endorsements from other peers and submission to the ordering service. It will also simplify the administrative overhead of running a Fabric network because client applications will be able to connect and submit transactions via a single network port at their organization rather than the current situation where ports have to be opened from a client application to multiple peers across potentially multiple organizations. The Fabric Gateway is delivered along with slim SDKs in the https://github.com/hyperledger/fabric-gateway repository. Check out the client application samples.
  • Peer unjoin - The new command "peer node unjoin" enables an administrator to remove (unjoin) a channel from a peer.
    The peer must be stopped when the command is executed so that channel artifacts can be cleaned up.
    The channel's blockchain, state database, and associated entries will be removed from the peer.
    When the peer is restarted it will no longer receive blocks for the channel.

Additionally the project has been planning future work through the RFC process.

RFCs merged this quarter:

  • OpenTelemetry (implementation has started across Fabric, SDKs, and chaincodes to enable tracing across the components).

New RFCs in review this quarter:

  • Private Data Purge

A survey was completed to gauge interest in future enhancements. The top candidates were identified as 1) BFT support 2) Pruning of old blocks 3) Performance improvements. Each of these items are on the Fabric roadmap. Specifically in the area of BFT options, the SmartBFT RFC has been revived and progress is being made on the MirBFT Hyperledger lab.

There has also been a significant amount of Fabric activity in Hyperledger Labs, a few highlights:

Current Plans

The project is working towards a final v2.4.0 release in Q4 with the Fabric Gateway as the primary new feature.

Other work items in plan or in progress:

  • A feature to purge private data stores, which will help solutions meet GDPR requirements. RFC available for review.
  • A more realistic Node.js SDK sample application demonstrating good practices (connection management, error handling, timeouts, retries, etc)
  • Guidance for kubernetes deployments and announcement of a Fabric Kubernetes working group. For more information see the contributor meeting from October 13th.

Maintainer Diversity

One new maintainer was added this quarter. 6 of 11 maintainers are from IBM.

Contributor Diversity

Year to year comparison, by commit:

  • Q3 2020 - 990 commits. 69% from IBM.
  • Q3 2021 - 411 commits. 59% from IBM

Year to year comparison, by contributor:

  • Q3 2020 - 130 contributors. 27% from IBM.
  • Q3 2021 - 87 contributors. 28% from IBM.

Additional Information

Link to the Fabric dashboard: Q3 2021

Reviewed By


  1. There is a new template that asks the following question for #2 "Have you implemented the Common Repository Structure in all your repos?" It seems that the answer to this is yes, but could you confirm?

    1. That is correct. We need to make sure we pick up the new template next quarter.

      1. I made the edit in this report... and the answer is Yes!

  2. Can we have details on the Fabric Kubernetes working group and share & encourage the community to get involved? I tried to find in Rocket chat , mailing list but did not find any details. We should share this working group details to fabric mailing list and rocket chat.