IT-SDK-Hyperledger-Fabric

Ref.

• https://www.serial-coder.com/post/demystifying-hyperledger-fabric-fabric-architecture/#the-consensus-in-hyperledger-fabric
• https://medium.com/xord/hyperledger-fabric-architecture-a-deep-dive-cea478f39765
• https://www.spydra.app/blog/architecture-of-hyperledger-fabric-an-in-depth-guide
• https://developer.ibm.com/articles/blockchain-basics-hyperledger-fabric/
• https://hyperledger-fabric.readthedocs.io/en/release-1.4/arch-deep-dive.html

Key Components

• Client: is a node that considered to be an application that interacts with Fabric blockchain network.
• Peer: is a node that stores all transactions on a joining channel.
• Orderer: is node responsible for ordering/endorsing(bestätigen) transactions, creating a new block of ordered transactions, and distributing a newly created block to all peers on a relevant channel.
• CA (Certificate Authority): is responsible for managing user certificates such as user registration, user enrollment, user revocation, and etc.
• MSP (Membership Services Provider): is a node that Manages identities and permissions of users and nodes within the network.
• Channels
• Chaincode
• Ledger

Basic workflow v1

• The submitting client creates a transaction and sends it to endorsing peers of its choice.
• The endorsing peer simulates a transaction and produces an endorsement signature.
• The submitting client collects an endorsement for a transaction and broadcasts it through ordering service.
• The ordering service delivers a transactions (blocks) to the committing peers.
• The committing peers appended transaction to the Ledger.