The Complete Guide to the Ethereum Pectra Upgrade

·

The Ethereum Pectra upgrade is scheduled for activation on the Ethereum mainnet at epoch 364032, which begins at 10:05:11 UTC on May 7, 2025.

An Overview of Pectra

Pectra represents the next major update following last year's Dencun upgrade. This upgrade significantly enhances the Ethereum ecosystem by introducing new functionalities for smart accounts, improving the validator experience, and supporting Layer 2 scaling solutions.

This guide will delve into the three primary areas of improvement brought by Pectra. For a comprehensive overview of all changes, you can refer to the official upgrade guide on ethereum.org.

Enhancing External Accounts with Smart Contract Capabilities

A cornerstone of the Pectra upgrade is EIP-7702, which marks a pivotal step forward in the journey toward full account abstraction. This proposal allows users to endow their standard External Owned Accounts (EOAs) with smart contract-like capabilities.

This hybrid approach merges the simplicity of EOAs with the powerful programmability of smart contract accounts. Specifically, it enables wallets to support advanced features such as:

When utilizing EIP-7702, an EOA owner signs an authorization that points to a specific delegate address containing the code to be executed. Once set up, the account gains these new programmable features. Because selecting a delegate involves transferring significant control, EIP-7702 enforces several critical security checks:

👉 Explore advanced account security options

Optimizing the Validator Experience

Pectra incorporates three key EIPs designed to improve the operational experience for validators: EIP-7251, EIP-7002, and EIP-6110.

EIP-7251 (Increasing the MAX_EFFECTIVE_BALANCE): This upgrade voluntarily allows validators to update their withdrawal credentials type, raising the maximum effective balance for earning rewards from 32 ETH to 2048 ETH.

For stakers, this enables the automatic compounding of rewards. Previously, any ETH staked beyond 32 ETH did not contribute to the validator's active stake. Users wanting to stake more than 32 ETH had to do so in increments of 32 ETH, often relying on staking pools for intermediate values. EIP-7251 allows both new and existing validators to be configured to earn rewards based on their actual staked amount, up to the new 2048 ETH limit.

This change also allows large staking operators to consolidate multiple 32 ETH validators, which can help reduce the overall bandwidth demands on the network.

EIP-7002 (Execution Layer Triggerable Exits): This proposal expands validator capabilities by introducing execution layer triggerable withdrawals. Previously, only a validator's active signing key could initiate an exit. Now, if an Ethereum address is set as the withdrawal credential, that address can also force an exit. This reduces trust assumptions in delegated staking setups, as the owner of the funds (whether an individual controlling an EOA or a DAO-managed smart contract) can always initiate a trustless exit.

EIP-6110 (On-Chain Validator Deposits): This EIP addresses a legacy issue from pre-merge Ethereum: the delay between a validator deposit being made and it joining the activation queue. Before The Merge, the Beacon Chain waited for 2048 blocks to process validator deposits to guard against potential Proof-of-Work reorganizations. This precaution is no longer necessary. EIP-6110 slashes the deposit processing delay from approximately 9 hours down to just 13 minutes.

Doubling Data Availability with Blob Expansion

The final major change in Pectra is EIP-7691, which doubles Ethereum's blob throughput.

Blobs, introduced in the Dencun upgrade, are a form of temporary storage used by Layer 2 solutions to submit compressed transaction data and proofs to Ethereum Layer 1. Their adoption led to a 10-100x reduction in L1 data fees for L2s, drastically cutting transaction costs for end-users.

Currently, the Ethereum mainnet supports an average of 3 blobs per block, with a maximum capacity of 6. EIP-7691 increases this to an average of 6 and a maximum of 9 blobs per block.

Unlike calldata, which is permanently stored by every node, blobs are pruned after 4096 epochs (approximately 18 days), limiting their long-term storage footprint. The primary constraint for blobs is bandwidth, as they must be propagated across Ethereum's peer-to-peer network. To offset the bandwidth increase from EIP-7691, Pectra also introduces EIP-7623, which increases the cost of calldata to help keep overall block sizes in check.

The long-term strategy for scaling Ethereum's data throughput without exponentially increasing bandwidth demands involves a shift from a model where "every node stores all blobs" to one where "nodes store a subset of blobs and verify the rest through network sampling." Promising research and development work on this front is already underway.

The Pectra Technical Specification

The complete and detailed list of changes included in the Pectra upgrade is defined by EIP-7600. The key EIPs encompass:

The full Python specifications for the execution and consensus layers can be found in these client versions:

Furthermore, Pectra includes updates to the Engine API, which facilitates communication between consensus and execution layer nodes.

Activation Timeline

The Pectra network upgrade is set to activate on the Ethereum mainnet at the start of epoch 364032, which occurs on May 7, 2025, at 10:05:11 UTC.

This follows successful activations on the Holesky, Sepolia, and Holešovice (Hoodi) testnets, which are used to simulate the upgrade process and identify any potential issues in a controlled environment.

Client Versions for Mainnet

Node operators must update their client software to compatible versions to follow the upgraded chain. The following client versions support the Pectra upgrade on the Ethereum mainnet.

When running a validator, it is crucial to update both the consensus layer beacon node and the validator client software.

Execution Layer Client Versions:

Consensus Layer Client Versions (Beacon Node / Validator):

Please note: Specific version numbers for mainnet are typically finalized closer to the upgrade date. Operators should monitor official client repositories and announcements for the exact versions to use.

👉 Get the latest blockchain node tools

Frequently Asked Questions

What do I need to do as a regular Ethereum user or ETH holder?
In short, nothing. If you use an exchange, custodial wallet, or hardware wallet, your service provider will handle the necessary updates. No action is required on your part unless your provider specifically notifies you.

What is required of a non-staking node operator?
To ensure compatibility with the upgraded network, you must update your execution layer and consensus layer client software to the versions specified for the Pectra upgrade once they are released.

What steps should a staker (validator) take?
As a validator, it is critical to update both your execution layer client and your consensus layer client (which includes both the beacon node and the validator client software) to the compatible versions. Failure to update will result in being left on the pre-fork chain and incurring inactivity penalties.

How do Ethereum network upgrades actually work?
Ethereum upgrades require node operators to explicitly opt-in by updating their client software. While client developers agree on a consensus set of EIPs to include, they are not the ultimate decision-makers. For an upgrade to succeed, the majority of validators and nodes must voluntarily update their software. If a significant number of nodes do not update, it can cause a network split. This voluntary participation is a core feature of Ethereum's decentralized governance model.

Why is the upgrade named "Pectra"?
Ethereum upgrades follow a naming convention that combines a name from the execution layer and one from the consensus layer. The execution layer name is typically a Devcon city, and the consensus layer name is a star or constellation. "Pectra" is a portmanteau of Prague (host city of Devcon IV) and Electra, a blue-white giant star in the Taurus constellation.

What should application or tooling developers do?
Developers should review the EIPs included in Pectra to assess their impact on existing projects. This upgrade introduces many exciting new features on both the execution and consensus layers that could enable novel functionalities and optimizations.