# An optional preamble header - “Stage”
This is a proposal to add a new (optional) preamble field to [eip-template.md](https://github.com/ethereum/EIPs/blob/master/eip-template.md) - "Stage".

## Background
[EIP-7723: Network Upgrade Inclusion Stages](https://eips.ethereum.org/EIPS/eip-7723) defines the stages that EIPs go through in the process of planning network upgrades:

* `Proposed for Inclusion` or PFI
* `Considered for Inclusion` or CFI
* `Scheduled for Inclusion` or SFI
* `Declined for Inclusion` or DFI
* `Included`

Tim Beiko proposed [Reconfiguring AllCoreDevs](https://ethereum-magicians.org/t/reconfiguring-allcoredevs/23370) which suggests better management of present process.

Addition of a "Stage" field to preamble may help
- keep track of EIPs "Network Upgarde Inclusion" stage while they are in active consideration as well as
- provide history of active consideration along with the latest "stage" of each core-EIP.

## The Proposal

Add an optional preamble header - “Stage” in the [EIP template](https://github.com/ethereum/EIPs/blob/master/eip-template.md). This would allow for easier tracking and filtering of an EIP’s current stage without needing to dig into each upgrade’s Meta EIP.

### Accepted input to "Stage"
- It could be the "[upgrade name](Meta EIP link) - "network upgrade stage" for that upgrade. <[Upgrade Name - CFI](MetaEIP)>
- It could accept multiple entry separated by comma (,) similar to (optional) "Requires" field. Having multiple entry will provide EIP considertaion history without searching past Meta EIPs. <[Fusaka - CFI](https://eips.ethereum.org/EIPS/eip-7607#considered-for-inclusion), [Pectra - DFI](https://eips.ethereum.org/EIPS/eip-7600)>
- It should be added as "latest first" order, if there are multiple `stage` entry.
- Only applicable to `Standards Track - Core` EIPs.
(Could be applicable to some `Meta` EIPs like [EIP-7692](https://eips.ethereum.org/EIPS/eip-7692)?)

**Note**: As on date "Pectra Meta EIP" doesn't maintain the list of DFI, but [Pectra DFI](https://github.com/ethereum/EIPs/commit/9d17611c87100a66bf5631ffe1406bf638f7f3e1) existed at one point of time. Maybe we can get that added?

The good news is that "Fusaka Meta EIP" does have the list of [Fusaka DFI](https://eips.ethereum.org/EIPS/eip-7607#declined-for-inclusion).

## Who will update this?
**Author(s) / EIP Champion**
It will be the responsibility of the Author(s) or EIP Champion to add or update the value based on decisions made during AllCoreDevs (ACD) meetings or as defined by related Meta EIPs.

**Editors / Reviewers**
Editor(s) or reviewers may verify the correctness of the entered value during proposal review and provide appropriate suggestions or feedback.

## Does it need to be added retroactively?
• Not necessarily required to be added retroactively.
• This should be treated as a new feature going forward (if/when accepted by EIP editors) and not mandatory for existing EIPs.
• However, it can be added to any EIPs (except those in Final or Withdrawn status) that are accepting new input or changes.
• Stagnant EIPs that are revived for active consideration should also include this field.
eg [EIP-7666](https://eips.ethereum.org/EIPS/eip-7666), was DFI in Pectra upgrade.

Considering this to be a change moving forward, it will be easier to keep track of previous stages of an EIP which was once considered in different upgrade(s).

### Takeaway from EIPIP 115 meeting

Noted concerns have been documented [here](https://ethereum-magicians.org/t/reconfiguring-allcoredevs/23370/5), along with a proposed solution to achieve the desired outcome through UI design—without adding an additional field to the EIP preamble.