ETH1x Istanbul Prep Meeting

[timbeiko]

@cdetrio

The process as described there conflicts with the definitions of the terms stated on the README, and with the actual process of getting EIPs adopted. Here’s the terms on the README (full disclosure: I wrote these):

• Draft - an EIP that is open for consideration.
• Accepted - an EIP that is planned for immediate adoption, i.e. expected to be included in the next hard fork (for Core/Consensus layer EIPs).

So there are two definitions of Accepted for Core EIPs now:

1. The one stated in EIP-1. Accepted only means the Core EIP went through a two week “last call” phase before its status was upgraded to Accepted.
2. The one stated in the readme. Core EIPs are updated from Draft to Accepted after AllCoreDevs reach provisional agreement (by rough consensus) to schedule it for adoption in the next fork.

Also in EIP-1:

Accepted (Core EIPs only) – This EIP is in the hands of the Ethereum client developers. Their process for deciding whether to encode it into their clients as part of a hard fork is not part of the EIP process.

I’ve submitted a small PR to EIP-1 to make this more consistent. https://github.com/ethereum/EIPs/pull/1858/files