Ethereum never stops evolving, regularly cooking up updates and improvements to the protocol to make the network more usable and scalable, keeping its blockchain nodes performant, all without compromising security.
The next big upgrade on the horizon is Pectra, which is already in development and coming soon following the very recent Dencun upgrade.
When to expect Pectra, what’s its current development status, and most importantly how will Ethereum change after? Let’s explore, with a sneak peek at what to expect next.
Ethereum is preparing for Pectra Hardfork: Highlights
Pectra is the next big network-wide update planned for Q1 2025.
- Code changes that core developers can activate with Pectra are mainly focused on improving the user and node operator experience on Ethereum;
- Interoperability between the Consensus and Execution layers will be improved, helping the network sync faster and making it easier to scale;
- New cryptographic tools will make Ethereum more secure, especially for advanced applications like zero-knowledge proofs;
- More importantly, it's setting the stage for bigger changes: enhancing dApp developer experience, introducing PeerDAS to rollups, and transitioning to Verkle Tree structure;
- These upgrades, initially part of Pectra, are now scheduled for the next hard fork Fusaka, expected by 2026.
At the moment of writing, the exact list of EIPs (Ethereum Improvement Proposals) for Pectra is still under discussion, but the core improvements and roadmap have already been decided.
What is Ethereum’s Pectra upgrade?
Since the Merge in 2022, Ethereum operates with execution and consensus layers. To keep both in sync, major upgrades now happen in pairs — one for each layer. Hence the dual namings (e.g. Dencun with Cancun and Deneb).
“Pectra”, the upcoming major update to the Ethereum network, combines the names of the Prague upgrade on the Execution Layer (EL) activated with the Consensus Layer (CL) upgrade Electra.
Source: Ethroadmap
The goal of this Ethereum hard fork is to make Ethereum faster and easier to use, while also strengthening security and preparing for more future changes affecting scalability.
Key changes coming to Ethereum with Pectra
The Pectra upgrade's fate is determined in a series of key developer meetings: the All Core Developers Execution (ACDE) and Consensus (ACDC) calls, led by Ethereum Foundation researcher Danny Ryan and Protocol Support Lead Tim Beiko.
By the time of writing, developers have already presented new features for discussion, with eight EIPs approved to be added to Pectra:
| # | Feature | EIP | Goal |
|---|---|---|---|
| 1 | Account Abstraction | EIP-7702 | Improve user account functionality (replaces EIP-3074) |
| 2 | Store hashes of the last 8192 blocks in state | EIP-2935 | Increase the amount of past block data stored and prepare for a shift to Verkle Trees |
| 3 | Add Support for BLS12-381 Curve Operations Precompile | EIP-2537 | Boost cryptographic security of signature verifications |
| 4 | A new type of message for EL-CL communication | EIP-7685 | Easier communication between Execution and Consensus Layers |
| 5 | On-chain validator deposits | EIP-6110 | Faster and simpler validator deposits on chain |
| 6 | Execution layer triggerable withdrawals for validators | EIP-7002 | More flexible validator withdrawal options |
| 7 | Increasing MaxEB | EIP-7251 | Increase validator staking limit |
| 8 | Move Committee Index outside the Attestation message | EIP-7549 | Faster consensus, more resilient network |
To dive deeper, check out the detailed review of each item below.
Prague upgrade
Ethereum Prague upgrades primarily impact EVM, the very heart of the execution layer of the network where smart contracts operate.
Here’s a list of changes suggested for this part of the Pectra fork.
EIP-7702
Proposed by Vitalik Buterin, this EIP introduces a new way to allow regular Ethereum accounts (EOAs) to act like smart contracts.
EIP-7702 supports features similar to the previously considered EIP-3074, such as batched and sponsored transactions, but instead of introducing new opcodes, it creates a new transaction type.
Source: Ethereum Improvement Proposals, no. 7702
Users will be able to add code to the transaction; once completed, the account goes back to being a regular EOA with no permanent changes.
The proposal will allow Ethereum developers to experiment with permission schemes, potentially enabling various use cases and features like account recovery or multi-sig setups. Ultimately, this empowers to build more user-friendly applications, reduce the friction for end users, and improve adoption.
EIP-2935
This EIP proposes to expand the number of historical block hashes that Ethereum’s state stores, from the current limit of 256 blocks up to 8196 blocks.
The proposal is a precursor to the upgrade from the Merkle Tree system to Verkle Trees, a part of Ethereum’s roadmap for improving the way it handles data storage and validation.
When implemented, Ethereum nodes will be able to sync to the blockchain faster and take less time to verify the blockchain’s state.
EIP-2537
EIP-2537 introduces a new precompile to the Ethereum Virtual Machine (EVM) to support cryptographic operations using the BLS12-381 curve. This will allow developers to perform signature verifications and other cryptographic functions with higher security and better performance.
EIP-7685
EIP-7685 introduces a framework for communication between the Execution Layer and the Consensus Layer by enabling execution layer-triggered requests.
These are special messages that allow smart contracts on the execution layer to trigger actions handled by the consensus layer. It simplifies the interaction between the two layers. Examples include deposit, exit, and withdrawal requests.
Electra upgrade
Ethereum’s Electra upgrade impacts the consensus layer also called the Beacon chain but still either requires some changes to the execution layer or impacts it.
EIP-6110
Aims to improve the Ethereum deposit mechanism by directly adding validator deposits into execution layer blocks.
Currently, when a validator initiates a deposit on the execution layer, it can take up to 16 hours for the consensus layer to acknowledge and process the transaction. With this improvement, validator deposits can be processed almost immediately.
EIP-7002
EIP-7002 proposes that Ethereum validators can initiate exits (i.e., complete withdrawals from staking) using either their active key or their withdrawal key. Currently, only the active key can trigger the action.
The feature is particularly important for staking pools and smart contracts that hold stakes on behalf of multiple users as it allows to trigger withdrawals more securely.
EIP-7251
EIP-7251 would allow Ethereum validators to stake more than the current 32 ETH cap, increasing the maximum effective balance to 2,048 ETH.
This means validators can run a single validator instance with a staked balance above 32 ETH and earn rewards proportionate to this larger stake, without needing to run multiple nodes.
EIP-7549
The proposal simplifies validator voting processes and optimizes the space used for on-chain attestations. It will speed up the consensus process, enabling the network to verify blocks more quickly and with lower computational cost.
Other enhancements discussed for Pectra upgrade
With PeerDAS excluded from Pectra, developers are exploring alternative upgrades to Ethereum’s data availability (DA) layer to allow further rollup scaling:
EIP-7762: Increase the minimum base fee per blob gas to prevent price spikes;
EIP-7623: Raise call data costs to limit block sizes, ensuring that stakers can continue to produce and propagate blocks;
EIP-7742: Allow the consensus layer to dynamically set the blob transaction limit, simplifying future upgrades without needing changes to the execution layer;
EIP-7781/7782: Reduce block creation time (slot time) from 12 to 8 seconds, increasing transaction throughput and speeding up confirmation times by 30%;
EIP-7783: Introduce a mechanism for gradually increasing the gas target, allowing more transactions in each block over time.
These EIPs are being considered for inclusion in Pectra, though none are finalized at this stage.
Node minimum requirements
Another topic of discussion is defining minimum specifications – hardware, software, and bandwidth needed for running an Ethereum node.
Since these requirements may change with future network upgrades, having clear and up-to-date guidelines is very necessary and may be prioritized by Ethereum core developers.
If you're looking to skip the hassle and just want a seamless way to interact with Ethereum, GetBlock offers reliable RPC node access to 50+ blockchains. No need to worry about requirements, network upgrades, or maintenance. Simply create a user account and try instant, high-performance access to the networks you need.
When is Pectra? Date and timeline
The development of Ethereum's Pectra will go through several phases before its official release:
- The upgrade is currently progressing through Devnets (developer networks), where changes are being tested in a controlled environment, currently at Devnet 4;
- The Pectra testnet will be launched prior to Devcon 2024, where attendees can test new features, and build applications on the new upgrade;
- By early 2025, the finalized and approved changes should be tested on public Ethereum testnets Sepolia and Holesky.
This is when the date for Pectra's mainnet release should be clear, currently targeted for Q1 2025.
What’s next after Pectra
Originally, the Pectra upgrade contained more than 20 EIPs, but on September 19, 2024, developers decided to split it into two hard forks due to complexity.
The first part (Pectra) will include a limited set of EIPs described above, and the more complex changes will be delayed until the second hard fork.
The follow-up to Pectra, originally part of the same upgrade, is now named Fusaka (Osaka - Fulu) and is expected to be released later, possibly in 2026.
Source: Ethroadmap
The main focus for the next upgrade is prioritizing rollup scaling with PeerDAS and enhancing smart contract functionality.
N.B.: For a more detailed look at zero-knowledge technology and how rollups are shaping the future of Ethereum, check out our dedicated article.
PeerDAS
The main change in Dencun completed in March 2024 was EIP-4844. It introduced blob transactions—specialized data storage within Ethereum blocks for rollups. This lowered rollup transaction fees significantly but didn't fully meet the demand for data availability.
Rollup fees post-Dencun, Source: Galaxy Research
PeerDAS is the next step in which Ethereum developers are trying to expand Ethereum’s data availability capabilities and make rollups even more cost-efficient.
It is expected to increase the number of blob transactions that can be attached to a block from a target of 3 blobs per block to 64 or more. Adding data availability sampling will prevent overloading nodes while increasing capacity.
EOF
The EVM Object Format (EOF) is a long-awaited upgrade to Ethereum that will impact how smart contracts are executed on Ethereum. Since it’s too large of an overhaul, it’s now pushed back to Fusaka.
This is aimed at better smart contract security and makes the EVM more upgradeable and developer-friendly.
Source: Inevitable Ethereum
EOF consists of about 10 EIPs that collectively modernize how the EVM operates. One of the features proposed is introducing a versioned container format for EVM bytecode, separating code and data sections in contracts.
Conclusion
Pectra, which initially was planned to be a “mega hard fork,” turned out to be a less intensive overhaul of the network. Nevertheless, it explores ways to increase transaction throughput, improve user experience, and keep a strong focus on security.
With the majority of EIPs related to blobs and EVM functionality postponed until the next hard fork —likely slated for 2026—the developer community will have to wait a bit longer for truly transformative updates.
