Create Blockchain

Create your Blockchain Network

  • Open the Create Blockchain Dialog

  • Provide your network, a suitable name and description on the purpose of blockchain

Select the blockchain Framework and the underlying Consensus Protocol.

Blockchain Framework can be depending on use case and the blockchain which the consortium partner agrees

1. Ethereum

2. Quorum

3. Hyperledger

Select the consensus protocol depending on the selection of blockchain

For Ethereum select the consensus protocol as POA (proof of authority)

For Quorum you can find two protocols

1. IBFT (Istanbul Byzantine Fault Tolerance)

Byzantine Fault Tolerance(BFT) is the feature of a distributed network to reach consensus(agreement on the same value) even when some of the nodes in the network fail to respond or respond with incorrect information. The objective of a BFT mechanism is to safeguard against the system failures by employing collective decision making(both – correct and faulty nodes) which aims to reduce to influence of the faulty nodes. BFT is derived from Byzantine Generals’ Problem.

Byzantine fault tolerance can be achieved if the correctly working nodes in the network reach an agreement on their values. There can be a default vote value given to missing messages i.e., we can assume that the message from a particular node is ‘faulty’ if the message is not received within a certain time limit. Furthermore, we can also assign a default response if the majority of nodes respond with a correct value.

Types of Byzantine Failures: There are two categories of failures that are considered. One is fail-stop(in which the node fails and stops operating) and other is arbitrary-node failure. Some of the arbitrary node failures are given below :

· Failure to return a result

· Respond with an incorrect result

· Respond with a deliberately misleading result

· Respond with a different result to different parts of the system

Advantages of IBFT:

· Energy efficiency : IBFT can achieve distributed consensus without carrying out complex mathematical computations(like in PoW). Zilliqa employs IBFT in combination with PoW-like complex computations round for every 100th block.

· Transaction finality : The transactions do not require multiple confirmations(like in case of PoW mechanism in Bitcoin where every node individually verifies all the transactions before adding the new block to the blockchain; confirmations can take between 10-60 minutes depending upon how many entities confirm the new block) after they have been finalized and agreed upon.

· Low reward variance : Every node in the network takes part in responding to the request by the client and hence every node can be incentivized leading to low variance in rewarding the nodes that help in decision making

2. RAFT

Raft is a distributed consensus algorithm. It was designed to be easily understood. It solves the problem of getting multiple servers to agree on a shared state even in the face of failures. The shared status is usually a data structure supported by a replicated log. We need the system to be fully operational as long as a majority of the servers are up.

Raft works by electing a leader in the cluster. The leader is responsible for accepting client requests and managing the replication of the log to other servers. The data flows only in one direction: from leader to other servers.

Raft decomposes consensus into three sub-problems:

  • Leader Election: A new leader needs to be elected in case of the failure of an existing one.

  • Log replication: The leader needs to keep the logs of all servers in sync with its own through replication.

  • Safety: If one of the servers has committed a log entry at a particular index, no other server can apply a different log entry for that index.

  • Select the Cloud Provider where you wish to deploy your blockchain nodes.

  • Enter the Node name & description Select the Geo and the Region where you want to host the blockchain node.

  • Wait for 10 minutes till blockchain status changes to Running, Manage your Network

Deploy Hyperledger Fabric:

  • Open the Create Blockchain either from Nav bar or from the “Launch Node”

Key in the details of Consortium name as per your choice. Consortium name can be “Healthcare” if you are creating a healthcare blockchain consortium or “Supplychain” if you are creating a supplychain blockchain consortium

Enter the details of the consortium description.

What is the purpose of this consortium?

Example: The purpose of this consortium is to bring together the supplychain partners which includes manufacturers, distributors and retailers for a common goal which will help in bringing in trust and transparency through blockchain

Select the blockchain Framework and the underlying Consensus Protocol.

Blockchain Framework can be depending on use case and the blockchain which the consortium partner agrees

Select the Cloud Provider where you wish to deploy your blockchain nodes.

Stezy platform Supports

1. Amazon Web Services

2. Microsoft Azure

3. Google Cloud

Key in the Certificate details, Root Admin, cluster details, orderer details and Peer details

Select the Region to host and the node type.

Creation of Hyperledger Fabric is now starting.

All the blockchain are up and running: