Skip to content

Latest commit

 

History

History
70 lines (39 loc) · 3.35 KB

EIPsForHardfork.md

File metadata and controls

70 lines (39 loc) · 3.35 KB
eip title author discussions-to status type created requires
<to be assigned>
Formal process of selection of EIPs for hardforks (Meta EIP#)
Pooja Ranjan (@poojaranjan)
Draft
Meta
2019-04-09
233

Abstract

To describe a formal process of selection of EIPs for upcoming hardfork (Meta EIP#).

Motivation

Recently, discussion to streamline the process of protocol upgrades is happening at various forum. In order to move from ad-hoc to fixed-schedule to release protocol upgrades, a process of EIP selection is proposed.

Description

This meta EIP provides a general outline process to propose, discuss and track progress of EIPs for upcoming hardfork (Meta EIP#). It recommends to make decision on a hard deadline and suggests to take all other proposals received after the deadline into a subsequent hardfork for a smooth upgrade.

Specification

A Meta EIP should be created and merged following the process mentioned in EIP 233.

EIP selection process for Meta EIP

1. Proposing an EIP

  • If you're an author, and still vetting the idea, please follow guidelines mentioned in EIP - 1 to formalise your idea into an EIP.

  • Once EIP is created, create a new issue at ECH repository referring "EIP# to be considered for next upgrade (Meta EIP#)" , before the deadline for acceptance of proposals.

  • It will be then picked up by the HF coordinators (Ethereum Cat Herders) and added as Proposed EIP under EIP tracker eg for Istanbul.

2. Socializing an EIP

  • Open a discussion thread preferably at EthMagician or publish a blog post for background, need and application of the EIP. Share it on gitter, reddit and twitter (if need be).

  • Invite author to All core dev call to explain / discuss.

3. Reviewing an EIP

Author may reach out to EIP Editors or HF coordinator for help in review the EIP, if not already reviewed. HF coordinator may coordinate with EIP Editors based on the interest / availability.

4. EIP Readiness Tracker

EIP Readiness Tracker may be a combination of EIP tracker and Client Implementation Progress Tracker.

№ EIP Description EIP Status Client 1 Client 2 Client 3 Client 4 Testnet Include in HF / Meta EIP#
1
2
3

Rationale

An EIP readiness tracker for coordinating the hard fork should help in visibility and traceability of the scope of changes to the upcoming hardfork.

Copyright

Copyright and related rights waived via CC0.