Hegota Upgrade EIP Proposal Timelines

Following the Fusaka upgrade, which delivered PeerDAS and numerous smaller improvements and ahead of Glamsterdam’s major features like Block‑level Access Lists and enshrined PBS, the Ethereum core development process is now turning its attention to the next network upgrade: Hegota. The announcement lays out how proposals will be gathered, evaluated, and finalized, establishing a clear process for both major (“headliner”) and minor (“non‑headliner”) EIPs.

Key Ideas

Structured timeline for selecting major features - The Hegota process begins with a window from January 8 to February 4 for submitting headliner EIPs on Ethereum Magicians. Submissions must follow a template requiring justification, user impact analysis, technical readiness, and the naming of an EIP champion. Proposals must also be presented on an All Core Devs call to be considered.
Deliberation and community input shape final headliners - After the submission window, roughly four ACD calls will be dedicated to evaluating proposals based on urgency, user benefit, complexity, and security considerations. Community members can provide feedback through a dedicated template on the Ethereum Magicians forum. One candidate, FOCIL, is already under consideration due to prior discussion.
Minor features follow after headliners are set - Once headliners are finalized, a 30‑day period opens for non‑headliner EIPs. These smaller proposals are added via pull requests to the Meta EIP and placed into the “Proposed for Inclusion” section. Forkcast will track the evolving timeline and technical schedule.

Why It Matters?

The Hegota process reinforces Ethereum’s commitment to transparent, staged, and community‑driven network evolution. By clearly separating major and minor features, requiring structured justification, and inviting broad feedback, the upgrade pipeline aims to balance ambition with technical discipline. This approach helps ensure that each upgrade meaningfully advances Ethereum’s roadmap while maintaining security, clarity, and developer alignment.