Hyperledger is a private validator network protocol. All the entities in a network must register with membership services to obtain an identity with access and transaction authority on the network. Validators determine the level of permissions required to transact. The network setup also defines the network as permissive, allowing the ease of access. It supports for rapid and high adoption for a more controlled and restrictive environment.

REST (Representational State Transfer) Server is often used to proxy requests to Hyperledger chaincode. This provides a well-defined process for accessing blockchain services.

It has a modular subsystem design so that different implementations can be plugged in and implemented over time. Modular and extensible means modularity in all components of all frameworks, including: Consensus layer Smart contract layer Communication Layer Data Store Identity services (root of trust, to identify the participants).

The application is bootstrapped knowing about a group of peers which are trusted by the application developer/administrator to provide authentic responses to discovery queries. There is the bootstrap of a peer network, during which policies, system chaincodes, and cryptographic materials (certs) are disseminated amongst participants, and the bootstrap of an ordering network. The bootstrap of the ordering network must precede the bootstrap of the peer network, as a peer network is contingent upon the presence of an ordering service. A network need only be “bootstrapped” once.

Hyperledger Caliper: A blockchain benchmark tool that allows users to measure performance of a specific implementation with predefined use cases Its in Alpha mode at time of writing. Contributed by developers from numerous organizations.

References:

References:

Peers are connected to the channel and can receive all the transactions that are broadcasted on that channel. Consensus takes place within a channel by members of the channel only. Channels are membership based.

References:

References:

Client Node: That initiates the transaction 2. Peer Nodes: Commits Transaction & keeps the data in sync across the ledger 3. Ordered: They are the communication backbones and responsible for the distribution of the transactions

References:

Nodes use a Peer to Peer protocol not a Client Server. The concept of node is common in all blockchain technologies. The “Node” becomes the communication end point in blockchain technology. Nodes connect to other nodes and that is how a blockchain is formed. Nodes use a type of peer-to-peer protocol for keeping the distributed ledger in sync across the network.

Each enrolled user is granted an allocation of transaction certificates (tCerts).

References:

References:

Invoke is called to update or query the ledger in a proposal transaction. Init is called during Instantiate transaction after the chaincode container has been established for the first time, allowing the chaincode to initialize its internal data. Invoke is called to update or query the ledger in a proposal transaction. Updated state variables are not committed to the ledger until the transaction is committed.

References:

Consensus is when the distributed ledger has been updated and all nodes maintain their own identical copy of the ledger. This is also known as the “World State” in some blockchains. This architecture allows for a new capacity as a system of recordkeeping that goes beyond being a simple database.