mirror of
https://github.com/status-im/EIPs.git
synced 2025-02-23 12:18:16 +00:00
Update EIP template (#3719)
* Update EIP template * Update eip-1.md Updating EIP-1 to provide consistent information as the EIP template.
This commit is contained in:
parent
3173a6fcff
commit
9eae744e36
@ -96,7 +96,7 @@ If this period results in necessary normative changes it will revert the EIP to
|
||||
|
||||
Each EIP should have the following parts:
|
||||
|
||||
- Preamble - RFC 822 style headers containing metadata about the EIP, including the EIP number, a short descriptive title (limited to a maximum of 44 characters), and the author details. See [below](./eip-1.md#eip-header-preamble) for details.
|
||||
- Preamble - RFC 822 style headers containing metadata about the EIP, including the EIP number, a short descriptive title (limited to a maximum of 44 characters), and the author details. Irrespective of the category, the title should not include EIP number. See [below](./eip-1.md#eip-header-preamble) for details.
|
||||
- Abstract - A short (~200 word) description of the technical issue being addressed.
|
||||
- Motivation (*optional) - A motivation section is critical for EIPs that want to change the Ethereum protocol. It should clearly explain why the existing protocol specification is inadequate to address the problem that the EIP solves. EIP submissions without sufficient motivation may be rejected outright.
|
||||
- Specification - The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Ethereum platforms (cpp-ethereum, go-ethereum, parity, ethereumJ, ethereumjs-lib, [and others](https://github.com/ethereum/wiki/wiki/Clients).
|
||||
|
@ -15,7 +15,7 @@ This is the suggested template for new EIPs.
|
||||
|
||||
Note that an EIP number will be assigned by an editor. When opening a pull request to submit your EIP, please use an abbreviated title in the filename, `eip-draft_title_abbrev.md`.
|
||||
|
||||
The title should be 44 characters or less.
|
||||
The title should be 44 characters or less. It should not repeat the EIP number in title, irrespective of the category.
|
||||
|
||||
## Simple Summary
|
||||
"If you can't explain it simply, you don't understand it well enough." Provide a simplified and layman-accessible explanation of the EIP. Imagine an email subject line, GitHub PR title, or forum post title.
|
||||
|
Loading…
x
Reference in New Issue
Block a user