EIP-7639 Discontinuing Serving Pre-PoS History (eth/70 - Cease serving history before PoS)

No call decision · Networking & nodes · EIP status Stagnant · created 2024-02-13

Adds a new version (eth/70) to the eth protocol so that execution layer clients no longer exchange pre-Paris upgrade (Merge) block data over p2p.

Why it is needed

Ethereum nodes store the entire blockchain history on disk. As of 2024, this historical data totals roughly 500GB, of which about 400GB is block data from the proof-of-work (PoW) era, predating the Paris upgrade that activated proof-of-stake (PoS). If nodes must keep storing this ever-growing historical data, hardware requirements keep rising and the barrier to running a new node keeps growing. Ethereum aims, in the long run, to cap the amount of data a node must store, and this EIP is a first step toward that goal: it prevents execution-layer clients from requesting or responding with pre-Paris block data over the p2p network.

What changes

Today

After EIP-7639

Who is affected

In depth

Applicable version and affected messages

This EIP adds a new capability version 70 (eth/70) to the eth protocol. Clients connected via eth/70 must not create or respond to p2p queries for block bodies and receipts before block 15537393 (the block at which the Paris upgrade took effect). The four affected messages are GetBlockBodies (0x05), BlockBodies (0x06), GetReceipts (0x0f), and Receipts (0x10).

Why split along the PoS boundary

The block structure changed significantly at the Merge (the Paris upgrade). Today, execution-layer client software still stores block data on disk in a form similar to the pre-PoS era, but since the Merge, the beacon chain defines the canonical chain. In other words, a single beacon block can record execution-layer and consensus-layer historical data together. This EIP holds that the distinction between 'execution layer' and 'consensus layer' may become less important over the long term, and chooses to base the boundary on the shape of the data itself rather than on client architecture.

Motivation: growing historical data volume

As of 2024, the historical data clients store has grown to about 500GB, of which about 400GB is block data from before PoS activation (the Paris upgrade). Ethereum aims, in the long run, to cap the amount of data a node must store, and this EIP is presented as a first step toward that goal.

Backwards compatibility: the full sync method changes

Once this EIP is active, nodes will no longer be able to fully sync using the devp2p network alone. Nodes that need pre-Paris block data must fetch it through a separate out-of-band path rather than p2p.

Security considerations are still empty

The Security Considerations section of the original text is left as a TODO, meaning no concrete security analysis had been filled in as of the time of writing.

Current status: Stagnant

This EIP is in the Standards Track · Networking category, written on 2024-02-13, and currently has Stagnant status. In other words, discussion is not actively progressing, and no decisions about fork inclusion or implementation timing have been confirmed. Discussion may resume or the content may change.

Original EIP · ← EIPs