jakiro
The Ethereum Pectra upgrade is expected to be implemented in the first quarter of 2025.This is the third major upgrade of Ethereum after the merger of Ethereum in September 2022 and the upgrade of Cancun in March 2024.
During the Ethereum core developer conference call held on January 9, 2025, Tim Beiko, head of technical agreement support at the executive layer, suggested that the Phase 5 Development Network (Devnet 5) process for Pactra upgrade be launched this week, January 13, and can upgrade Ethereum’s public test networks Sepoila and Holesky in February 2025, and will be activated on the main network in March 2025.
About Pectra Upgrade
Pectra upgrades include two main parts: Prague execution layer upgrade and Electra consensus layer upgrade.The key proposal in this technology upgrade is to enhance account abstraction, optimize validator operations, and continue to improve Ethereum network performance. It also includes a technical protocol to optimize Layer2, which is also a highlight that this Pectra upgrade deserves to be looked forward to.
-
Technical agreements related to consensus layer upgrade include:
EIP-6110, EIP-7002, EIP-7251, EIP-7549, EIP-7691.
-
Technical agreements related to execution layer upgrades include:
EIP-7685, EIP-7623, EIP-7702, EIP-2537, EIP-2935.
How to improve Ethereum with Pectra upgrade
According to the EIP-7600 Pectra hard fork process implementation protocol, the Ethereum improvement protocol that has been included in the Pectra upgrade includes:
EIP-6110: Using the in-protocol processing mechanism at the consensus layer
-
When a validator deposits ETH, it no longer needs to rely on the voting mechanism verification of the consensus layer, thereby improving the security of the validator’s operations. Even if there are more than two-thirds of the hostile rights pledges, honest nodes can deal with it.At the same time, this mechanism can reduce the complexity of client software design and also reduce operation delays.
EIP-7002: Triggered extraction from execution layer (Withdrawal)
-
Allows verifiers to extract through the execution layer, credentials trigger exit and perform extraction.
EIP-7251:Add MAX_EFFECTIVE_BALANCE
-
Ethereum is allowed to pledge more than 32 ETHs, and the minimum staking threshold has not changed, and it is still 32 ETHs.The improvements to this technology protocol are designed to allow large node operators to reduce the number of validators in the network by merging multiple validators, thereby reducing the burden of point-to-point messaging, signature aggregation, and storage.
EIP-7549:Move the Committee Index out of the proof
-
Aim to achieve more efficient consensus voting aggregation, reducing verification costs and network load.
EIP-7691: Increase the number of blobs
-
Increase the number of blobs per block to up to 6 to 9, helping Ethereum improve scalability through Layer2 solutions.
EIP-7685:General Execution Layer Request
-
The proposal defines a common framework for storing contract-triggered requests, which can simplify the addition of new request types without changing the structure of the Execution Block, and ultimately create a safer system for users.
EIP-7623: Increase the cost of calldata
-
Since the EIP-1599 proposed implementation, the limit on Gas fees for Ethereum blocks has not increased, but the number of data released to the main network has been increasing, and the average size of blocks has also been increasing. Since the implementation of EIP-2028, the cost of calldata has been increasing.It has not changed, but after EIP-4844 introduces blobs, it is necessary to re-evaluate the cost of calldata to reduce the data size of the maximum block, and make room for more blobs that can help improve block throughput.
EIP-7702: Setting up EOA Account Code
-
Add a new type tx to add code execution capabilities to EOA accounts to improve account flexibility and programmability.
EIP-2537:BLS12-381 Precompilation of curve operations
-
By introducing precompiled contracts (Precompils) to add support for BLS12-381 curve operation to Ethereum, the encryption algorithm BLS signature verification can be implemented and allows multiple signatures to be aggregated into one signature, reducing the complexity of verification.
EIP-2935:Save historical block hash in state
-
By storing the most recent 8192 block hashes in the system contract, it provides support for the stateless client model and provides more flexible historical block hash query capabilities.These hashes can be queried directly through the contract and are provided as witness bundling to stateless clients.
However, the early technology proposal EIP-7594, which has been under the radar for more than 6 months, has been suspended 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 only a subset of data is downloaded.
