Why Ethereum Called the Upgrade Pectra
“Pectra” combines Prague, the execution-layer upgrade name, with Electra, the consensus-layer name. The combined label reflects a coordinated Ethereum upgrade that changed accounts, validator operations and rollup data capacity across both layers.
Timeline
- Before mainnet: Pectra changes were tested on Ethereum test networks and implemented by execution and consensus clients.
- May 7, 2025: Pectra activated on Ethereum mainnet at epoch 364032.
- After activation: Wallets, applications and validators could adopt the new capabilities; ordinary ETH balances required no conversion.
Ethereum called its May 2025 network upgrade “Pectra” by joining two names: Prague and Electra. Prague refers to the package of execution-layer specification changes, and Electra refers to the consensus-layer changes. Ethereum coordinates these parts in one mainnet activation, so the community uses one blended name for the combined event instead of treating them as unrelated upgrades. [1][2]
The naming pattern reflects Ethereum’s architecture after The Merge. Execution clients process transactions, smart-contract state and the Ethereum Virtual Machine, while consensus clients coordinate proof-of-stake validators and agreement on the chain. A node operator generally runs software for both layers. A protocol upgrade can therefore require matched changes on each side and to the Engine API through which the clients communicate. [1][2]
“Prague” follows the execution-layer custom of using Devcon host cities; it refers to Prague, the location of Devcon IV. “Electra” follows the consensus-layer use of star names and refers to the blue-white giant star in Taurus. Combining the two produced “Pectra.” The label is convenient shorthand, but the actual upgrade is a defined collection of Ethereum Improvement Proposals rather than a single feature. [1]
One prominent proposal, EIP-7702, lets an externally owned account authorize selected smart-contract code for capabilities such as transaction batching, sponsored fees or alternative authentication. The authorization model also creates security responsibility because choosing delegation code grants it meaningful control. Users should rely on well-reviewed wallet interfaces, read transaction requests carefully and avoid signing unfamiliar authorizations promoted through unsolicited links. [1][2]
Pectra also changed validator operations. EIP-7251 raised the maximum effective balance from 32 ETH to 2,048 ETH on an opt-in basis, supporting reward compounding and validator consolidation. EIP-7002 enabled exits through execution-layer withdrawal credentials, and EIP-6110 moved validator-deposit information on-chain to reduce processing delay and remove older pre-Merge machinery. These changes matter primarily to staking infrastructure and operators. [1][2]
For rollup capacity, EIP-7691 raised the target and maximum number of blobs per block from three and six to six and nine at activation. Blobs are temporary data containers used by layer-2 systems to publish data to Ethereum. More capacity can help L2 throughput, but it does not guarantee a particular user fee because demand, application behavior and later network upgrades also affect costs. [1][2]
Ordinary ETH holders did not need to convert or “upgrade” their coins for Pectra. Ethereum.org explicitly warns that anyone instructing a holder to convert ETH because of the fork is attempting a scam. Node operators and validators did need compatible client releases, while application developers needed to review affected proposals. For future upgrades, use the current Ethereum Foundation and ethereum.org notices because client versions and operating instructions are time-sensitive. [1][2]
Sources
- Ethereum Foundation — Pectra mainnet announcement
- ethereum.org — Prague-Electra (Pectra) upgrade guide