...
Informational EIP’s describe an Ethereum design issue, but do not propose a new feature. They do not require consensus and it is at the liberty of the user to decide whether or not to implement the change.
EIP Requirements:
- Preamble: A short descriptive title, author details, and the EIP number.
- Summary: A simple, brief description of the EIP.
- Abstract: A short description of the technical specifications of the EIP.
- Motivation: These are critical for EIP’s seeking to change the Ethereum protocol. It is a clear explanation of why the existing protocol is inadequate to solve the problem the current EIP seeks to solve.
- Specification: Describes the syntax of the new feature. It should be detailed enough to allow competing and interoperable implementations of the current Ethereum platforms.
- Rationale: Explains why particular design decisions were made. It should consider alternate designs and show compatibility in different languages. It must also show consensus within the community and discuss important concerns.
- Backwards Compatibility: All EIP’s with backwards incompatibility must describe these incompatibilities and their severity. The author must explain how they intend to deal with these incompatibilities.
- Test Cases: These are mandatory for EIP’s affecting consensus changes.
- Implementations: This must be completed before any EIP is given status ‘Final’, but does not need to be completed before the EIP is merged as a draft.
- Copyright waiver: All EIP’s must be in the public domain.
The EIP format design and implementation is as follows:
Work in Progress (WIP)
An EIP qualifies as a Work in Progress (WIP) when the author drafts a pull request.
...