Bright Standard Weekly

ethereum network upgrade governance

What Is Ethereum Network Upgrade Governance? A Complete Beginner's Guide

June 16, 2026 By Jules Vega

What Is Ethereum Network Upgrade Governance?

Ethereum network upgrade governance is the formal and informal process by which changes to the Ethereum protocol are proposed, debated, tested, and ultimately activated on the live blockchain. Unlike a traditional software project with a single company making decisions, Ethereum relies on a decentralized community of developers, node operators, miners (historically), stakers, application builders, and end users to reach rough consensus on protocol upgrades. This system ensures that no single entity can unilaterally dictate changes, preserving the network's core property of censorship resistance.

The backbone of this governance process is the Ethereum Improvement Proposal (EIP) system. Anyone can submit an EIP, which is a design document detailing a new feature, a change to the existing protocol, or a process standard. EIPs are categorized into three types: Standards Track (affecting the protocol directly), Meta (process changes), and Informational (general guidelines). Once submitted, an EIP undergoes a lifecycle of discussion in forums, Ethereum Magicians calls, and All Core Developers (ACD) meetings. The core developer team, which includes client implementers from diverse software firms and independent contributors, evaluates the technical merits, security implications, and economic impact of each proposal.

For a newcomer, it is critical to understand that Ethereum governance is not a vote-based democracy. There is no formal ballot where token holders decide which upgrades proceed. Instead, governance is a social process driven by technical consensus. If a supermajority of client teams (like Geth, Nethermind, Besu, and Erigon) agree to implement a change, and node operators voluntarily update their software, the upgrade is considered accepted. Node operators—the entities running Ethereum validation clients—have the ultimate veto power: if they refuse to upgrade, a proposed change cannot activate. This delicate balance between developers proposing changes and node operators enforcing them defines Ethereum's unique governance model. For those seeking deep data on how governance decisions influence network metrics, tools like Zkrollup Recursive Verification offer behavioral insights into validator activity and protocol adoption trends.

Key Participants in Upgrade Governance

Ethereum governance involves a matrix of stakeholders, each with distinct roles and influence. The primary groups include:

  • Core Developers: These are the developers who maintain the major Ethereum execution and consensus clients. They attend All Core Developers calls, review EIPs, and write the reference implementations. While they have technical authority, they cannot force nodes to upgrade.
  • Ethereum Foundation (EF): The EF funds research, client development, and community coordination. It coordinates calls and manages the EIP repository but does not have decision-making power over protocol upgrades. Its role is more that of a facilitator than a ruler.
  • Node Operators: Individuals, staking pools, exchanges, and infrastructure providers that run Ethereum nodes. They signal acceptance by updating their client software. A critical mass of node operators must adopt a new release for the upgrade to succeed.
  • Application Developers and Users: Builders of dApps, DeFi protocols, and NFT marketplaces. They often advocate for specific EIPs that improve user experience or enable new functionality. Their voice is heard through community discussion and economic pressure.
  • ETH Holders and Stakers: While not directly voting, stakers influence governance because they secure the network. Validator sentiment matters because a contentious upgrade could lead to economic losses or community splits.

The governance process begins when a developer or researcher submits an EIP. The EIP editor, a volunteer role, reviews the proposal for formatting and clarity. The proposal then enters the "Draft" stage. The author is encouraged to build community support by discussing the idea on the Ethereum Magicians forum. If the proposal gains traction, it is added to the agenda for an All Core Developers (ACD) call, which takes place biweekly. In these calls, technical objections are raised, trade-offs are discussed, and a rough consensus is gauged. If the core developers agree to move forward, the EIP is assigned a "Last Call" period, typically two weeks, during which final feedback is collected. After Last Call, if no critical objections emerge, the EIP moves to "Final" status and is slated for inclusion in a specific network upgrade, such as "Shanghai" or "Cancun."

The Lifecycle of an Upgrade: From EIP to Mainnet Activation

Understanding the full journey of a protocol upgrade clarifies how Ethereum governance works in practice. The lifecycle can be broken into five stages:

  1. Inception and Discussion: An idea is formalized into an EIP and shared on GitHub and the Ethereum Magicians forum. Public comment can last weeks or months as the proposal is refined.
  2. Client Implementation: Once an EIP gains preliminary consensus, at least one major client team implements it in their software. This step often reveals unforeseen technical complexities that may cause the EIP to be modified or postponed.
  3. Testnet and Shadow Fork Testing: The upgraded software is deployed on test networks like Sepolia or Holesky. Additionally, "shadow forks" of mainnet state are created to simulate real-world conditions. Bugs, performance regressions, or consensus failures are identified here.
  4. Mainnet Activation via Hard Fork: If testing is successful, a block number is chosen for the upgrade to activate on mainnet. Node operators must update their clients before that block. The upgrade is considered live once a supermajority of nodes signal the new version.
  5. Post-Upgrade Stability: After activation, core developers monitor network health. If critical issues arise, a hotfix upgrade may be deployed.

