As part of an EIP centric forking model, this EIP tracks the first step in the approval process for any EIP to be included in a fork or upgrade. Specifically, the stage where the Core Developers vet the concept of an EIP and give a βgreen lightβ sufficient for EIP authors to move forward in development.
Abstract
The pipeline for Core EIPs, per the EIP-Centric upgrade model, is as follows.
This EIP documents all EIPs marked as Eligible For Inclusion by the All Core Devs. Typically to reach this stage, an EIP must be discussed in brief on an AllCoreDevs Call and motioned by rough consenses to be moved to this stage. Any additions to this list are required to provide a link to the meeting notes when this discussion and decision took place.
The requirements for Eligible for Inclusion is that the AllCoreDevs, representing the major clients and ecosystem stakeholders etc:
Are positive towards the EIP,
Would accept (well written) PRs to include the EIP into the codebase.
So that it could be toggled on for testingβ¦
β¦but not with an actual block number for activation
Motivation
Development of clear specifications and pull requests to existing Ethereum Clients is a large investment of time and resources. The state of Eligible for Inclusion is a signal from the Ethereum Core Developers to an EIP Author validiating the idea behind an EIP and confirms investing their time further pursing it is worthwhile.