EIP-7600 Pectra hard fork meta (Hardfork Meta - Pectra)

Final · Other · EIP status Final · created 2024-01-18

A document that compiles in one place which EIPs are included in the Prague/Electra (Pectra) network upgrade. It records 10 core EIPs, 2 other EIPs, and activation timing for each network.

Why it is needed

Ethereum applies multiple proposed changes together in a single network upgrade (hard fork). Pectra bundles together more than 10 EIPs of varying character, including changes related to validators, fees, and account functionality. If each of these changes were documented separately, it would be hard to see at a glance exactly what is included in this upgrade. Client development teams need a list of what to implement, and users and app developers need a reference document to check what is changing. This meta EIP provides a single document listing all EIPs included in Pectra, pointers to the full specifications, and activation timing on testnets and mainnet. It follows on from EIP-7569, which documented the previous upgrade, Dencun.

What changes

Today

After EIP-7600

Who is affected

In depth

10 core EIPs

Pectra's core EIPs are the following 10: EIP-2537 (BLS12-381 curve operation precompiles), EIP-2935 (storing historical block hashes in state), EIP-6110 (supplying validator deposits on-chain), EIP-7002 (execution-layer-triggered validator exits), EIP-7251 (raising MAX_EFFECTIVE_BALANCE), EIP-7549 (moving committee index out of Attestation), EIP-7623 (increased calldata cost), EIP-7685 (general purpose execution layer requests), EIP-7691 (increased blob throughput), and EIP-7702 (setting EOA account code). Changes spanning validator lifecycle, fees, account functionality, and cryptographic operations are all bundled into one upgrade.

2 other EIPs and the support obligation for EIP-7642

Two more EIPs are included beyond the core set. EIP-7840 is an Informational document that adds the blob schedule to execution layer (EL) configuration files. EIP-7642 is the networking protocol eth/69, which removes fields that were only used prior to the Merge. EIP-7642 is not required for the Pectra upgrade itself, but the source text specifies that client teams MAY support it up until Pectra activation and MUST support it through the following network upgrade.

Location of the full specifications: consensus layer and execution layer

EIP-6110, EIP-7002, EIP-7251, EIP-7549, EIP-7685, and EIP-7691 require consensus layer changes. These EIP documents contain an overview, and the full specifications live in the specs/electra and specs/_features directories of the ethereum/consensus-specs repository. On the execution layer side, EIP-2537, EIP-2935, EIP-6110, EIP-7002, EIP-7623, EIP-7685, EIP-7702, and EIP-7840 require changes, and here each EIP document is itself the full specification. Some EIPs, such as EIP-6110, EIP-7002, and EIP-7685, span both layers.

Activation timestamps by network

Activation timing is recorded per network as follows. Holešky: epoch 115968, timestamp 1740434112. Sepolia: epoch 222464, timestamp 1741159776. Hoodi: epoch 2048, timestamp 1742999832. Mainnet: epoch 364032, timestamp 1746612311. The order is to activate on testnets first, then apply to mainnet.

Document status and lineage

This EIP's status is Final and its type is Meta. A meta EIP is not a document that directly changes protocol code but serves to give an overview of the entire upgrade and collect links to the full specifications. The source text's Rationale also explains the document's purpose this way. Pectra is the upgrade following Dencun, and Dencun is documented in the same manner in EIP-7569. Security Considerations are stated as none.

Original EIP · ← EIPs