Ethereum 2.0 Upgrades Explained: What Changed by 2026

Ethereum 2.0, often written ETH 2.0 or Eth2, was the informal name for a set of upgrades meant to replace the original proof-of-work consensus with proof of stake. Under proof of work, miners secured the chain with computing power. Under proof of stake, validators lock up ETH as a bond and are selected to propose and attest to blocks.

The plan also included scaling work, such as data sharding, to lower costs for rollups and the apps built on them. Over time the project was split into two parts that developers often describe as layers:

• The consensus layer decides which blocks are valid and how validators agree on the chain. It runs on the Beacon Chain and later on the proof-of-stake logic.
• The execution layer handles transactions, smart contracts and account balances, as it did before the change.

The name was used heavily in 2019 and 2020, when news coverage tracked launch dates and deposit totals. Once the two parts were joined, the 2.0 label mostly faded. Many older articles still use it, so when you see the term, read it as a description of the plan rather than a separate network you can switch to.

Most of the coverage available on this topic dates from 2020 to 2022. It is useful history, but it does not describe the network as it works now. Several reports from that period focused on how much ETH had been deposited into the deposit contract for the first phase, and whether that total would be reached in time for a planned launch date. Other pieces speculated that a launch could prompt people to sell ETH, a view that did not clearly play out.

The pattern in those reports is worth remembering. Dates moved, and the milestones were measured by deposits and code readiness rather than by a fixed calendar. A launch date in the news was often a target, not a guarantee.

The first major piece went live on December 1, 2020, when the Beacon Chain started as a separate proof-of-stake chain. It did not process ordinary user transactions at first. That separation is the reason the network had two chains for a time, and it explains why later steps were needed to combine them.

If you are reading an older article, check its date and whether it describes a planned event or a completed one. For current status, the official Ethereum documentation and client release notes are more reliable than news items written during the transition.

The transition happened in stages rather than in a single switch. The milestones below are listed for orientation. Confirm the exact changes and activation details on official Ethereum sources before relying on them:

• Beacon Chain launch (December 2020): started the proof-of-stake consensus layer alongside the existing chain.
• The Merge (September 2022): joined the execution chain to the proof-of-stake consensus layer and ended proof-of-work mining on Ethereum.
• Shanghai and Capella upgrades (April 2023): enabled withdrawals of staked ETH and accrued rewards, so validators could exit and take funds out.
• Dencun upgrade (March 2024): added blob data space for rollups, which was intended to reduce the cost of posting their data to Ethereum.
• Pectra upgrade (2025): introduced several changes to validators and account features. Read the official summary for the full list.

Each of these steps was delivered as a hard fork. A hard fork changes the rules that every node must follow, so every participating node needs compatible software before the activation point. Nodes that do not upgrade can fall out of step with the rest of the network.

Later upgrades were named after the planned changes in each set of improvements, and the network continues to evolve. Treat any list like this as a snapshot and check the current schedule before you plan around it.

Ethereum's software is made of two kinds of clients. Execution clients process transactions and state. Consensus clients follow the proof-of-stake rules and manage validators. Several independent teams build each kind, which is one reason the network can survive a bug in one implementation.

A minor code release is usually one of three things: a bug fix, a performance improvement, or a change to how a single client works internally. Many minor releases do not change consensus rules at all. They can be installed on their own schedule, and most users never notice them.

A protocol change is different. It needs an agreed activation point, such as a specific epoch or block number, and it may be scheduled for a test network first. Test networks let client teams and node operators check that the new rules work before the main network follows them.

To tell which kind of release you are looking at, read the release notes. Look for language about a mandatory update, an activation time, or a required version for a fork. If the notes mention a new fork name or a schedule, treat it as a protocol change. If they list fixes and performance work only, the update is usually simpler to apply, though you should still install it from the official source.

If you run a validator or a node, a release is your responsibility, and the steps are straightforward:

1. Identify both clients you run, the execution client and the consensus client, and note their current versions.
2. Read the release notes for each client and check whether the update is described as mandatory or optional.
3. If the release sets an activation point, make sure your node is upgraded before that point.
4. Update the execution and consensus clients together when the notes say they must match, and restart each service in the order the documentation describes.
5. Watch your node after the update for sync problems, peer issues or missed duties, and check logs for version warnings.
6. Back up your validator keys and keystore files securely before you change anything. Never share them with a third party.

