# Inter-Blockchain Communication Message Relay Time Measurement and Analysis in Cosmos +
## 5 Results and Analysis
### Results of Measuring IBC Msg Relay Time  
The IBC message relay time data was modified to address its perceived length, which may have distorted the concentration tendency. Figure 13 illustrates Cosmos's IBC message relay time before outliers are removed. The top three data points (message relay time) are 371.886, 285.052, and 198.265 s. The boxplot, as shown in Figure 14, shows that these three data points are extensively apart compared to the total data distribution. Outliers were found in fungible token transfers with the sequence numbers 1029737, 1029741, and 1029744 between channel-141 and channel-0, which connects the Cosmos Hub and Osmosis. Valid IBC Recv Tx and Valid IBC Ack Tx outliers occurred within blocks of the same height.  
The block-generating times for Cosmos Hub and Osmosis remained constant during the outlier occurrence at the typical block-generation time. Furthermore, the Round value in the block data, representing the number of times the relevant height block was revoted, was 0 [17]. Analysis shows that the three outliers faced delays in the relay process rather than in each blockchain's consensus process. The cause of the IBC message relay time delay deserves additional investigation. As a result, this study removes outliers from the dataset, refines the data, and performs statistical analysis.  
Figure 15 shows the ordered IBC message relay timings, which compute the time from Generation_time to Ack_time of the IBC Msg Relay Time data. The longest time for an IBC message relay is 138.662 s, while the minimum duration is 28.176 s. The message relay process takes roughly 55.448 s on average. The median value is 52.153 s, which is close to the average, showing that the IBC message relay time data is distributed evenly.  
The minimum value of G to T time was taken to be 0 in order to synchronize the time zones of the Cosmos hub and the Measurement Node by adding \(-\)13.081 to the minimum value of Generation time. Given the low variance and standard deviation of the T to R time section, the data are concentrated around the mean. Furthermore, the message delivery in R to A time section was approximately \(\times\)1.3 higher than in other time sections. As a result, the T to R time will be supplied at an average of 13 s, while R to A time will be slower than other time sections. Transactions are transmitted from the Cosmos Hub and incorporated in blocks at G to T time. The G to T time is the same as the transaction processing procedure in the blockchain, with the only difference being the kind of transaction. The in-chain transaction processing time in the Cosmos Hub is estimated as G to Time.  
Figure 14: IBC Message Relay Time Bloxplot.  
Figure 13: IBC Message Relay Time before removing the outliers.  
By adding the value of the minimum G to T time (\(-13.081\)) to the Generation_time, the minimum G to T time was set to 0. The parallax between the Measurement Node and the Cosmos Hub was aligned with this correction. Given the low variance and standard deviation of the T to R time section, the data are concentrated around the mean. The message delivery in R to A time section was approximately \(\times 1.3\) longer than in other time sections, which implies that in the T to R time section, a transaction is expected to be transmitted in an average of 13 s, while in the R to A time section, the delivery time will be slower than other sections. Transactions are transmitted from the Cosmos Hub and incorporated in blocks at G to T time section. Regardless of transaction type, the G to T time represents transaction processing time within the Cosmos Hub blockchain. Table 3 shows the findings of the distribution of IBC time.