Ethereum Governance Hub

Homestead.

ECH is the steward of major initiatives documented at Homestead.

Supporting the processes, coordination, and participation that help Ethereum evolve responsibly as open, public infrastructure.

8
EIP Lifecycle Stages
3
EIP Inclusion States
2x
Annual Upgrade Cadence
2024
ECH Institute Founded

Section 1

What is Ethereum Governance?

A simple explanation of how Ethereum makes decisions the upgrade selection process, the EIP framework, and where to track it live.

Ethereum governance is the process by which changes to the protocol are proposed, discussed, evaluated, and implemented. Unlike traditional software with a centralized team, Ethereum relies on a rough consensus model meaning changes must achieve broad agreement among client teams, researchers, application developers, and the broader community before they are accepted. No single entity has veto power or final authority over the protocol.

Decentralized decision-making with no single authority
Rough consensus required across client teams and community
Changes proposed through the EIP (Ethereum Improvement Proposal) process
All discussions are open and accessible to anyone
Client teams must independently choose to implement changes

Section 2

The EIP Process

What EIPs are, how they're structured, and the lifecycle every proposal passes through from concept to mainnet deployment.

Standards Track

EIPs that change the Ethereum protocol itself including Core, Networking, Interface, and ERC (token/application) changes.

Meta EIP

Describes a process or proposes a change to the EIP process itself. Not changes to the protocol.

Informational

Provides general guidelines or information to the Ethereum community. No binding changes to the protocol.

EIP Lifecycle: Stage by Stage

01

Idea

A concept is informally discussed on Ethereum Magicians or Discord to gauge community interest and feasibility before any formal document is written.

Post on Ethereum Magicians Gauge community interest Refine the core idea
02

Draft

A formal EIP document is written following the EIP-1 template. It is submitted as a pull request to the ethereum/EIPs GitHub repository and assigned an EIP number.

Write EIP using the EIP-1 template Submit PR to ethereum/EIPs Assigned an EIP number by editors
03

Review

EIP editors and the core developer community review the proposal for technical soundness, specification clarity, and backward compatibility. Revisions are made in response to feedback.

EIP editor format review Core developer technical review Revisions based on feedback
04

Last Call

A final 14-day public comment window for all stakeholders. The EIP is considered complete unless critical issues are raised that require it to return to Review status.

14-day public comment window Broadcast to wider community Final chance to raise blocking issues
05

Final

The EIP is accepted as an official Ethereum standard. From here it may be considered for inclusion in an upcoming network upgrade, or may stand alone as an informational or interface standard.

Accepted as official standard Considered for network upgrade inclusion Becomes permanent reference spec
06

Stagnant

Any EIP in Draft or Review state that is inactive for a period of 6 months or greater is moved to Stagnant. It can be resurrected by authors later.

Inactive for 6 months Moved to Stagnant Can be resurrected
07

Withdrawn

The EIP author has explicitly withdrawn the proposed EIP. This state has finality and can no longer be resurrected using this EIP number.

Author withdraws EIP Permanent state Cannot be resurrected
08

Living

A special status for EIPs that are designed to be continually updated and not reach a state of finality (e.g., EIP-1).

Continually updated Never final Core process documentation

Section 3

Network Upgrades

How Ethereum coordinates hard forks, the formal inclusion stages from EIP-7723, and an overview of recent and upcoming upgrades.

An Ethereum network upgrade (also called a hard fork) is a scheduled change to the protocol that requires all clients to update to a new version simultaneously. Upgrades are coordinated through the ACD calls and require unanimous agreement from all major client teams. A "fork hash" is used to coordinate the exact block or slot at which the upgrade activates.

Multiple finalized EIPs are bundled into a single upgrade
All major Ethereum clients must implement the changes
Activation happens at a specific block number or timestamp
Devnets and testnets are deployed first for testing
Community is notified well in advance of mainnet activation
Post-deployment monitoring confirms upgrade success

Section 4

Role of ECH Institute

ECH Institute is the neutral coordination and education infrastructure for Ethereum governance. Here is how the Institute contributes across four pillars.

ECH Institute coordinates a wide range of governance infrastructure including EIPIP (EIP Improvement Process) meetings, All Core Devs documentation, and upgrade communication. As a neutral party, the Institute is able to facilitate conversations between groups that might otherwise lack a shared coordination venue. This coordination role is critical to ensuring no proposal or concern falls through the cracks.

Organizes EIPIP (EIP Improvement Process) office hours and calls
Facilitates All Core Devs (ACD) call logistics and pre-meeting preparation
Manages upgrade communication timelines with client teams
Coordinates between EIP authors, editors, and core developers
Maintains agenda systems and follow-up tracking for governance calls

Section 5

Why This Matters

Ethereum's decentralization is not self-sustaining. It requires active governance infrastructure, clear processes, and broad participation.

Take the Next Step

Get Involved in Governance

Participation & Ecosystem Contribution

ECH Institute is your starting point for understanding and contributing to Ethereum governance. Join the community, attend office hours, or simply start reading.