0%
HomeBlogTechnical
What Is the Ethereum Pectra Upgrade? Dev Guide to 11 EIPs

What Is the Ethereum Pectra Upgrade? Dev Guide to 11 EIPs

Author: Uttam Singh


Last updated May 7, 20257 min read

The Pectra upgrade (Prague + Electra) is Ethereum’s next major hard fork & largest upgrade in terms of included EIPs, live on May 7, 2025 . It bundles 11 EIPs touching everything from smart wallet capabilities to staking mechanics and rollup data efficiency. Below we break down each improvement, explaining what changes and how it impacts you as a developer – whether you’re deploying an app, smart contracts, or your own chain.

Which EIPs are coming in Ethereum Pectra? Let’s break it down.

A breakdown of Ethereum Pectra's 11 EIPs
A breakdown of Ethereum Pectra's 11 EIPs

EIP-7702 lets a normal Externally Owned Account (EOA) temporarily execute smart contract code during a transaction. In practical terms, it introduces a new transaction type where an EOA can attach and run bytecode without permanently becoming a contract. Think of it like your plain wallet suddenly being able to behave like a full smart contract wallet for one transaction. This upgrade has been described as the “iPhone moment” for Ethereum wallets – dramatically expanding what they can do beyond just sending ERC-20 tokens or calling a contract. It is compatible with the prevailing account abstraction (AA) standard, ERC-4337, so existing wallets can become smart wallets without creating a new address and transferring assets.

For application and wallet devs with existing users, EIP-7702 is huge. It unlocks better UX flows (batching, gasless UX, social recovery logic, multi-sig authentications, etc.) directly at the protocol level. Wallet providers may need to integrate the new transaction type and provide UI for these “smart account” features.

For apps that are launching to net new users, choose ERC-4337 for the best security and features. See this guide for recommendations in detail.

Ethereum Pectra EIP-7702 summary
Ethereum Pectra EIP-7702 summary

For smart contract devs, you should be aware that some old assumptions break. Contracts that relied on tx.origin to be sure the caller was an EOA (an anti-reentrancy or anti-bot pattern) will no longer be effective.

With 7702, an EOA is tx.origin and can execute inner calls – meaning tx.origin == msg.sender checks can’t reliably distinguish “externally-called” vs “internally-called” anymore . If you have code using this pattern, consider updating it. On the flip side, you can now design contracts expecting more complex transaction logic from EOAs – for example, a dApp could assume a user might batch an approval and action together, and optimize for that.

Also if you plan to use EXTCODESIZE==0 (EXTCODESIZE is an opcode that returns the size of an account’s code) then remember EXTCODESIZE will return non-zero value post-7702, so enforcing EXTCODESIZE==0 check will block any wallet that uses 7702.

Reminder: it was already possible to Bypass Contract Size Check by external call from a contract's constructor which returns zero because no code exists at the contract address until the contract creation process concludes.

We're here to help you integrate EIP-7702. Explore smart wallet capabilities, read the implementation guide for EIP-7702, and get in touch with us for integration questions.

We have a $5M fund just for you to ship with smart wallets. Get up to $25k in credits!

Apply now

Rollup developers, this section is for you. Pectra includes upgrades to Ethereum’s data availability layer that will directly affect L2 throughput and costs. The theme is “use blobs, not calldata, and use more of them!” – continuing the momentum from proto-danksharding (EIP-4844 in Dencun) to make rollups cheaper and more efficient.

What changes:

EIP-7691 increases Ethereum’s blob-carrying capacity per block, doubling the target number of blobs from 3 to 6, and raising the maximum allowed from 6 to 9. It also fine-tunes the fee mechanics associated with blobs: the blob base fee will rise slightly less aggressively when blocks are full (~8.2% up) and decrease more sharply (~14.5% down) when blobs are scarce. This ensures fees remain stable and predictable even as blob capacity expands.

Impact:

This directly benefits rollups, allowing them to include twice as much data in each Ethereum block. Practically, rollups can either boost transaction throughput, reduce fees, or do a bit of both. Users interacting with L2 solutions like optimistic or ZK-rollups should see notably lower transaction fees or increased performance, as the data availability cost significantly influences overall transaction expenses.

What changes:

EIP-7623 strategically increases the gas cost of transaction calldata. Before blobs existed, rollups often stored compressed data directly in calldata, a method once incentivized by Ethereum. Now, Ethereum encourages rollups to fully migrate their data storage to blobs by making calldata relatively expensive.

Impact:

This economic nudge is meant to push rollups away from inefficient calldata usage toward the dedicated blob storage layer. To illustrate, think of Ethereum blocks as suitcases: normal transactions are regular luggage, while large calldata is like packing bowling balls. EIP-7623 means that heavy packers must pay significantly more, incentivizing the use of blobs, Ethereum’s specialized data compartment.

Rollup developers must update their systems accordingly. Older rollups still using calldata for data availability need to transition fully to blobs or risk substantially higher operational costs. Regular smart contracts and standard Ethereum transactions remain mostly unaffected due to their minimal calldata usage.

What changes:

EIP-7840 introduces a new object “blob schedule” within client configurations. Instead of hard-coding blob-related parameters (like target and max blobs per block) for each fork, these settings can now be adjusted via configuration files, enabling easier and more predictable network tuning.

Extend the client configuration files with the object blobSchedule with the following shape:

json
Copied
"blobSchedule": { "cancun": {"target": 3,"max": 6,} "prague": { "target": 6, "max": 9 }, "osaka": { "target": 12, "max": 16}, ... }

