## 4 Nazzfast Consensus Mechanism
### Block Creation Cycle
#### 4.4.1 Block Proposal Phase
It is happening because the consensus involves all the validators of the system in the block-creation process. Therefore, we run the Tendermint simulation with

Figure 11: Tendermint consensus execution with 0.2 propagation time and connected to all validators. Figure 12: Tendermint consensus with different numbers of connections having the same validator number and propagation time. the minimum requirement to achieve the least block creation time of Tendermint, such as five validators, three transactions, two connections, and a 0.2 propagation delay. Figure 15 shows the simulation results with minimum initialization; we observe an average of 1.2 s as the minimum time for block creation in the Tendermint consensus. However, as the number of validators increases, the block creation time increases, and the throughput decreases. It will eventually drop the blockchain network performance. In the Nazfast consensus, we try to overcome the time increment problem to improve the scalability of the consensus. Our presented consensus is different in many ways from the Tendermint consensus to improve the scalability issue. Below, we present the major differences that we made in our consensus in comparison with the Tendermint consensus. Figure 14: Tendermint consensus with different numbers of transactions having the same validator number and propagation time. Figure 13: Tendermint consensus execution with different numbers of validators having propagation time 0.1 and connected to all validators. Figure 15: Tendermint consensus with minimum initialization, such as five validators, three transactions, two connections, and a 0.2 propagation delay. Comparison with Tendermint on Scalability Aspects

1. Reduced and fixed validators

The consensus used BFT layers for block finalization to improve security, such as the Tendermint consensus. The BFT layer has a high communication overhead rate. It reduces throughput and improves network latency. Tendermint uses network validators to sign the block for validation. It also increases block finalization time and reduces the throughput of the network. We also used the BFT layer for security; therefore, to improve the throughput of the complete consensus, we reduced and fixed the number of validators for the consensus to improve the scalability of the network. We used only fifteen V-validators, one wildcard entry validator, and five correctors in every block validation process instead of involving complete validators of the network. Hence, we have achieved block finalization in very little time. If we increase the number of validators in the validation process, the throughput time will be increased. They are directly proportional to each other. Block finalization time (Bt) \(\propto\) No. of validators in the validation committee (Nv)

\[\text{Bt}\propto\text{Nv}\]

\[\therefore\text{Bt/Nv}=\text{k}\]

Figure 10:0

where k is the non-zero, positive constant of proportionality. In such a case, where the values \(\text{Nv}_{1}\) and \(\text{Nv}_{2}\) of Nv correspond to the values \(\text{Bt}_{1}\) and \(\text{Bt}_{2}\) of Bt, respectively, then it turns into the following:

Figure 10:1

Therefore, the reduced and fixed number of validators in the Nazfast consensus leads to a higher throughput with less communication overhead in the proposed network. 2. Only five correctors for a commitment

In Tendermint consensus, all the validators of the system are involved in the validation process. It creates strong broadcasting pressure in the network. The communication overhead is also very high. In our proposed work, to reduce the total time of a block creation cycle, we reduce the number of validators in the commit phase. During the block creation cycle, \"check validity phase\", V-validators of the recent block creation cycle send their vote, which is pre-committed to correctors rather than to each other. Each V-validator sends their vote to five correctors instead of sending it to the remaining 14 V-validators and the wildcard entry validator.