EIP-6953 A complete rundown of network upgrade activation conditions (Network Upgrade Activation Triggers)

Final · Networking & nodes · EIP status Final · created 2023-04-28

An informational EIP that compiles, in one document, the conditions Ethereum has used to trigger network upgrades so far: block number, epoch, total difficulty, and timestamp methods.

Why it is needed

Ethereum has gone through many network upgrades (hard forks) over more than a decade, and the method for activating upgrades has differed by era. During the Proof-of-Work period, upgrades activated at a specific block number, while the Beacon Chain activated by epoch. The Merge, which ended Proof-of-Work, was triggered using a special value called total difficulty. After the Merge, the consensus layer uses epochs while the execution layer uses timestamps. With four different methods in play, understanding why they changed and exactly what value triggered each upgrade required digging through multiple EIPs and documents. The purpose of this EIP is to gather that history into a single document, giving users and developers one unified reference. It is not a proposal to change protocol rules, but a record-keeping document.

What changes

Today

After EIP-6953

Who is affected

In depth

The proof-of-work era: block number activation

All upgrades during the proof-of-work era activated at specific block numbers. Frontier was block 1, Frontier Thawing was 200000, Homestead was 1150000, the DAO Fork was 1920000, Tangerine Whistle was 2463000, Spurious Dragon was 2675000, and Byzantium was 4370000. Constantinople and Petersburg activated together at the same block, 7280000, followed by Istanbul at 9069000, Muir Glacier at 9200000, Berlin at 12244000, London at 12965000, Arrow Glacier at 13773000, and Gray Glacier at 15050000. Per the Rationale, blocks and epochs are the units at which state transitions occur on Ethereum, making them the natural activation points for upgrades.

Beacon Chain launch conditions

The Beacon Chain was designed to launch not at a single block number but once all three conditions defined in EIP-2982 are met. First, the deposit contract must accumulate at least 524288 ETH from 16384 validators. Second, the MIN_GENESIS_TIME timestamp of 1606824000 (December 1, 2020) must have passed. Third, GENESIS_DELAY, 604800 seconds, must elapse from the point the minimum validator count is exceeded. Rather than fixing a specific point in time, this is a conditional approach that launches once enough validators and deposits have accumulated.

Beacon Chain upgrades: epoch activation

Beacon Chain upgrades activate at specific epochs. Altair activated at epoch 74240, and Bellatrix at epoch 144896. Since an epoch is the unit at which state transitions occur on the consensus layer, it plays the same role there that block numbers play on the proof-of-work chain.

The Merge (Paris): total difficulty activation

The execution layer portion of the Merge, the Paris upgrade, activated not on a block number but on the condition that proof-of-work total difficulty reached 58750000000000000000000. This approach is specified in EIP-3675, which also contains the rationale for the choice. However, Paris could only activate properly on the proof-of-work chain once the Bellatrix upgrade had already activated on the Beacon Chain. Using total difficulty instead of a block number was a one-time mechanism specific to this upgrade.

Post-Merge: the dual structure of epochs and timestamps

Post-Merge upgrades activate by epoch on the consensus layer (CL), ideally aligned to a multiple of 8192 slots, a historical roots accumulator boundary. The execution layer (EL) uses the timestamp corresponding to that epoch as its activation condition instead of a block number. In the first such case, Capella (CL) activated at epoch 194048 and Shanghai (EL) at timestamp 1681338455; since epoch 194048 corresponds exactly to timestamp 1681338455, the two layers activated simultaneously despite using different constants. Additionally, once the execution layer began using timestamps, the way nodes compute FORK_HASH and FORK_NEXT values changed, a change described in EIP-6122.

Why timestamps

Because the Beacon Chain can have missed slots, the execution layer cannot use block numbers alone to activate an upgrade at precisely the same point as the consensus layer. Timestamps, by contrast, correspond deterministically to a specific epoch, making them a reliable way to keep the two layers aligned. Unix timestamp values are also always larger than the block numbers used previously, so a timestamp-based post-Merge upgrade is never interpreted as occurring at a lower value than the last block-number-based upgrade.

Scope and status of the document

This EIP is of Informational type, a record-keeping document that does not change protocol rules. It covers only the period from the proof-of-work era through Shanghai/Capella, the first post-Merge upgrade, and it is not intended to become a document that continuously records every future upgrade. Readers can assume that, unless another EIP supersedes this one, future upgrades will use the method described in the Post Merge Upgrades section, namely consensus layer epochs and execution layer timestamps. Its status is Final and will not change further.

Original EIP · ← EIPs