Hyperledger Fabric is a platform that enables the delivery of a secure, robust, permissioned blockchain for the enterprise that incorporates a byzantine fault tolerant consensus. We have learned much as we progressed through the v0.6-preview release. In particular, that in order to provide for the scalability and confidentiality needs of many use cases, a refactoring of the architecture was needed. The v0.6-preview release will be the final (barring any bug fixes) release based upon the original architecture.
Hyperledger Fabric's v1.0 architecture has been designed to address two vital enterprise-grade requirements – security and scalability. Businesses and organizations can leverage this new architecture to execute confidential transactions on networks with shared or common assets – e.g. supply chain, FOREX market, healthcare, etc. The progression to v1.0 will be incremental, with myriad windows for community members to contribute code and start curating the fabric to fit specific business needs.
The current implementation involves every validating peer shouldering the responsibility for the full gauntlet of network functionality. They execute transactions, perform consensus, and maintain the shared ledger. Not only does this configuration lay a huge computational burden on each peer, hindering scalability, but it also constricts important facets of privacy and confidentiality. Namely, there is no mechanism to “channel” or “silo” confidential transactions. Every peer can see the most minute, and at times, sensitive details and logic of every transaction. This is untenable for many enterprise businesses, who must abide by stringent regulatory statutes.
The new architecture introduces a clear functional separation of peer roles, and
allows a transaction to pass through the network in a structured and modularized fashion.
The peers are diverged into two distinct roles – Endorser & Committer. As an endorser,
the peer will simulate the transaction and ensure that the outcome is both deterministic
and stable. As a committer, the peer will validate the integrity of a transaction
and then append to the ledger. Now confidential transactions can be sent to specific
endorsers and their correlating committers, without the broader network being made cognizant of
the transaction. Additionally, policies can be set to determine what levels of
“endorsement” and “validation” are acceptable for a specific class of transactions.
A failure to meet these thresholds would simply result in a transaction being withdrawn
or labeled as "invalid", rather than imploding or stagnating the entire network.
This new model also introduces the possibility for more elaborate networks, such as a
foreign exchange market. For example, trade settlement might be contingent upon a
mandatory "endorsement" from a trusted third party (e.g. a clearing house).
The consensus or "ordering" process (i.e. algorithmic computation) is entirely abstracted
from the peer. This modularity not only provides a powerful security layer – the
ordering nodes are agnostic to the transaction logic – but it also generates a framework
where ordering can become a pluggable implementation and scalability can truly occur.
There is no longer a parallel relationship between the number of peers in a network and
the number of orderers. Now networks can grow dynamically (i.e. add endorsers and committers)
without having to add corresponding orderers, all the while existing in a modular
infrastructure designed to support high transaction throughput. Moreover, networks
now have the capability to completely liberate themselves from the computational and
legal burden of ordering by tapping into a pre-existing or third party-hosted "ordering service."
As v1.0 manifests, we will see the foundation for interoperable blockchain networks that have the ability to scale and transact in a manner adherent with regulatory and industry standards. Watch how fabric v1.0 and the Hyperledger Project are building a true blockchain for business -
Use the following links to explore upcoming additions to the codebase that will spawn the capabilities in v1.0:
- Familiarize yourself with the guidelines for code contributions to this project. Note: In order to participate in the development of the Hyperledger Fabric project, you will need an LF account. This will give you single sign-on to JIRA and Gerrit.
- Explore the design document for the new architecture
- Explore design docs for the various Fabric components
- Explore JIRA for open Hyperledger Fabric issues.
- Explore the JIRA backlog for upcoming Hyperledger Fabric issues.
- Explore JIRA for Hyperledger Fabric issues tagged with "help wanted."
- Explore the source code
- Explore the documentation