Enhance account abstraction, optimize Layer2: The third major upgrade of Ethereum is approaching

The ETH2.0 Pectra upgrade is expected to be implemented in the first quarter of 2025. This is the third major upgrade of ETH2.0, following the ETH2.0 merge in September 2022 and the Cancun upgrade in March 2024. At the Ethereum core developer call on January 9, 2025, Tim Beiko, the technical protocol support lead, proposed to initiate the 5th development network (Devnet 5) process for the Pactra upgrade this week, starting on January 13, and upgrade the public testnets Sepoila and Holesky in February 2025, with the mainnet activation in March 2025. The Pectra upgrade consists of two main parts: the Prague execution layer upgrade and the Electra consensus layer upgrade. The key proposals in this technical upgrade include enhancing account abstraction, optimizing validator operations, and continuing to improve the performance of the Ethereum network. It also includes technical protocols for optimizing Layer2, which is a highlight of the Pectra upgrade. • Technical protocols related to the consensus layer upgrade include: EIP-6110, EIP-7002, EIP-7251, EIP-7549, EIP-7691. • Technical protocols related to the execution layer upgrade include: EIP-7685, EIP-7623, EIP-7702, EIP-2537, EIP-2935. How does the Pectra upgrade improve Ethereum? According to the EIP-7600 Pectra hard fork process implementation protocol, the following Ethereum improvement proposals have been included in the Pectra upgrade: EIP-6110: Using on-chain deposit mechanism at the consensus layer • When validators deposit ETH, they no longer need to rely on the voting mechanism at the consensus layer for validation, thus enhancing the security of validator operations. Even in the presence of more than two-thirds of adversarial stake, honest nodes can still cope. This mechanism can also reduce the complexity of client software design and reduce operational delays. EIP-7002: Triggering withdrawals from the execution layer • Allows validators to trigger withdrawals and perform extractions through the execution layer. EIP-7251: Increase MAX_EFFECTIVE_BALANCE • Allows Ethereum staking to exceed 32 ETH, with the minimum staking threshold remaining unchanged at 32 ETH. The improvement of this technical protocol aims to allow large node operators to reduce the number of validators in the network by merging multiple validators, thereby reducing the peer-to-peer messaging, signature aggregation, and storage burdens. EIP-7549: Remove Committee Index from the proof • Aiming to achieve more efficient consensus voting aggregation, reduce verification costs, and network load. EIP-7691: Increase Blob quantity • Increase the maximum number of Blobs per block to 6-9, to help Ethereum improve scalability through Layer2 solutions. EIP-7685: General execution layer request • This proposal defines a general framework for storing contract-triggered requests, simplifying the addition of new request types without changing the structure of the execution block, ultimately creating a more secure system for users. EIP-7623: Increase the cost of calldata • Since the implementation of EIP-1599, the gas cost limit for Ethereum blocks has not been increased, but the amount of data published to the mainnet has been increasing. Since the implementation of EIP-2028, the cost of calldata has remained unchanged. However, with the introduction of Blob by EIP-4844, the cost of calldata needs to be reassessed to reduce the maximum block data size, to free up data space for more Blobs that can help improve block throughput. EIP-7702: Set EOA account code • Add a new type tx to enable code execution for EOA accounts, to enhance the flexibility and programmability of accounts. EIP-2537: Precompile for BLS12-381 curve operations • By introducing precompiled contracts, add support for BLS12-381 curve operations to Ethereum, which can achieve cryptographic algorithm BLS signature verification and allow multiple signatures to be aggregated into one signature, thereby reducing the complexity of verification. EIP-2935: Save historical block hashes in the state • By storing the recent 8192 block hashes in system contracts, provide support for stateless client models and more flexible historical block hash queries. These hash values can be queried directly through contracts and provided as witness bundling to stateless clients. However, the earlier and more attention-grabbing technical proposal EIP-7594 has been suspended from updates for over 6 months and is not expected to be implemented in the Pectra upgrade. EIP-7594 introduces the Data Availability Sampling (DAS) protocol to ensure that Blob data is available when downloading data subsets.
🔍 More cryptocurrency news and analysis, only on mlion 🔍👉 Visit mlion now to stay updated on the cryptocurrency market and start a new chapter in your investment journey!

#ETH #ACT #MAGA