Pectra went live on 7 May 2025. Its wallet delegation, validator balances and larger blob capacity changed different parts of Ethereum in different ways.

Pectra reached mainnet on 7 May 2025

Ethereum activated Pectra at epoch 364,032 on 7 May 2025, at about 10:05 UTC. The name joins Prague, the execution-layer upgrade, with Electra, its consensus-layer counterpart. It followed Dencun and bundled changes affecting wallet accounts, validators and rollup data.

Your ETH didn’t need replacing.

Existing ETH stayed in the same accounts. Pectra changed what the protocol could support; individual wallets and services still had to build the features people would actually use.

• Ethereum.org | activation record

What EIP-7702 gives a wallet

EIP-7702 lets an externally owned account authorise delegation to contract code, opening up features previously associated with smart-contract wallets while keeping the account address that its owner already uses to receive and hold assets. A wallet can support bundled operations, such as a token approval followed by a swap in one transaction.

Fee sponsorship is another possibility: a different account pays the network cost. The transaction still consumes gas. Whether a service sponsors it, charges another token or leaves the user paying ETH depends on that service’s implementation. Signing the delegation also needs care because the selected code will operate in the account’s context.

• EIP-7702 | account delegation and wallet features

The validator ceiling rose to 2,048 ETH

EIP-7251 increased the maximum effective balance of a validator from 32 to 2,048 ETH. The minimum stayed at 32 ETH. That difference matters: the upgrade did not suddenly require a solo validator to find another 2,016 ETH.

The proposal allows eligible validators to consolidate and supports compounding balances. For an operator, fewer validator identities can mean less signing and messaging overhead. The larger ceiling is an option within the new rules, with its own consolidation and withdrawal-credential requirements; it doesn’t automatically merge every existing validator.

• EIP-7251 | effective balances and consolidation

Rollups received more room for data

Blobs hold the data that rollups need to make their activity available through Ethereum. EIP-7691 doubled the target from three to six blobs per block and raised the maximum from six to nine. Those are Pectra’s historical settings, not a claim about every later upgrade.

A target and a maximum do different jobs. Six was the level the pricing mechanism worked towards; nine was the block ceiling. More available blob capacity gave rollups additional headroom, but a capacity change alone can’t tell a user the fee a particular application will quote.

• EIP-7691 | blob targets, limits and pricing

Withdrawal control changed too

EIP-7002 added execution-layer-triggered exits and withdrawals using eligible withdrawal credentials. It addressed a specific separation of control: the key performing validator duties and the credential controlling the withdrawn funds could belong to different parties.

With the new mechanism, the withdrawal side gained a protocol route to request an exit. Requests still follow the relevant processing rules. The practical question for a staking service became which credentials it used and who controlled them, alongside whether its software exposed the new route clearly.

• EIP-7002 | withdrawal-triggered exits

Why one headline cannot describe the whole upgrade

A wallet user may encounter fewer separate transaction approval prompts when a service bundles operations. A validator operator may use consolidation, while a rollup developer gains data capacity. These features require support from the relevant wallet or service, so the protocol upgrade did not make every application look different the next morning.