Keep a record of versions and dates so you can compare your setup with the release timeline if something goes wrong. If you are unsure, test changes on a test network or ask in the official client community channels, but verify any advice you receive against the documentation first.

A validator that falls behind can miss duties, and a node that is on an outdated version can fall out of sync. Planned maintenance is far less risky than an emergency fix made under pressure, so schedule updates when you can watch them.

For most people who only hold ETH or use apps, a minor patch changes very little. Wallets and exchanges update their own software and handle the technical side. You do not need to run a node to hold ETH safely, and you do not need to take action just because a release exists.

The exceptions are worth knowing about. Exchanges sometimes pause deposits or withdrawals for a short period around a significant network change, so check the status page of any platform you use before you move funds. DeFi protocols may also pause or adjust their markets during an upgrade. Official notices from the app itself are the place to check.

If you hold a liquid staking token, the token itself stays in your wallet, but its price can move relative to ETH. Liquid staking tokens such as stETH from Lido or rETH from Rocket Pool are issued by smart contracts, so your exposure includes the performance and security of those contracts. The price of a liquid staking token can also drift from the price of ETH, especially during periods of heavy withdrawals.

For a fixed record of your position, keep the transaction history and the contract addresses you used. This makes it easier to reconcile balances later and to check that you are dealing with the genuine token.

Staking is one of the main reasons people follow proof-of-stake upgrades closely. The options differ in control, cost and risk. The table below gives a simple comparison:

Option	Control	Typical starting amount	Main risk
Solo validator	Full control of keys and node	32 ETH per validator	Technical errors, downtime, key loss
Liquid staking protocol	Token received, protocol holds stake	Set by the protocol	Smart contract risk, token price drift
Exchange staking	Platform holds the assets	Set by the platform	Counterparty risk, terms changes

Solo staking is the most direct form of participation. You run the clients, keep your keys safe, and manage upgrades yourself. It rewards careful operation but requires ongoing attention.

Liquid staking protocols such as Lido and Rocket Pool pool stake from many depositors. Rocket Pool also lets node operators run validators with a smaller ETH bond than solo staking requires, in its own design. These services add a layer of smart contracts and governance, so read their documentation and fee structure before you deposit.

Exchange staking is the simplest route but gives you the least control. Check whether the platform is regulated in your jurisdiction, what the terms say about withdrawals, and how rewards are calculated. Reward rates change, so look up current figures on the service itself rather than relying on a number written in a guide.

Upgrade periods attract scams, because people expect action and sometimes expect rewards. Protect yourself with a few habits:

• No genuine upgrade asks for your seed phrase, private key or a transfer of ETH to a personal address. Treat any request like that as a theft attempt.
• Verify every link against official documentation that you found yourself, and bookmark the sites you trust.
• Be suspicious of unsolicited messages, direct messages from people claiming to be developers, and posts promising a special token for taking part in an update.
• Use a hardware wallet for significant holdings, and keep your recovery phrase offline.
• Review token approvals in your wallet and revoke any you no longer need, using a reputable approval-management tool.
• Keep your wallet, browser and operating system updated from official sources only.

If you already shared a seed phrase or signed a transaction you do not understand, move remaining funds to a new wallet you control and seek help from the wallet provider. Acting quickly reduces losses, but a scammer may already have access, so assume the old wallet is compromised.

No legitimate release requires you to send ETH to start the process. If an announcement creates urgency, that is a reason to wait and verify.

A practical way to follow Ethereum releases is to build a short routine rather than reacting to every headline. Consider this checklist:

1. Bookmark the official Ethereum documentation and the release pages for the clients you use.
2. Check the fork or upgrade schedule on official sources, and note whether any test network has already run the change.
3. Subscribe to the notice channels of the exchanges, wallets and protocols you depend on.
4. Record your own setup, including which clients, wallets and staking services you use.
5. Review your positions after any scheduled change, especially if you rely on a liquid staking token or a lending market.
6. Ignore price predictions tied to an upgrade date. Markets often move before an event and do not always follow the expected pattern.

For lending and borrowing, a protocol such as Aave V3 or Compound V3 may publish its own notices about markets and risk settings. Check those notices before changing positions. Keep in mind that DeFi activity carries smart contract, liquidity and price risks whatever the network is doing.

The aim is to act on verified information, at the time that matters to you, and to avoid decisions made from speculation about a launch that has already happened.