# A Survey of the Real-Time Metaverse: Challenges and Opportunities +
## 8 Challenges and Opportunities
### Blockchain in Real-Time Data Handling  
Blockchain technology, while pivotal for decentralization and security in the metaverse, faces significant limitations when it comes to supporting real-time, high-frequency data exchanges [257]. Most blockchain systems, particularly those based on proof-of-work (PoW) consensus mechanisms, are designed to prioritize security and decentralization over speed. In platforms like Bitcoin and Ethereum, transaction processing times are measured in minutes, which creates unacceptable latency for real-time metaverse applications that require instant responses, such as virtual commerce, real-time collaboration, and live events. The number of transactions per second (TPS) that these networks can handle is limited--Bitcoin supports approximately 7 TPS, while Ethereum manages around 30 TPS [258]. This is inadequate when compared to traditional payment systems like Visa, which can handle over 24,000 TPS, illustrating blockchain's current scalability issues. Even newer blockchain \begin{table}
\begin{tabular}{l l l l} \hline \hline
**Technology** & **Bandwidth Requirement** & **Latency** & **Resolution** \\ \hline \multirow{3}{*}{Wi-Fi 6E} & \multirow{3}{*}{Up to 2.4 Gbps} & \multirow{3}{*}{\(\sim\)20 ms} & HD, 2K, 4K \\  & & & 8K with a strong signal \\  & & & strength and minimal \\  & & & interference \\ \hline \multirow{3}{*}{Wi-Fi 7} & \multirow{3}{*}{Up to 46 Gbps} & \multirow{3}{*}{\(\sim\)10 ms} & Up to 8K \\  & & & \multicolumn{1}{l}{Potential to support 16K} \\  & & & video resolution \\ \hline \multirow{3}{*}{Wi-Fi 8} & \multirow{3}{*}{Up to 100 Gbps} & \multirow{3}{*}{\(<\)1 ms} & Up to 8K \\  & & & \multicolumn{1}{l}{Potential to support 16K} \\  & & & video resolution \\ \hline \multirow{3}{*}{5G Network} & \multirow{3}{*}{1-10 Gbps} & \multirow{3}{*}{1–10 ms} & Up to 4K \\  & & & 8K depends on network \\  & & & conditions and coverage \\ \hline NGCodec + 5G & \(\sim\)1–10 Gbps (optimized) & \(<\)5 ms & Up to 8K \\ \hline FPGA-based VR Streaming & Depends on setup & \(<\)1 ms & Up to 8K \\ \hline \hline \end{tabular}
\end{table} 
Table 1: Progression of VR, comparing bandwidth and latency across different technologies. models, such as Ethereum's transition to proof-of-stake (PoS) have improved efficiency but still face challenges in scaling to the demands of a real-time metaverse. Additionally, the block size and transaction confirmation time exacerbate these scalability problems. Blockchains like Bitcoin limit the size of each block to 1 MB, and Ethereum's average block size is similarly constrained, meaning only a small number of transactions can be processed in each block [259]. As the transaction volume increases--especially in a bustling metaverse with a large number of users interacting simultaneously--the network becomes congested, leading to increased transaction fees and even longer confirmation times. During periods of high demand, these delays and fees can render blockchain solutions impractical for applications where low latency and high throughput are critical, such as live virtual events or fast-moving virtual economies where digital assets must be exchanged instantaneously. Moreover, blockchain's inherent structure--where every transaction must be verified and recorded across a distributed ledger--further exacerbates latency issues in the metaverse [260]. The decentralized nature of blockchain, while crucial for security and autonomy, slows down transaction processing times due to the computational overhead required for consensus mechanisms. The synchronization of multiple nodes in a decentralized network to achieve consensus can lead to significant delays, rendering blockchain impractical for high-speed applications like real-time gaming or virtual events, where immediate feedback is necessary. For example, each transaction in Ethereum requires computationally intensive operations, such as cryptographic validation and the execution of smart contracts, which further delays the transaction finalization process [261].