## 4 Case Study Implementation Using Hyperledger Fabric
Therefore, we get the optimal send rate as 2500 tps for the read throughput in the case of the proposed network. Similar to Figure 21, the optimal send rate for the transaction throughput is 1100 tps as the throughput decreases continuously with the increase of the send rate after that. Figure 9.2

Figure 9.3

Figure 9.4 Transaction history in the Composer web playground. Another study on the network latency was performed to indicate the amount of time taken for a transaction to be executed across the blockchain network. Similar to the first study, the latency also falls into two categories: the read latency and transaction latency. The read latency is the time that the read request is submitted plus the time that the reply is received. The transaction latency is a network-wide view of the amount of time taken for a transaction to be executed across the network. The measurement not only includes the time from the point that it is submitted but also the broadcast time and any correction time because of the consensus mechanism in place. [PERSON] et al. [47] proposed a useful definition of the network threshold, which is the amount of time for a percentage of the network to commit the transaction. In this study, the percentage of the network was set to 100% since the use of the non-probabilistic protocol like PBFT. General and simplified formulas for computing the read latency and transaction latency are shown in Equations (3) and (4), separately. As shown in Figure 22, the average read latency of the proposed system was evaluated by varying the send rate from 500 tps to 3000 tps 10 times at a random selected system resource utilization level. The read latency has a relatively small increase with the increase of the send rate. However, the latency increases

Figure 9.5 Blockchain network transaction throughput evaluation. Figure 9.6 Blockchain network read throughput evaluation. significantly after the send rate of 2500 since the optimal value is exceeded. Similarly, the graph in Figure 23 shows that the average transaction latency increases linearly as the user request rate increases, and this value rises sharply after the optimal send rate of 1100 tps. Figure 9.7

Figure 9.8

In general, Bitcoin takes near 10 min to mine a block, and it can be expected that a transaction takes around an hour on average as at least six confirmations are required before a transaction is finalized. For Ethereum, the average transaction time to mine a block is around 15 s. Moreover, this time cost varies significantly in terms of the network environments. According to Figure 21, the average transaction latency for the proposed blockchain network is

Figure 9.9 Blockchain network transaction latency evaluation. Figure 10:0 Blockchain network read latency evaluation. far ahead than most popular blockchain platforms. The reason behind that depends on the nature of the blockchain, which directly impacts the transaction performance. Bitcoin and Ethereum are permissionless blockchains, where anyone can participate, and every participant is anonymous. In order to establish trust among anonymous participants, the permissionless blockchain typically employs a native cryptocurrency or transaction fees to provide economic incentive to offset the extraordinary costs of validating transactions based on the proof-of-work (PoW). On the other hand, the proposed blockchain is built on a permissioned network, where transactions are operated among a set of known, identified participants under a governance model. By relying on the identities of the participants, a permissioned blockchain can use a more traditional PBFT protocol that does not require costly mining. Additionally, a permissioned blockchain can diminish the risk of a participant intentionally introducing a malicious code through a smart contract.