# VidBlock: A Web3.0-Enabled Decentralized Blockchain Architecture for Live Video Streaming
## 4 Experiment and Evaluation  
### Implementation  
The experimental setup for evaluating the VidBlock system, as detailed in Table 3, included three main types of nodes: the ViB creator node, the ViB consumer node, and ViB relay nodes.  
ViB creator node: This node was deployed on Sdk_gphone64_arm64m hardware running Android 14, connected via an IEEE 802.11n network. The creator node is responsible for initiating live streams within the VidBlock ecosystem.  
\begin{table}
\begin{tabular}{|c|c|c|c|} \hline
**Category** & **Details** & **Specifications** & **Network Configuration** \\ \hline \multirow{8}{*}{Node Environment} & ViB Creator Node & SM-F711N, RAM 8 GB, Android 14 & IEEE 802.11n \\ \cline{2-4}  & ViB Consumer Node & Sdk\_gphone64\_arm64, Android 14 & LTE/5G Network \\ \cline{2-4}  & ViB Relay Nodes & Amazon Web Services, Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40 GHz (Seoul, Tokyo, California, Frankfurt) & Public IPv4 address \\ \hline \multirow{4}{*}{Blockchain Environment} & \multirow{4}{*}{Ethereum Nodes} & Intel(R) Xeon(R) Gold 5220 & \multirow{4}{*}{-} \\  & & CPU @ 2.20 GHz, 2 Core, 8 GB RAM, 512 GB & \\ \cline{1-1} \cline{3-4}  & & HDD/Docker v20.10.21, Geth & \\ \cline{1-1} \cline{3-4}  & & v1.11.6-stable & \\ \hline \multirow{2}{*}{Application} & VidBlock (using WebRTC [29] for P2P connections) & Flutter v3.13.7, Dart v3.1.3 & - \\ \hline \end{tabular}
\end{table}
Table 3: The experimental environment of the proposed system.  
ViB consumer node: Configured with 8 GB RAM, the consumer node operated on an SM-F711N device with Android 14 and accessed the network through LTE/5G connectivity. This node allows users to select and view live streams initiated by the creator node.
* ViB relay nodes: Relay nodes were hosted across multiple regions (Seoul, Tokyo, California, and Frankfurt) on Amazon Web Services. Each relay node was assigned a public IPv4 address, providing distributed and accessible streaming services globally. These nodes enhance streaming efficiency by relaying data between the creator and consumer nodes.
* The blockchain framework for VidBlock was implemented using Ethereum nodes, hosted on systems with Intel(R) Xeon(R) Gold 5220 CPUs (2 cores, 8 GB RAM) and 512 GB HDDs. Docker v20.10.21 and Geth v1.11.6-stable were used to manage the private Ethereum network, supporting the decentralized architecture of VidBlock.
* For peer-to-peer (P2P) communication and NAT traversal, WebRTC technology was adopted. This enabled efficient, direct content sharing between nodes, overcoming network barriers and ensuring seamless streaming.
* In addition, IPFS was selected as the distributed storage system in this experiment due to its decentralized nature, which eliminates the reliance on a central server, enhancing data availability and resilience. IPFS also provides efficient content addressing, allowing files to be retrieved based on their unique cryptographic hashes, which ensures data integrity and reduces duplication [30; 31]. These features make IPFS an ideal choice for distributed storage in a decentralized environment.  
The user interface (UI) and client node displays are illustrated in Figure 6. In this setup, the creator node initiates a live streaming session, while the consumer node connects to the stream by selecting it from the live list displayed in the UI. As seen in the top-right corner of each UI display for the creator and consumer nodes, they are situated on different private networks. This configuration emphasizes VidBlock's capability to enable seamless streaming across isolated network environments.  
Figure 6: VidBlock’s UI screens: main page (**a**), creators connected to a 5G network (**b**) and consumers connected to a IEEE802.11n network (**c**).