Skip to content
Blockchain Posts

protocol

Ethereum activates Pectra at epoch 364032 — EIP-7702 ships

Pectra went live on Ethereum mainnet on May 7, 2025. Eleven EIPs ship together; EIP-7702 gives EOAs temporary contract code, EIP-7251 raises the validator effective-balance cap to 2048 ETH.

by 4 min read
protocolethereumpectraeip

Ethereum's Pectra hard fork activated on mainnet at epoch 364032 on May 7, 2025, around 10:05 UTC. Eleven EIPs ship together. The two headline changes: EIP-7702, which lets an externally-owned account (EOA) carry a contract's code for the duration of a transaction, and EIP-7251, which raises the max effective balance per validator from 32 to 2048 ETH.

What happened

Pectra is the combined execution-layer (Prague) and consensus-layer (Electra) upgrade. It clears mainnet after passing on the Holesky, Sepolia and Hoodi testnets — Holesky's finality stall in February 2025 delayed the rollout by roughly two months from the original March target.

The full EIP list, by area:

  • Account abstraction primitives: EIP-7702 (set EOA code).
  • Staking and validator UX: EIP-7251 (MaxEB to 2048 ETH), EIP-6110 (deposits via execution-layer events), EIP-7002 (execution-layer triggerable withdrawals), EIP-7549 (move committee index out of attestations).
  • Scaling: EIP-7691 (blob target raised from 3 to 6, max from 6 to 9).
  • Cryptography and execution: EIP-2537 (BLS12-381 precompile), EIP-2935 (block hash history in state), EIP-7623 (calldata cost increase).

EIP-7702 in one paragraph

An EOA can, in a single transaction, set a contract address whose code is executed in its own storage context for that transaction. The delegation is signed by the EOA's private key and lives in a new transaction type. The effect: any EOA can opt into smart-contract behavior — batched calls, sponsored gas, session keys, social recovery, spending limits — without migrating to a new address or moving funds. The delegation can be revoked.

EIP-7702 supersedes the earlier EIP-3074 proposal and was scoped down through several iterations in 2024 to remove the most contentious privilege escalations. Wallet teams (Ambire, Argent, Trust, Coinbase Smart Wallet) had production support ready at fork.

EIP-7251 — validator consolidation

Before Pectra, every validator was capped at a 32 ETH effective balance. Stake above 32 ETH per validator did not earn rewards. Operators with thousands of validators (Lido, Coinbase, Binance, Kiln) paid that overhead at every layer: signatures aggregated, attestations sent, slashing surface.

EIP-7251 raises the cap to 2048 ETH. Operators can consolidate up to 64 old validators into one new one, reducing churn and the consensus-layer message load. Solo stakers see no change unless they choose to top up.

Impact

  • Wallets: EOA-to-smart-account UX without migration. Expect the first wave of consumer-facing wallets to default new users into 7702 delegation within a fork or two.
  • Stakers: Lido and the major staking providers have begun consolidation. The consensus client teams (Lighthouse, Prysm, Teku, Nimbus, Lodestar) are watching attestation message volume for the first sustained drop in years.
  • L2s: blob target up to 6 (max 9) raises rollup data throughput by roughly 2× per slot — directly compresses L2 fees on Arbitrum, Base, Optimism, Linea and zkSync, all of which post to Ethereum DA.
  • Tooling: EIP-2935's block-hash precompile gives L2s and light clients access to the last 8,192 block hashes from state, making historical verification cheaper.

What to watch

  1. 7702 delegation abuse. A signed delegation is bearer-style: if a user signs one to a malicious contract, that contract has full code authority over the EOA. Wallet warnings around delegation prompts will be the next phishing surface — expect tooling vendors (Blockaid, Forta, Wallet Guard) to publish detection rules in the coming weeks.
  2. Validator churn during consolidation. Pectra ships EIP-7002 alongside EIP-7251 so withdrawals can be triggered from the execution layer. The first big consolidations from Lido and Coinbase will stress queues; watch the activation/exit queue depth.
  3. Blob fee market. With a 6/9 target/max, blob base fee dropped sharply at fork. Whether it stays low or rebounds as more rollups onboard will set the medium-term DA pricing curve.

Context

Pectra was originally proposed as a single "Prague-Electra" fork, then split, then re-merged after the Cancun upgrade (March 2024). The Fusaka fork — successor to Pectra — is scoped around EIP-7594 (PeerDAS), the next step toward danksharding. Client teams have signalled a target of late 2025 for Fusaka testnet activation.

EIP numbers, activation slot and the client release tags are tracked at ethereum.org/roadmap/pectra.

Related stories