# How Ethereum upgrades: proposals, client releases and activation 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. Evidence: [Ethereum Improvement Proposal process](https://eips.ethereum.org/EIPS/eip-1); [Ethereum governance](https://ethereum.org/en/governance/) Canonical: https://degreesofsatoshi.com/encyclopedia/ethereum-network-upgrades/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Proposal:** EIPs document standards or proposed changes and their rationale. ([Ethereum Improvement Proposal process](https://eips.ethereum.org/EIPS/eip-1)) - **Categories:** Application standards and core protocol changes are different EIP categories. ([Ethereum Improvement Proposal process](https://eips.ethereum.org/EIPS/eip-1)) - **Activation:** Implementation and network activation are separate from publishing a proposal. ([Ethereum governance](https://ethereum.org/en/governance/)) ## 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. Evidence: [Ethereum Improvement Proposal process](https://eips.ethereum.org/EIPS/eip-1); [Ethereum governance](https://ethereum.org/en/governance/) ## 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. Evidence: [Ethereum governance](https://ethereum.org/en/governance/) ## 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. Evidence: [Ethereum governance](https://ethereum.org/en/governance/) ## Questions ### 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. Evidence: [Ethereum Improvement Proposal process](https://eips.ethereum.org/EIPS/eip-1); [Ethereum governance](https://ethereum.org/en/governance/) ### 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. Evidence: [The Merge](https://ethereum.org/en/roadmap/merge/); [Ethereum governance](https://ethereum.org/en/governance/) ## Claims and scope ### ethereum-network-upgrades-quick-answer 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: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-network-upgrades-fact-proposal Proposal: EIPs document standards or proposed changes and their rationale. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-network-upgrades-fact-categories Categories: Application standards and core protocol changes are different EIP categories. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-network-upgrades-fact-activation Activation: Implementation and network activation are separate from publishing a proposal. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Ethereum Improvement Proposal process](https://eips.ethereum.org/EIPS/eip-1) — Ethereum Improvement Proposals. Specification stages are distinct from network upgrade deployment. Locator: EIP types; workflow; status. Retrieved: 2026-10-02T18:55:26.643Z. - [Ethereum governance](https://ethereum.org/en/governance/) — ethereum.org contributors. Offchain proposal discussion, client implementation and node adoption. Locator: Governance process; stakeholders; network upgrades. Retrieved: 2026-10-02T18:55:26.750Z. - [The Merge](https://ethereum.org/en/roadmap/merge/) — ethereum.org contributors. Consensus transition preserved execution balances and transaction history. Locator: Merging with Mainnet; misconceptions. Retrieved: 2026-10-02T18:55:26.611Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry 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/