Intro to Hyperledger
In this module, we'll explore where Hyperledger came from, and how it has evolved over time.
The best way to understand how Hyperledger works is to set up your own node.
Example: Hyperledger for Car Dealerships
It's not the size of your node that matters - it's how you use it.
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.
BUILDING A BLOCKCHAIN FOR BUSINESS WITH THE HYPERLEDGER PROJECT // IBM Developer
WHY IS HYPERLEDGER DIFFERENT?
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.
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:
- General Ledger – The overall ledger of the system records all transactions regardless of whether they’re approved or not. This is a useful tool for audits and ensures that no data is lost.
- Validated Ledger – Transactions which have been fully approved are added to the VLedger, which is a shortened version of the overall history containing only the successfully processed events.
- State Object – The State Object is stored as a database record representing the current state of the system. This provides the maximum functional efficiency as peer nodes can simply query the present state rather than reconstructing it from the ledger.