EIP-8133 Network upgrade naming convention (Network Upgrade Naming)

No call decision · Other · EIP status Review · created 2026-01-23

A reference document summarizing the conventions by which Ethereum network upgrades have been named. Without changing the protocol, it serves as an official record of the execution layer city names, consensus layer star names, combined names, and BPO numbering conventions.

Why it is needed

Ethereum has gone through several major upgrades, including the transition from proof-of-work to proof-of-stake (the Merge), and each upgrade received its own name. After the first few, a consistent naming convention took hold, but that convention was never written down in a single document. Now that upgrades happen more frequently, and a single upgrade spans both the Execution Layer and the Consensus Layer, it can be hard to tell from the name alone which upgrade is being referenced or how they relate to each other. For example, portmanteau names like Shapella and Pectra are used alongside layer-specific names like Shanghai and Capella. This EIP does not create a new convention; it documents an already-established practice so the ecosystem can communicate with a shared vocabulary and reduce confusion and guesswork. It does not bind future naming decisions.

What changes

Today

After EIP-8133

Who is affected

In depth

Early upgrades and historic city names

Early upgrades used names that reflected the network's experimental state, a milestone, or a feature theme. These include Frontier (Genesis), Frontier Thawing, Homestead, the DAO Fork (DAO Wars, which was halted), Tangerine Whistle, and Spurious Dragon. Tangerine Whistle conveyed the urgency of responding to a denial-of-service attack (an emergency whistle), while Spurious Dragon referred to clearing out the millions of empty accounts created by that attack. Later, during the Metropolis development phase, historically connected city names were adopted: Byzantium, Constantinople, St. Petersburg, and Istanbul, symbolizing the protocol's gradual maturation much as Byzantium became Constantinople and then Istanbul. Constantinople and St. Petersburg activated at the same block height, with St. Petersburg serving to guarantee the removal of EIP-1283.

Glacier names: dedicated difficulty bomb upgrades

Upgrades whose main purpose was to delay the Difficulty Bomb used glacier names: Muir Glacier, Arrow Glacier, and Gray Glacier. These were named after glaciers that are actually retreating, symbolizing a temporary delay of the mining difficulty spike known as the 'Ice Age' to buy time before the transition to proof-of-stake. The fact that Gray Glacier is a glacier formed by merging with another glacier was a deliberate hint at the approaching Merge. These names signaled functional scope rather than feature expansion.

Execution Layer: Devcon/Devconnect host cities

Execution Layer upgrades may use the name of the city that hosted a Devcon or Devconnect event. Observed examples are Berlin (Devcon 0), London (Devcon 1), Shanghai (Devcon 2), Cancún (Devcon 3), Prague (Devcon 4), Osaka (Devcon 5), Amsterdam (Devconnect 1), and Bogotá (Devcon 6). The one exception is Paris, included in the Merge, which was named to commemorate EthCC, the first and largest Ethereum community conference. Past and announced host cities also include Istanbul, Bangkok, Buenos Aires, and Mumbai. This convention provides geographic neutrality, cultural diversity, and a predictable sequence usable for roadmap planning.

Consensus Layer: alphabetically ordered star names

Since the launch of the Beacon Chain, Consensus Layer upgrades must use star names in alphabetical order. Each name must be a star name accepted by rough consensus. Altair, activated in October 2021, was the first Consensus Layer upgrade and the baseline for this convention, followed alphabetically by Bellatrix, Capella, Deneb, Electra, Fulu, Gloas, and Heze. This convention provides predictability in upgrade ordering, a clear distinction from the Execution Layer, long-term scalability without reusing names, and a shared vocabulary for developers, client teams, researchers, and operators.

The Merge is a special case

The Merge is a special case both in its name and in how it activated. Unlike later upgrades, the two layers did not activate simultaneously but proceeded in stages, and no portmanteau name was adopted. The Consensus Layer upgrade Bellatrix activated first on the Beacon Chain on September 6, 2022 (Epoch 144896), preparing for the Execution Layer transition. The Execution Layer upgrade Paris then activated when the network reached its predetermined Terminal Total Difficulty (TTD) at 06:42 UTC on September 15, 2022. This completed mainnet's transition from proof-of-work to proof-of-stake at block 15,537,393. While the transition was completed on September 15, the process began with Bellatrix on September 6, and the official name for this event is The Merge.

Portmanteau names are for reference only

After the Merge, Execution Layer and Consensus Layer upgrades can activate simultaneously within a single network upgrade. In this case, each layer keeps its own naming convention, and the ecosystem may additionally use a portmanteau name combining both. Observed examples are Shapella (Shanghai+Capella), Dencún (Deneb+Cancún), Pectra (Prague+Electra), Fusaka (Fulu+Osaka), Glamsterdam (Gloas+Amsterdam), and Hegotá (Heze+Bogotá). Portmanteau names are purely informational, intended to ease communication, and must not replace the official layer-specific names used in specifications, client implementations, and protocol documents.

BPO upgrades are named by sequence number

Blob-Parameter-Only (BPO) upgrades change only blob-related parameters, such as the blob target and maximum, without including any other protocol changes. They serve as a mechanism to progressively achieve the Surge roadmap's data availability scaling goals with low operational risk. The name follows the format BPO<n>, where n must be a monotonically increasing positive integer starting from 1. Observed examples are BPO1, BPO2, and BPO3. Descriptive names were deliberately avoided because sequence numbers directly convey ordering and fit the single-purpose, standardized nature of these upgrades. This convention is specified in EIP-7892 and applies to upgrades limited to blob parameter adjustments. A BPO can be deployed on its own or alongside a larger upgrade.

A non-binding Informational document, still in Review status

This EIP is of Informational type, involves no protocol changes, and has no security considerations. It does not bind future naming decisions and merely records established practice and current conventions. Future upgrade names will continue to be determined through community coordination and can be found in the upgrade-specific Meta EIPs. Since the current status is Review, the content of this document may still change.

Original EIP · ← EIPs