Pectra is the combined name for Ethereum’s Prague (execution layer) and Electra (consensus layer) hard fork — a milestone upgrade that activated on Ethereum mainnet in 2025. Pectra is one of the most significant Ethereum upgrades since The Merge, bundling over a dozen EIPs across both the execution and consensus layers. Key improvements include EIP-7702 (enabling existing EOA wallets to use smart account features), EIP-7251 (raising the maximum effective validator balance from 32 ETH to 2,048 ETH), EIP-7691 (increasing blob throughput for L2 scalability), and EIP-6110 (simplifying validator deposits). Pectra is Ethereum’s most technically comprehensive single upgrade since The Merge, addressing staking efficiency, L2 data capacity, and wallet usability simultaneously.
Key EIPs in Pectra
The following sections cover this in detail.
Execution Layer (Prague)
EIP-7702 — Set EOA Account Code (Account Abstraction)
The flagship user-facing change. Allows externally-owned accounts (EOA wallets like MetaMask) to temporarily execute smart contract code during a transaction — enabling transaction batching, gas sponsorship, and session keys without migrating to a new account address. See EIP-7702.
EIP-7685 — General Purpose Execution Layer Requests
A generic framework for passing information from the execution layer to the consensus layer — enabling future improvements requiring execution + consensus coordination.
EIP-2537 — Precompile for BLS12-381 Curve Operations
Adds a native precompile for BLS12-381 elliptic curve operations, significantly reducing gas cost for operations used in DVT, BLS signature verification, and zkSNARK verifier circuits.
EIP-2935 — Save Historical Block Hashes in State
Stores recent block hashes in the execution state, enabling contracts to access historical block hashes without an oracle — useful for cross-chain messaging and ZK proof systems.
Consensus Layer (Electra)
EIP-7251 — Increase MAX_EFFECTIVE_BALANCE
Raises validators’ maximum effective balance from 32 ETH to 2,048 ETH. This allows professional staking operations to consolidate many 32 ETH validators into fewer, larger validators — reducing the total validator set size (currently 1M+ validators) and decreasing network message overhead. Individual home stakers are unaffected (32 ETH minimum unchanged); large operators benefit most.
EIP-6110 — Supply Validator Deposits On-Chain
Eliminates the current system where validator deposit data must be relayed from the execution layer to the consensus layer through a separate Eth1-Eth2 deposit contract observation mechanism. EIP-6110 makes deposit processing happen natively in the execution layer, removing delay and complexity.
EIP-7002 — Execution Layer Triggerable Exits
Allows validator withdrawals and exits to be triggered from the execution layer (by a withdrawal credential smart contract) rather than requiring the validator key itself to initiate. Critical for staking protocols that separate depositor and validator key custody.
EIP-7691 — Blob Throughput Increase
Raises EIP-4844’s target blob count from 3 to 6 per block (max from 6 to 9), directly doubling the data bandwidth available for L2 rollups and reducing L2 transaction costs. This is the most immediate L2 scalability improvement in Pectra.
EIP-7549 — Move Committee Index Outside Attestation
Technical optimization to attestation data structure that reduces the p2p network bandwidth used by attestations — a quality-of-life improvement for validator operations.
Why Pectra Matters
The following sections cover this in detail.
L2 Scalability (EIP-7691)
L2 rollups (Arbitrum, Optimism, Base, etc.) post compressed transaction data to Ethereum as blob transactions. The number of blobs per block determines how much L2 data can be settled per Ethereum block. Pectra nearly doubles this capacity — directly translating to lower L2 fees in periods of high rollup activity.
Staking Simplification (EIP-7251)
Before Pectra, a staking operator with 1,000 validators (32,000 ETH staked) had to manage 1,000 separate validator keys, 1,000 separate attestation duties, and 1,000 separate withdrawal processes. EIP-7251 lets them consolidate into fewer validators (each with up to 2,048 ETH effective balance) — dramatically reducing operational overhead. This also reduces Ethereum’s p2p network message burden (fewer validators = fewer attestations per slot).
Wallet Usability (EIP-7702)
Account abstraction features (batching, gas sponsorship) become available to all existing EOA users without migration — potentially the most user-visible improvement in Pectra. Wallet providers (Coinbase, MetaMask, Trust Wallet) can build 7702-compatible UX that abstracts gas management away from typical users.
History
- 2023 — Pectra scoped after Dencun (EIP-4844) hard fork — planned as the next major upgrade combining execution + consensus improvements.
- 2024 — EIP selection for Pectra — Multiple rounds of discussion on which EIPs to include; EIP-7702 added relatively late (April 2024) replacing EIP-3074.
- 2024 — Testnets: Holesky and Sepolia testnet activations run; multiple rounds of bug fixes.
- 2025, May — Pectra activates on mainnet — Successfully forks Ethereum with all planned EIPs.
- Post-Pectra roadmap — Fusaka (next hard fork) planned with EOF (EVM Object Format) and Verkle tree groundwork; “Glamsterdam” follows targeting full Verkle tree state migration.
Common Misconceptions
“Pectra is primarily about Ethereum price/ETH supply.”
Pectra doesn’t change ETH’s issuance rate, burn mechanic (EIP-1559), or supply dynamics directly. EIP-7251 reduces validator count, which may marginally affect issuance, but the primary focus is infrastructure improvements, not economics.
“EIP-7251 means home stakers need more ETH.”
Home stakers can still validate with exactly 32 ETH — the minimum is unchanged. EIP-7251 only raises the maximum effective balance, benefiting large professional operators who want to consolidate validators.
“Pectra includes Verkle trees.”
Verkle tree state migration is planned for a future hard fork (post-Pectra, likely Fusaka or Glamsterdam). Pectra includes BLS precompiles and execution/consensus groundwork, but not the full state migration.
Criticisms
- Complexity risk — Bundling 10+ EIPs across both layers (execution + consensus) increases the risk of interaction bugs between changes. The Holesky testnet issues before mainnet activation illustrated this.
- EIP-7251 benefits large stakers disproportionately — Validator consolidation primarily helps professional staking operations manage fewer keys; home stakers see minimal direct benefit. Critics frame this as further professionalization of Ethereum staking.
- EIP-7702 phishing risk — Adding a powerful new EOA code delegation mechanism without broad wallet-level user education creates a new attack surface that may take years of ecosystem iteration to mitigate effectively.
- Blob increase may be insufficient — Doubling blob throughput (EIP-7691) helps short-term, but L2 activity growth may outpace the increase quickly. Full danksharding remains the long-term solution.
Social Media Sentiment
Pectra generated significant Ethereum Twitter/X discussion leading up to and following its activation — more than any upgrade since The Merge. EIP-7702 received the most retail/consumer attention; EIP-7691 was praised by L2 teams (Arbitrum, Base, Optimism official accounts all posted about reduced fees). EIP-7251 was debated in staking-focused communities: r/ethstaker discussed validator consolidation impacts for small operators; professional staking operators were uniformly positive about reduced operational overhead. Overall sentiment post-activation was positive — clean activation without major issues reinforced Ethereum’s upgrade track record.
Last updated: 2026-04
Related Terms
Sources
- Ethereum Foundation (2025). Pectra Upgrade Specification. github.com/ethereum/execution-specs.
- Buterin, V. (2024). Ethereum Roadmap Update: The Verge, Purge, and Splurge. vitalik.eth.limo.
- Ethereum Foundation (2025). Pectra Mainnet Announcement. blog.ethereum.org.
- Ethereum Cat Herders (2024). Pectra EIP Selection and Scope Discussions. ethereum-cat-herders.github.io.