On the Bandwidth Consumption of Blockchains
Andrei Lebedev, Vincent Gramoli
TL;DR
This work addresses the practical problem of bandwidth consumption in blockchains by delivering the first empirical, cross-protocol comparison across five layer-1 networks using a controlled 25-node testbed. It shows that transport mechanisms (polling vs WebSockets) and block propagation strategies (full blocks vs hashes) are the primary drivers of traffic, rather than raw transaction size, and that traffic patterns vary dramatically with network scale and validator composition. Solana exhibits node-dependent, high-bandwidth growth with network size, while Algorand and Redbelly scale mainly with the validator set; Avalanche and Aptos show hybrid scaling, with nuanced propagation behaviors. The findings have direct implications for deployment cost and robustness, highlighting design choices that can mitigate egress charges and improve resilience in large-scale blockchain deployments.
Abstract
With the advent of blockchain technology, the number of proposals has boomed. The network traffic imposed by these blockchain proposals increases the cost of hosting nodes. Unfortunately, as of today, we are not aware of any comparative study of the bandwidth consumption of blockchains. In this paper, we propose the first empirical comparison of blockchain bandwidth consumption. To this end, we measure the network traffic of blockchain network nodes of five blockchain protocols: Algorand, Aptos, Avalanche, Redbelly and Solana. We study the variation over time, differentiate the receiving and sending traffic and analyze how this traffic varies with the number of nodes and validators. We conclude that the transport protocol is the main factor impacting the network traffic, segregating node roles helps reduce traffic and different blockchains are differently impacted by the network size.
