Intro to Private Blockchains

Hyperledger Architecture

The making of the machine This brief video was created by IBM to explain why Hyperledger is different. IBM is among the core developers of this new protocol and has committed in-house resources to build this solution for industrial blockchains. A number of other major software companies including Oracle and the Linux Foundation have also committed in-house teams to support the development of the Hyperledger protocol.

Where does your food come from? // IBM Blockchain


In a public blockchain, trust limitations restrict how information can be allowed to flow. In a private environment, there is much more flexibility, which means that different nodes in the network can have a wider set of responsibilities and the advantage of efficiency tools which rely on trust within the network.


Unlike the bitcoin or ethereum networks, where all nodes are alike, Hyperledger uses different nodes for different purposes, which ultimately increases efficiency across the network.

In the Hyperledger, a node must take on one of three roles:

  • Peer - A peer node is similar to a standard client in the Bitcoin or Ethereum networks.
  • Endorsing - Endorsing nodes can sometimes act as peer nodes, but have the added responsibility and privilege of endorsing others' transactions.
  • Ordering - Ordering nodes are responsible for adding records to the ledger. These are similar to mining nodes in public blockchains.


In order to increase the overall efficiency of the system, the network uses several distinct record systems:

In a Hyperledger Network, all most new transactions are added to the State Object almost immediately, producing a database which can perform nearly as well as a common system like SQL, but with all the benefits of a distributed ledger.