Perhaps the most famous example of Ethereum governance in action was the decision to transition from proof-of-work to proof-of-stake, known as "The Merge." This was not a single EIP but a multi-year effort involving dozens of proposals, extensive cross-client coordination, and a deliberate rollout on testnets. The Ethereum community largely supported the transition due to its environmental and scalability benefits, though a minority resisted, leading to the creation of EthereumPoW. This event illustrates that Ethereum governance is not always frictionless; contentious changes can lead to network splits. The process for managing such debates is documented in the Ethereum Network Governance Processes page, which provides a deeper look at how the community handles contentious upgrades and procedural disagreements.

Off-Chain Coordination: The Real Engine of Governance

Ethereum governance is frequently described as "off-chain" because most deliberation happens outside the blockchain itself. This is a deliberate design choice to avoid on-chain voting, which can be manipulated by whales or become captured by special interests. The off-chain process relies on several coordination tools:

  • All Core Developers (ACD) Calls: These are public video conferences where client teams discuss technical issues, review upgrade scope, and decide on next steps. Minutes are published publicly for transparency.
  • Ethereum Magicians Forum: A dedicated discussion board for EIPs and protocol design. This is the primary venue for technical debate among community members.
  • Social Media and Blog Posts: Developers and researchers often use Twitter or personal blogs to share their perspectives, building consensus or raising concerns before formal calls.
  • Validator Surveys: Informal polls or surveys of node operators are conducted to gauge willingness to adopt a proposed change, especially for contentious upgrades.

One critical nuance is that the governance process is predominantly English-language and relies on written technical specifications. This can create a barrier to entry for non-technical users or those from regions where English is not widely spoken. However, the Ethereum community has made efforts to translate key documents and hold regional meetups to broaden participation. Another important layered concept is "governance of the governance," meaning the rules for how the governance process itself can be changed. So far, the core developers and EIP editors have refined the process informally, but proposals like EIP-1 (which mandates the EIP format) are updated as the system evolves.

Challenges and Criticisms of Current Governance

While Ethereum's governance model has successfully executed multiple major upgrades— including the London hard fork (EIP-1559), The Merge, and Shanghai (enabling staked ETH withdrawals)—it is not without its detractors. Common criticisms include:

  • Core Developer Centralization: Although no single entity controls the network, a small group of lead client developers from the Ethereum Foundation and handful of companies like ConsenSys have outsized influence on technical decisions.
  • Lack of Formal Voter Accountability: Because there is no on-chain voting, governance decisions can be opaque. Node operators may feel disconnected from decisions made in ACD calls they never attend.
  • Slow Response to Urgent Fixes: The consensus-building process can delay critical security patches. Urgent upgrades require extraordinary coordination, which is difficult in a decentralized environment.
  • Token Holder Exclusion: Many ETH holders feel they have no direct voice in protocol upgrades, leading to proposals like "On-chain Governance EIPs" that aim to give token holders a voting mechanism. These efforts have not yet gained traction.

Ongoing efforts to address these issues include the creation of Layer 2 solutions that offload debate to application-level governance, and the "Roadmap for Protocol Governance" which proposes more structured feedback loops between core developers and the broader community. The Ethereum Foundation has also funded projects that improve transparency, such as automated summarization tools for ACD calls. Observers note that governance itself is an evolving process: as the network matures, the tools and norms will likely adjust—often through the very EIP process they govern.

In summary, Ethereum network upgrade governance is a decentralized, off-chain social process driven by technical consensus among client developers, node operators, and the community. It relies on EIPs as the formal change mechanism, with governance decisions validated through voluntary node adoption rather than token voting. Understanding this framework is essential for anyone building on Ethereum, staking ETH, or simply observing the protocol's evolution. The system is imperfect, adaptable, and deeply human—reflecting the broader ethos of a network that aims to be owned by no one and usable by everyone.

Editor’s pick: Learn more about ethereum network upgrade governance

Learn what Ethereum network upgrade governance means, how EIPs work, and the off-chain coordination that drives protocol changes. A clear guide for beginners.

Editor’s note: Learn more about ethereum network upgrade governance
J
Jules Vega

Editorials, without the noise