When there is no explicit configuration for the current fork, use the last specified fork value. If no last value is specified, set both to zero.

Impact:

This change simplifies future adjustments. For example, increasing blob capacity again in later upgrades no longer requires extensive code changes—just a simple config tweak. It provides rollups and Ethereum core developers greater flexibility and makes Ethereum’s scaling path more transparent and maintainable.

Developers operating nodes or running infrastructure should ensure their execution clients include these blob parameters correctly post-upgrade. Application developers won’t see direct impact immediately, but indirectly, they’ll benefit from smoother, more predictable scaling outcomes on Ethereum’s data availability layer.

If you’re interested in deploying a rollup or have questions about the benefits, get in touch with us.

What changes:

The Pectra upgrade introduces key improvements for Ethereum staking. Validators can now hold up to 2048 ETH per validator (EIP-7251), reducing complexity and enabling automatic reward compounding. Validators can initiate exits directly from the execution layer (EIP-7002), deposits activate faster (~13 minutes, down from hours) due to simpler processing (EIP-6110), attestation signatures become dramatically more efficient (~60× fewer verifications, EIP-7549), and a standardized communication channel between execution and consensus layers is established (EIP-7685).

Why it matters:

These changes collectively enhance the staking experience by making validator operations simpler, safer, and significantly more scalable. Fewer validators handling larger stakes mean less operational overhead and improved network efficiency. Execution-layer exits boost validator security and decentralization, while faster deposit processing improves the user experience. Standardizing cross-layer communication also lays groundwork for smoother future upgrades.

Impact on developers:

Infrastructure and staking pool developers must adjust their tools and workflows for larger validator stakes, EL-triggered exits, and streamlined attestations. Client and node operators will benefit from reduced complexity and improved network efficiency, but must update their software accordingly. General dApp developers see minimal immediate impact, but indirectly benefit from enhanced network performance and stability.

What changes:

EIP-2537 adds native Ethereum precompiles for the BLS12-381 elliptic curve, making operations like BLS signature verification and zk-SNARK proofs dramatically cheaper. Previously, these complex cryptographic checks were prohibitively expensive within smart contracts. EIP-2935 extends Ethereum’s BLOCKHASH history from ~1 hour (256 blocks) to ~27 hours (8192 blocks), enabling contracts to reference recent past blocks directly onchain.

Why it matters:

EIP-2537 empowers developers to build advanced cryptographic applications directly on Ethereum—such as zk-rollups, onchain light client proofs, trustless bridges, and privacy-preserving contracts—at significantly lower gas costs. Meanwhile, EIP-2935 addresses Ethereum’s short-term memory limitation, supporting use-cases requiring reliable onchain historical references, like enhanced randomness generation, verifiable proofs, and rollup fraud proofs.

Impact on developers:

Smart contract developers gain powerful, efficient tools for onchain cryptography (EIP-2537) and broader access to recent historical data for contract logic (EIP-2935). Applications involving advanced cryptographic schemes—DAOs with aggregated BLS signatures, zk-based privacy apps, or onchain verification systems—become significantly easier to implement. Additionally, contracts depending on recent block hashes for randomness or validation can now reliably access onchain data, simplifying their designs and reducing external dependencies.

The Pectra upgrade went live on May 7, 2025. As with previous Ethereum hard forks, the exact timing depends on block production rates, but ecosystem participants and developers should prepare their systems ahead of this target date.

The standout features of Pectra include:

  • Temporary smart contract capabilities for regular wallets (EIP-7702), described as the "iPhone moment" for Ethereum wallets

  • Doubling blob capacity from 3 to 6 per block to make rollups more efficient and cost-effective

  • Increasing max validator capacity from 32 to 2048 ETH for simpler validator operations

  • Adding native support for BLS12-381 cryptography, making advanced crypto applications viable onchain

  • Extending the block history reference from ~1 hour to ~27 hours for enhanced smart contract functionality

Pectra's impact varies by developer focus:

  • App and wallet developers gain powerful UX capabilities through EIP-7702's smart account features

  • Smart contract developers need to review code that relies on tx.origin checks or EXTCODESIZE==0 assumptions

  • Rollup developers should migrate fully from calldata to blobs for optimal cost efficiency

  • Infrastructure providers need to update clients for new blob parameters and validator operations

  • Cryptographic application developers can implement previously impractical zk-SNARKs and BLS signature schemes

Pectra builds upon Dencun's proto-danksharding foundation but takes a broader approach. While Dencun primarily focused on introducing blobs for data availability (EIP-4844), Pectra addresses multiple aspects of the Ethereum protocol simultaneously. It significantly enhances wallet functionality, optimizes staking economics, doubles blob capacity, and introduces native cryptographic operations. This comprehensive scope makes Pectra Ethereum's largest upgrade in terms of included EIPs, touching more facets of the protocol than previous upgrades like Dencun, Shanghai, or Paris.

The Pectra upgrade brings substantial improvements to Ethereum, delivering smarter wallets, scalable staking, powerful cryptographic capabilities, and enhanced data availability. For developers, this means more robust tools, simpler operations, and greater flexibility in building the next generation of decentralized apps. It’s a meaningful step forward—empowering you to create better user experiences, stronger solutions, and ultimately a healthier Ethereum ecosystem.

Explore resources

We’re here to help you leverage all the upgrades to build successful apps onchain.

Get in touch with our team, and let’s build!

Desktop section background image

Build blockchain magic

Alchemy combines the most powerful web3 developer products and tools with resources, community and legendary support.

Get your API key