Hyperledger Fabric is an open-source permissioned distributed ledger platform.
Hyperledger Fabric is different from public permissionless blockchain protocols in that it provides:
- Privacy for transactions and confidentiality for organization data
- Membership services that allow for permissioned and identifiable network participant enrollment
Hyperledger Fabric is different from permissioned consortium blockchain protocols in that it provides:
- A modular architecture that allows customization for particular use cases and trust models.
Raft — a CFT consensus implementation in etcd.
Hyperledger Fabric uses orderer nodes to form consensus.
Hyperledger Fabric has the following foundational components:
- Certificate Authority (CA)
- Membership Service Provider (MSP)
- Ordering service
Peers are nodes in a Hyperledger Fabric network. They host ledgers and chaincodes.
Each peer has two communication interfaces:
- Peer to peer communication that implements gossip data dissemination protocol over TLS
- Node to owner communication implemented as gRPC
The Certificate Authority component manages the digital identities of the Hyperledger Fabric network participants.
The Membership Service Provider component identifies the network participants, their roles, and access privileges based on the Certificate Authority and by listing the participant identities.
Any transaction in a Hyperledger Fabric network goes through the ordering service before being packaged in a block, distributed to peers, and committed to the ledger by peers.
The ordering service consists of orderer nodes. The orderer nodes form the Raft consensus of the network.
In Hyperledger Fabric terminology, a packaged and deployed smart contract is called a chaincode.
A Hyperledger Fabric network is deployed with the following service nodes:
Updated 9 months ago