Hyperledger

Transaction Flow

In order to integrate privacy and permissions into the Hyperledger architecture, there are a few additional features which have been added on top of the Bitcoin design pattern. In the Hyperledger context, clients still propose transactions to the network, but the process for validating these transactions is slightly different.

In a Hyperledger app, a transaction can be required to find multiple endorsements from trusted parties within the system before it can be added to the blockchain. Endorsements can be configured to ensure a minimal risk of fraud within the system. An example of this might be to require a business partner to verify certain details of a transaction before it is written to the public ledger. Once all necessary endorsements have been met, the transaction is passed to an ordering node, which will add it to the chain, or Validated Ledger.

You can find the full docs here.

General TX Flow
  1. Client Initiates Transactions
  2. Endorsing Peers Verify Signature and Execute the Transaction
  3. Proposal Responses are Inspected
  4. Client Assembles Endorsements into a Transaction
  5. The transaction is Verified and Committed to the Ledger
  6. The Ledger is updated across all nodes

The full flow is seen in the figure below: