# A Blockchain Protocol for Authenticating Space Communications between Satellites Constellations
## 5 Simulation Results
### Blockchain Performance Results  
Four metrics have been used to evaluate blockchain performance. These metrics are read latency (RL), transaction latency (TL), read throughput (RT), and transaction throughput (TT). They can be calculated as in Equations (1)-(4) respectively:  
\[\mathrm{RL}=\mathrm{Response\;time}-\mathrm{Submission\;time} \tag{1}\]  
\[\mathrm{TL}=\mathrm{Confirmation\;time@network\;threshold}-\mathrm{submission\;time} \tag{2}\]  
\[\mathrm{RT}=\frac{\sum\mathrm{Reads\;Operations}}{\sum\mathrm{Times\;in\;sec\,onds}} \tag{3}\]  
\[\mathrm{TT}=\frac{\sum\mathrm{Committed\;Transactions}}{\sum\mathrm{Time\;in\;sec\,onds}} \tag{4}\]  
Figure 4 depicts the obtained results that clarify the impact of a transactional data size equal to 1049 bytes on RL, and TL after applying algorithm 1 to the dataset depicted in Table 1. Figure 5 depicts the obtained results that clarify the impact of a transactional data size equal to 2049 bytes on RL, and TL after applying Algorithm 2 to the dataset depicted in Table 2. Figure 6 depicts the obtained results that clarify the impact of a transactional data size equal to 3049 bytes on RL, and TL after applying Algorithm 2 to the dataset depicted in Table 3. On the other hand, Tables 4-6 clarify the impacts of the three categories of transactional data size (i.e., 1049, 2049, and 3049 bytes) and GAS on Reading Throughput (RT) and Transaction Throughput (TT). \begin{table}
\begin{tabular}{c c c c c c c c c c} \hline \hline
**A/B** & **S6** & **S10** & **S8** & **S5** & **S3** & **S7** & **S4** & **S9** & **SUM** \\ \hline
**S1** & 7 & 4 & 8 & 6 & 7 & 5 & 8 & 5 & **50** \\ \hline
**S2** & 14 & 12 & 16 & 12 & 8 & 18 & 11 & 13 & **100** \\ \hline
**S3** & 18 & 23 & 16 & 25 & 14 & 17 & 21 & 16 & **150** \\ \hline
**S9** & 28 & 23 & 27 & 29 & 33 & 24 & 19 & 17 & **200** \\ \hline
**S5** & 29 & 38 & 33 & 17 & 29 & 36 & 33 & 35 & **250** \\ \hline
**S6** & 27 & 43 & 39 & 35 & 41 & 33 & 44 & 38 & **300** \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Satellites transactions between Swarm A, and B (size of a transaction is 2049 bytes). \begin{table}
\begin{tabular}{c c c c c c c c c c} \hline \hline
**B/C** & **S10** & **S6** & **S4** & **S1** & **S7** & **S5** & **S3** & **S8** & **SUM** \\ \hline
**S2** & 5 & 6 & 7 & 4 & 9 & 8 & 4 & 7 & **50** \\ \hline
**S6** & 13 & 12 & 9 & 17 & 15 & 9 & 14 & 11 & **100** \\ \hline
**S7** & 21 & 13 & 24 & 15 & 22 & 15 & 23 & 17 & **150** \\ \hline
**S9** & 26 & 17 & 21 & 28 & 30 & 29 & 24 & 25 & **200** \\ \hline
**S5** & 30 & 29 & 33 & 39 & 26 & 37 & 32 & 24 & **250** \\ \hline
**S10** & 34 & 38 & 49 & 33 & 36 & 39 & 40 & 31 & **300** \\ \hline \hline \end{tabular}
\end{table} 
Table 3: Satellites transactions between Swarm B, and C (the size of a transaction is 3049 bytes). Figure 4: Impact of the transactional data size, 1049 bytes on RL, and TL for (**a**) 50, (**b**) 100, (**c**) 150, (**d**) 200, (**e**) 250, and (**f**) 300 transactions. Figure 5: Impact of the transactional data size,2049 bytes on RL, and TL for (**a**) 50, (**b**) 100, (**c**) 150, (**d**) 200, (**e**) 250, and (**f**) 300 transactions. \begin{table}
\begin{tabular}{c c c c c} \hline \hline
**\#Satellites Trans** & **(RT)/RPS** & **(TT)/TPS** & **Gas** & **Size (BYTES)** \\ \hline
50 & 112.95 & 2.95 & 202,419 & 1049 \\ \hline
100 & 68.19 & 1.92 & 202,419 & 1049 \\ \hline
150 & 50.90 & 1.48 & 202,419 & 1049 \\ \hline
200 & 41.41 & 1.20 & 202,419 & 1049 \\ \hline
250 & 33.87 & 0.99 & 202,419 & 1049 \\ \hline
300 & 28.32 & 0.83 & 202,419 & 1049 \\ \hline \hline \end{tabular}
\end{table} 
Table 4: Results of the impact of the transactional data size **1049** bytes on RT, and TT according to the number of satellite transactions.