# Inter-Blockchain Communication Message Relay Time Measurement and Analysis in Cosmos +
## 3 Data Collection and Methodology  
### Proposed Framework  
This section describes the mechanism for collecting message delivery times between the Osmosis and Cosmos Hub blockchains. It also explains the proposed tracking approach, which would link inter-blockchain messages via fungible token transfers in the aggregated transactions. The proposed framework for tracking message delivery times between blockchains is depicted in Figure 4. \begin{table}
\begin{tabular}{c c} \hline \hline
**Transaction Types** & **Description** \\ \hline IBC Transfer & Locking of the Handling Token in the Sending Chain \\ \hline IBC RecvPacket & \
\begin{tabular}{c} Proof of token lock completion on the transmitting chain \\ and token transfer to the receiving chain \\ \end{tabular} \\ \hline IBC Acknowledgement &
\begin{tabular}{c} The receiving chain’s proof of token receipt and token \\ transfer completion response to the sender chain \\ \end{tabular} \\ \hline IBC Timeout & Failure of token transfer response to sending chain \\ \hline \hline \end{tabular}
\end{table} 
Table 1: Cosmos IBC transactions. Figure 3: Cosmos inter-blockchain communication protocol sequence diagram. Each blockchain's mainnet [15] is linked to the Cosmos Hub and Osmosis clients, which synchronize to update the ledger information. These clients function in each network just like any other node. The Cosmos Hub client transmits IBC Tx by frequently sending a fungible token [16] based on the IBC to the wallet address of the Osmosis client. These fragmented transactions are confirmed using inter-blockchain Relayer message filtering and tracking, and the message delivery time between these blockchains is determined for each fungible token transmission. The measurement node, which gathers and examines inter-blockchain message delivery times inside the Cosmos network, is an essential part of the proposed framework. Its primary goal is to measure how long it takes messages to travel across various blockchains, giving important information about how well the Inter-Blockchain Communication (IBC) protocol is working. The measurement node consists of two nodes serving as clients within the Cosmos network. The first node is connected to the Cosmos Hub, while the second node is linked to the Osmosis client, representing different blockchains. These connections enable the measurement node to retrieve the latest blockchain data, including transaction details. Obtaining IBC Tx Generation, IBC Transfer, IBC Recv, and IBC Ack data--which reflect inter-blockchain communication between the Cosmos Hub and Osmosis--requires requesting specific transaction data using RPC commands like \"gaiad\" and \"osmosiod\". Once the data has been gathered, the node processes and analyzes it to determine the  
Figure 4: Measurement framework for message delivery time between blockchains. inter-blockchain message delivery time and evaluate the effectiveness of the IBC protocol. To comprehend the total distribution of message delivery durations and correlations between time intervals, statistical approaches like kernel density estimation and lognormal distribution analysis are used, exposing performance characteristics of inter-blockchain communication in Cosmos. The measurement node is crucial to understanding IBC protocol performance and enabling further investigation and advancements for the scalability and interoperability of the Cosmos ecosystem.3.2 Transaction Database. Figure 5 depicts the seven transaction databases used in Cosmos to measure message transit time between blockchains. The hash and propagation start time of fungible token transfer transactions generated by the Measurement Node's IBC Tx Generation Controller comprise the IBC Tx Generation data. The IBC Transfer Tx data capture transactions that include the requested fungible token transfer transactions from the IBC Tx Generation Controller in the Cosmos Hub's blockchain through a consensus process. The IBC Transfer Tx data contains transactions with matching hashes from the IBC Tx Generation data.