## 4 Nazzfast Consensus Mechanism
### Block Creation Cycle
#### 4.4.1 Block Proposal Phase
**Deployment in the real-world network**

The deployment of blockchain is based on the type of network it is using. There are many blockchain networks available in the real world, such as Bitcoin [1], Ethereum [4], and Ethermint [117]. All were deployed according to their need. The general deployment of any blockchain network requires many stages. It has a backend deployment, a front-tend deployment, and blockchain network configurations. For a completely operational blockchain, it has a ledger, peer network, membership services, wallets, events, system management, and system integrations. There are multiple actors, such as the operator, developer, end user, and data storage, in the blockchain network that operate complete components of the network. It depends on the application network and how it uses the Nazfast consensus in its network. Either users or front-end software are used to operate \begin{table}
\begin{tabular}{l l l l} \hline \hline
**Ref.** & **Consensus Mechanism** &
\begin{tabular}{l} **Block** \\ **Time (s)** \\ \end{tabular} & **Finality** \\ \hline \hline \multirow{2}{*}{[112]} & Nazfast & \textasci{}0.3 & Final after block vote \\ \hline
[112] & EOS.IO & \textasci{}0.5 & Final after block vote \\ \hline
[14] & Tendermint (Cosmos) & \textasci{}1 & Final after block vote \\ \hline
[16] & Quorum IBFT & \textasci{}1 & Final after block vote \\ \hline
[113] & Avalanche & \textasci{}1-2 & Probabilistic finality \\ \hline
[100] & PBFT (Hyperledger Fabric) & \textasci{}2-5 & Final after block vote \\ \hline
[17] & Stellar (FBFT) & \textasci{}5 & Final after block vote \\ \hline \hline \end{tabular} Other Major Consensuses

\begin{tabular}{l l l l} \hline
[114] & Proof of Work (Bitcoin) & \textasci{}600 & Probabilistic, after six blocks \\ \hline
[101] & Casper FFG & \textasci{}12-14 & Deterministic finality \\ \hline
[4] & Proof of Stake (Ethereum) & \textasci{}12 & Final after a few blocks \\ \hline
[8] & Polkadot & \textasci{}6 & Deterministic finality \\ \hline
[115] & Algorand & \textasci{}4 & Deterministic finality \\ \hline
[102] & Casper CBC (Casper Network) & \textasci{}1-2 & Deterministic finality \\ \hline
[103] & Raft & \textasci{}1-2 & After consensus round \\ \hline
[104] & LaKSA & \textasci{}1 & Probabilistic finality \\ \hline
[99] & Delegated Proof of Stake (Bitshare) & \textasci{}1 & Finality after Confirmation \\ \hline
[108] & Aptos (Tetra BFT + PoS) & \textasci{}1 & Deterministic finality \\ \hline
[116] & Shardeum & \textasci{}1 & Deterministic finality \\ \hline
[107] & Sui Lutris & \textasci{}0.5 & Deterministic block finality \\ \hline
[109] & Solana (PoH + PoS) & \textasci{}0.4 & Probabilistic finality \\  & continued to 2023 & \textasci{}0.4 & Probabilistic finality \\ \hline \hline \end{tabular}
\end{table} 
Table 7: Comparison of the presented blockchain network system’s block time with others. the network for the Nazfast consensus. The Nazfast consensus can be deployed under the PoS blockchain umbrella architecture. It does not need any special hardware, nor does it have any special requirements for deployment. It can be implemented in our traditional peer-to-peer environment settings. ## 7 Limitations of Nazfast

The election mechanism provides a block creation committee list; if it does not supply a list on time or before time, the whole system will suffer, and the throughput of the system will decrease. We have already discussed the solution to this problem in the scalability section of the discussion. The concept of a host is involved in every fold of consensus; that is why it should work actively and be alive, or else the whole system will be slowed down. We already suggested that an additional alternate host for emergency situations would be suitable for the solution of this problem. ## 8 Conclusions

This paper presents a Nazfast consensus mechanism that has multiple folds. The consensus process used an election process (S&Sem) to securely select a fixed number of validators between all active validators for each block creation cycle.