As part of separating the EIP process from the network upgrade process, a set of stages were created to track progress of EIPs towards mainnet, they are:

• Considered for Inclusion (CFI)
• "Devnets" (i.e. YOLO, Aleut, etc.)
• Testnets
• Mainnet

CFI is intended for core developers to signal support for an idea before it is fully fleshed out. Given how much things change between network upgrades, I propose that this status resets between upgrades (i.e. an EIP which was CFI for Berlin would not automatically be CFI for London). We already implicitly do this, but I wanted to ask before going ahead and archiving past CFI EIPs.

The CFI list is tracked here. The pre-London/Shanghai list includes the following EIPs: 663, 2711 (likely superseded by 3074), 2398, 2046, 1985, 1380. EIP-2537 was also CFI pre-Berlin, but it had enough interest for someone to propose it for London. IMO that should be the minimum bar we expect to move something over to CFI again for the next upgrade.

Doing this will help keep the eth1-specs repo clean and not have stagnant EIPs pile up in the CFI column.