PANews reported on July 27 that regarding Vitalik’s response to “Ethereum is becoming more and more decentralized in verification but centralized in control”, a community user mentioned that “sending 32MB of data to 4 nodes requires 1Gbit of upstream bandwidth. If the network requires 4 jumps, 4Gbits of bandwidth is required, and when considering data propagation, the upstream bandwidth requirement may double to 2.5GBit/s.” No direct answer was given.
Vitalik Buterin said that we don't need a single actor to broadcast all blobs. The blobs are already in the mempool, and there are many options for distributed broadcasting. There are still quite a few steps to go before a full DAS with the 16 MB goal is achieved, and there are no plans to stick with it until a satisfactory solution is found.
Earlier news, Ethereum core developer Péter Szilágyi (karalabe.eth) tweeted that the future direction of Ethereum, PeerDAS, plans to increase the data block size to 32MB in the next upgrade, which will have a negative impact on local block producers. He pointed out that Ethereum's block propagation time is very strict, with only 4 seconds to propagate the block to the entire network. Although PeerDAS divides the subnet, it still needs to propagate 32MB of data within 4 seconds, which is an unbearable burden for home nodes.
