Transaction flow in Hyperledger Fabric

  1. This flow assumes that a channel is set up and running.
  2. The application user has registered and enrolled with the organization’s certificate authority (CA) and received back necessary cryptographic material, which is used to authenticate to the network.
  3. The chaincode (containing a set of key value pairs representing the initial state of the radish market) is installed on the peers and instantiated on the channel.
  4. The chaincode contains logic defining a set of transaction instructions and the agreed upon price for a radish.
  5. An endorsement policy has also been set for this chaincode, stating that both peerA and peerB must endorse any transaction.

Step 1: Client A initiates a transaction

Step 2: Endorsing peers verify signature & execute the transaction

Step 3: Proposal responses are inspected

Step 4: Client assembles endorsements into a transaction

Step 5: Transaction is validated and committed

Step 6: Ledger updated

Each peer appends the block to the channel’s chain, and for each valid transaction the write sets are committed to current state database.
An event is emitted, to notify the client application that the transaction (invocation) has been immutably appended to the chain, as well as notification of whether the transaction was validated or invalidated.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store