{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "ethereum-network-upgrades",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/ethereum-network-upgrades/",
  "collection": "ethereum",
  "title": "How Ethereum upgrades: proposals, client releases and activation",
  "description": "Follow the path from an Ethereum proposal to tested client software and an activated network change.",
  "aliases": [
    "Ethereum network upgrades process",
    "EIP proposed versus activated"
  ],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T19:27:58.939Z",
    "dataAsOf": "2026-10-02"
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "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.",
    "claimId": "ethereum-network-upgrades-quick-answer",
    "sourceIds": [
      "x425-eth-eip1",
      "x425-eth-eth-governance"
    ]
  },
  "keyFacts": [
    {
      "label": "Proposal",
      "value": "EIPs document standards or proposed changes and their rationale.",
      "sourceIds": [
        "x425-eth-eip1"
      ],
      "id": "proposal",
      "claimId": "ethereum-network-upgrades-fact-proposal"
    },
    {
      "label": "Categories",
      "value": "Application standards and core protocol changes are different EIP categories.",
      "sourceIds": [
        "x425-eth-eip1"
      ],
      "id": "categories",
      "claimId": "ethereum-network-upgrades-fact-categories"
    },
    {
      "label": "Activation",
      "value": "Implementation and network activation are separate from publishing a proposal.",
      "sourceIds": [
        "x425-eth-eth-governance"
      ],
      "id": "activation",
      "claimId": "ethereum-network-upgrades-fact-activation"
    }
  ],
  "prerequisites": [
    "ethereum-nodes-rpc"
  ],
  "sections": [
    {
      "id": "stages",
      "heading": "A specification is one part of deployment",
      "sourceIds": [
        "x425-eth-eip1",
        "x425-eth-eth-governance"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "example",
      "heading": "Testnet support does not prove mainnet support",
      "sourceIds": [
        "x425-eth-eth-governance"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "governance",
      "heading": "Coordination happens through more than token voting",
      "sourceIds": [
        "x425-eth-eth-governance"
      ],
      "paragraphs": [
        "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."
      ]
    }
  ],
  "faq": [
    {
      "question": "Does an EIP marked Final mean every chain has deployed it?",
      "answer": "No. EIP status describes the specification process. Actual behavior depends on the proposal type and the implementation or network using it.",
      "sourceIds": [
        "x425-eth-eip1",
        "x425-eth-eth-governance"
      ]
    },
    {
      "question": "Must every Ethereum user manually upgrade ETH tokens?",
      "answer": "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.",
      "sourceIds": [
        "x425-eth-eth-merge",
        "x425-eth-eth-governance"
      ]
    }
  ],
  "claims": [
    {
      "id": "ethereum-network-upgrades-quick-answer",
      "articleSlug": "ethereum-network-upgrades",
      "statement": "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.",
      "sourceIds": [
        "source-8b618399ddf05875",
        "source-95f53241e21aef41"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-8b618399ddf05875",
          "locator": "EIP types; workflow; status"
        },
        {
          "sourceId": "source-95f53241e21aef41",
          "locator": "Governance process; stakeholders; network upgrades"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read EIP1 categories/status workflow and governance formal activation process. Core specification, implementation, testnet activation and mainnet activation differ; application ERC need not require network fork. Offchain coordination not automatic token vote. Final specification status not a universal chain-deployment assertion."
        ]
      }
    },
    {
      "id": "ethereum-network-upgrades-fact-proposal",
      "articleSlug": "ethereum-network-upgrades",
      "statement": "Proposal: EIPs document standards or proposed changes and their rationale.",
      "sourceIds": [
        "source-8b618399ddf05875"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-8b618399ddf05875",
          "locator": "EIP types; workflow; status"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read EIP1 categories/status workflow and governance formal activation process. Core specification, implementation, testnet activation and mainnet activation differ; application ERC need not require network fork. Offchain coordination not automatic token vote. Final specification status not a universal chain-deployment assertion."
        ]
      }
    },
    {
      "id": "ethereum-network-upgrades-fact-categories",
      "articleSlug": "ethereum-network-upgrades",
      "statement": "Categories: Application standards and core protocol changes are different EIP categories.",
      "sourceIds": [
        "source-8b618399ddf05875"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-8b618399ddf05875",
          "locator": "EIP types; workflow; status"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read EIP1 categories/status workflow and governance formal activation process. Core specification, implementation, testnet activation and mainnet activation differ; application ERC need not require network fork. Offchain coordination not automatic token vote. Final specification status not a universal chain-deployment assertion."
        ]
      }
    },
    {
      "id": "ethereum-network-upgrades-fact-activation",
      "articleSlug": "ethereum-network-upgrades",
      "statement": "Activation: Implementation and network activation are separate from publishing a proposal.",
      "sourceIds": [
        "source-95f53241e21aef41"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-95f53241e21aef41",
          "locator": "Governance process; stakeholders; network upgrades"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:27:58.939Z",
        "reviewer": "Independent automated verification agent verify_bitcoin_stablecoins_100",
        "notes": [
          "Read EIP1 categories/status workflow and governance formal activation process. Core specification, implementation, testnet activation and mainnet activation differ; application ERC need not require network fork. Offchain coordination not automatic token vote. Final specification status not a universal chain-deployment assertion."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "x425-eth-eip1",
      "label": "Ethereum Improvement Proposal process",
      "publisher": "Ethereum Improvement Proposals",
      "url": "https://eips.ethereum.org/EIPS/eip-1",
      "locator": "EIP types; workflow; status",
      "note": "Specification stages are distinct from network upgrade deployment.",
      "version": "EIP-1",
      "checkedAt": "2026-10-02T18:55:26.643Z",
      "contentSha256": "c2be94a87a1804cd5a678ae11c162018c302768469b5c9cbb871239d61f28b9e",
      "recordId": "source-8b618399ddf05875"
    },
    {
      "id": "x425-eth-eth-governance",
      "label": "Ethereum governance",
      "publisher": "ethereum.org contributors",
      "url": "https://ethereum.org/en/governance/",
      "locator": "Governance process; stakeholders; network upgrades",
      "note": "Offchain proposal discussion, client implementation and node adoption.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:26.750Z",
      "contentSha256": "2e8ea5bcaac9a1aec1b5d37cad81d55e61a8ff4701ad61fa1a2ed456372a44c0",
      "recordId": "source-95f53241e21aef41"
    },
    {
      "id": "x425-eth-eth-merge",
      "label": "The Merge",
      "publisher": "ethereum.org contributors",
      "url": "https://ethereum.org/en/roadmap/merge/",
      "locator": "Merging with Mainnet; misconceptions",
      "note": "Consensus transition preserved execution balances and transaction history.",
      "version": "Documentation snapshot retrieved 2 October 2026; response hash recorded separately",
      "checkedAt": "2026-10-02T18:55:26.611Z",
      "contentSha256": "ba5215656c2f78e216194516233977b3800ae05195e0bb7999fdf50e6ab0f5f4",
      "recordId": "source-6c6265b20e47ad72"
    }
  ],
  "related": {
    "articles": [
      "ethereum-nodes-rpc",
      "ethereum-gas-fees",
      "ethereum-blobs-data-availability",
      "ethereum-weak-subjectivity",
      "ethereum-block-reorganizations"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "First publication after primary-source research and separate automated verification."
    }
  ],
  "citation": "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/"
}