Blob

Ethereum ACDC#144: Developers plan to include EIP 7742 in Pectra, which can dynamically set blob gas targets and maximum limits

ChainCatcher news, Galaxy's Vice President of Research Christine Kim summarized the main points of the 144th Ethereum Core Developers Consensus Meeting (ACDC #144):Developers agreed to include a new code change EIP 7742 in Pectra, which allows the beacon chain to dynamically set the network's target and maximum blob gas limits. The inclusion of EIP 7742 indicates that developers may also increase the target and maximum blob gas limits in Pectra. However, some developers raised concerns during the call that incorporating additional EIPs (especially EIP 7742) would delay the activation of other Pectra code changes on the mainnet. Developers also discussed the testing progress of Pectra and PeerDAS development.L2 rollup Base developer Francis Li introduced the urgency and fundamental principles of increasing blob capacity in Pectra. Li suggested increasing the blob gas target to 5 and the maximum to 8, along with additional work at the network layer, such as implementing engine_getBlobsV1. Busa pointed out that the increase in blob capacity should be combined with the deployment of EIP 7742, which introduces a mechanism to dynamically set blob gas targets and maximum limits through CL. Busa stated that the current mechanism for setting these parameters is difficult to change, and introducing EIP 7742 would ensure that developers can easily adjust these settings in the future, such as upgrades like PeerDAS. However, Busa also noted that EIP 7742 requires additional work from the EL and CL client teams for deployment and could delay Pectra's timeline by 1 to 2 months. He urged developers to consider starting the work on deploying EIP 7742 as soon as possible to avoid unnecessary delays in the Pectra upgrade.

Vitalik: The key goal of validators is to avoid power concentration, especially in aspects such as consensus rule validation and fork choice

ChainCatcher news, Ethereum co-founder Vitalik Buterin recently responded to concerns raised by Ethereum core developer Péter Szilágyi regarding network decentralization and validation mechanisms.In response to how validators can obtain 32MB of blob transaction data every 12 seconds, Buterin proposed two possible strategies: each validator is responsible for building only 1/16 of the block, or validators only perform DAS checks without needing to fully download the data.Regarding the issue of Verkle tree design not deleting storage slots, Buterin stated that the impact of deleting storage slots is currently quite small. He denied claims about abandoning the transaction pool, emphasizing that this is an outdated idea that does not align with the current direction of Ethereum research.Buterin acknowledged that validation does not require an execution layer (EL), but stressed that this does not mean making it difficult for most people to run an EL. He pointed out that using SNARKs technology could enable more users to achieve full validation.Buterin emphasized that the key goal for validators is to avoid power concentration, especially in terms of consensus rule validation, fork choice, and transaction inclusion. He believes that during periods of only witnessing, there is no need to re-execute the EVM cycle.
ChainCatcher Building the Web3 world with innovators