Skip to article
Degrees of SatoshiFollow the connections.
SearchTrace an address
Degrees of Satoshi/ Encyclopedia

Encyclopedia Ethereum · Entry 274

How Ethereum upgrades: proposals, client releases and activation

AI-assisted research · separate automated verificationCorrections

Theme
Ethereum
Sources
3 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for How Ethereum upgrades: proposals, client releases and activation
FactDetailSource
ProposalEIPs document standards or proposed changes and their rationale.[1]
CategoriesApplication standards and core protocol changes are different EIP categories.[1]
ActivationImplementation and network activation are separate from publishing a proposal.[2]
01

A specification is one part of deployment

An author can propose a change and receive community and client-team feedback. Core changes then need implementation and testing across compatible clients, followed by coordinated activation. Not every proposed feature follows through to mainnet.

An application-level ERC can standardize a contract interface without requiring a core network fork. Read the proposal category before assuming its existence changes Ethereum itself.

02

Testnet support does not prove mainnet support

Suppose a new transaction behavior has been implemented and tested on a development network. A wallet targeting mainnet still needs to know whether mainnet has activated that rule and whether the relevant client and tooling support it.

Conversely, a mainnet node missing a required upgrade can disagree with the network after activation. Node operators should follow their client’s release and upgrade guidance.

03

Coordination happens through more than token voting

Ethereum core governance uses offchain discussion among developers, operators, users and other stakeholders. It is not a single onchain vote that automatically rewrites every node’s software.

For a current feature claim, record the network and activation context. A date attached to an EIP’s creation is not its deployment date.

Direct answers

Questions people ask

Does an EIP marked Final mean every chain has deployed it?

No. EIP status describes the specification process. Actual behavior depends on the proposal type and the implementation or network using it.

Must every Ethereum user manually upgrade ETH tokens?

Protocol upgrades concern software and network rules. The Merge, for example, preserved ordinary ETH balances without requiring a token conversion. Check a specific upgrade’s official guidance.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

An Ethereum network upgrade changes protocol rules through a coordinated process of proposals, review, implementation, testing and node adoption. An EIP number or draft does not mean a feature is live. Check the proposal’s scope and status, the network’s activation and the client version before relying on a behavior described in a future upgrade.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Proposal: EIPs document standards or proposed changes and their rationale.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Categories: Application standards and core protocol changes are different EIP categories.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Activation: Implementation and network activation are separate from publishing a proposal.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Revision history
  1. — First publication after primary-source research and separate automated verification.

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. Ethereum Improvement Proposal processEthereum Improvement Proposals

    Specification stages are distinct from network upgrade deployment.

    Locator: EIP types; workflow; status · Version / scope: EIP-1 · Retrieved: 2026-10-02T18:55:26.643ZOpen source
  2. Ethereum governanceethereum.org contributors

    Offchain proposal discussion, client implementation and node adoption.

    Locator: Governance process; stakeholders; network upgrades · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:26.750ZOpen source
  3. The Mergeethereum.org contributors

    Consensus transition preserved execution balances and transaction history.

    Locator: Merging with Mainnet; misconceptions · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:26.611ZOpen source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

Degrees of Satoshi editorial project. “How Ethereum upgrades: proposals, client releases and activation.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-network-upgrades/