Whatever Happened to Eth2? Ethereum's Naming History Explained

"Eth2" was the informal name once used for Ethereum's planned proof-of-stake, sharded future, back when it was expected to be a largely separate chain running alongside the original proof-of-work chain ("Eth1"); the community formally retired that terminology in early 2022, several months before the Merge, in favor of describing Ethereum as a single chain made of an execution layer and a consensus layer. Understanding why the naming changed also explains a fair bit about how Ethereum's actual upgrade path unfolded differently than originally planned.

Where "Eth2" came from

In Ethereum's earlier roadmap (roughly 2018-2020), the plan was structured around a separate Beacon Chain — a new proof-of-stake chain launched independently in December 2020 — that would eventually take over consensus duties from the original proof-of-work chain, alongside a sharding design intended to scale throughput significantly. Because this was conceived as a substantial, multi-phase transition, the community adopted shorthand: "Eth1" for the existing proof-of-work chain people were using every day, and "Eth2" for the new proof-of-stake, sharded system being built to eventually replace or absorb it.

This naming made sense at the time the Beacon Chain launched as a genuinely separate chain (it ran in parallel, with no user transactions or smart contracts, purely establishing and testing proof-of-stake consensus before the eventual merge with the main chain). But it created a lasting and, in hindsight, unhelpful impression: that "Eth2" was a different, forthcoming cryptocurrency or network — leading to real confusion, including scams that tried to convince people to "convert" their ETH to a separate "ETH2" token, which never existed as a tradeable asset.

Why the terminology changed

By late 2021, Ethereum's actual technical path had diverged somewhat from the original phased Eth1/Eth2 plan — sharding's design and priority shifted substantially (partly due to the rise of layer 2 rollups reducing the urgency of base-layer data sharding, and partly due to research evolving toward the EIP-4844 "danksharding" approach instead of the earlier execution-sharding design). More importantly, it became clear that when the Merge eventually happened, there would be no separate "Eth2 chain" to migrate to — the existing chain, with its existing history, accounts, and contracts, would simply switch its underlying consensus mechanism while remaining the exact same chain, same addresses, same balances, same smart contracts.

Given that reality, "Eth1" and "Eth2" were retired as confusing and, in the case of the Merge specifically, actively misleading — they implied two separate systems merging, when the Merge was actually one continuous chain changing its consensus engine underneath it. The community adopted clearer language instead:

Old terminology	New terminology	What it actually refers to
Eth1	Execution layer	The part that processes transactions and runs the EVM/smart contracts
Eth2	Consensus layer	The part that handles validator duties, block proposal timing, and finality (formerly the separate Beacon Chain)
"Merging to Eth2"	"The Merge"	The execution layer switching from producing its own proof-of-work blocks to being driven by the consensus layer's proof-of-stake

What actually happened at the Merge

Rather than users needing to migrate assets to a new "Eth2" chain, the Merge simply combined the existing execution layer (still processing the same transactions and smart contracts, with the same account balances and history intact) with the already-running Beacon Chain's consensus layer, which took over responsibility for producing blocks and reaching finality via proof-of-stake instead of proof-of-work mining. No user action was required, no tokens needed "converting," and no new chain was created — this is precisely why the "two systems merging into one new thing" framing that Eth1/Eth2 implied was misleading, and why "execution layer plus consensus layer, now integrated" better describes what happened.

Why this history still matters today

Understanding this naming shift is useful mainly for two reasons. First, if you encounter older articles, forum posts, or (worse) active scams referencing "ETH2" as if it's a separate asset you need to "claim" or "convert" to, that's an outdated or actively fraudulent framing — see our guide to common DeFi scams for how these impersonation and fake-migration scams typically work. Second, it's a useful reminder that Ethereum's actual technical roadmap evolved meaningfully from its original multi-phase plan, with sharding's specific design changing substantially in response to the success of rollup-centric scaling.

Lingering confusion in older material

Because "Eth1" and "Eth2" were the standard terminology for several years before being retired, a meaningful amount of older documentation, forum discussion, YouTube content, and even some outdated wallet or exchange interfaces still reference the old naming. If you come across a reference to "Eth2 staking rewards" or "migrating to Eth2," it's almost always describing what's now simply called Ethereum staking or the consensus layer — not a distinct, separate action you still need to take today. Genuine, current staking activity (whether running your own validator or using a liquid staking service) is just "staking ETH" in current terminology, full stop.

The rebrand also reflected a broader philosophy

Beyond just cleaning up confusing terminology, the community's preference for "execution layer" and "consensus layer" also reflects a more accurate mental model of how Ethereum is actually built today: as two cooperating but conceptually separable software layers within one single network, rather than two different blockchains or two different versions of Ethereum existing side by side. This framing has stuck and is now the standard way client teams, researchers, and documentation describe Ethereum's architecture, including when discussing further planned changes to either layer independently — for instance, EIP-4844 primarily affects the execution layer's data handling, while proposals like single slot finality are consensus-layer changes.

Bottom line

"Eth2" was retired not because the underlying technical work stopped, but because the name implied a separate chain that never actually existed at the Merge — the real event was one continuous chain integrating a proof-of-stake consensus layer that had already been running independently since December 2020. Today, "execution layer" and "consensus layer" are the accurate terms, and any reference to a separate "ETH2" token or required migration should be treated as outdated at best and a scam at worst.