status-im/EIPs
2
0
Fork 0
mirror of https://github.com/status-im/EIPs.git synced 2025-02-22 19:58:06 +00:00
Code Issues Projects Releases Wiki Activity

Rewords Motivation section of template. (#3081)

Browse Source 
* Rewords Motivation section of template.

While this section is more clear to EIP authors than most, it still requires coaching.  Also, the wording was written back when EIPs were tightly coupled with hard fork coordination, which is no longer the case.

* Improved wording.

Co-authored-by: lightclient <14004106+lightclient@users.noreply.github.com>

Co-authored-by: lightclient <14004106+lightclient@users.noreply.github.com>
This commit is contained in:
Micah Zoltu 2020-12-05 17:49:56 +08:00 committed by GitHub
parent adf069fdb1
commit 7276588e7a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
eip-template.md
View File

@ -24,7 +24,7 @@ If you can't explain it simply, you don't understand it well enough." Provide a
A short (~200 word) description of the technical issue being addressed. This should be a very terse and human-readable version of the specification section. Someone should be able to read only the abstract to get the gist of what this specification does.
## Motivation
The motivation 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.
The motivation section should describe the "why" of this EIP. What problem does it solve? Why should someone want to implement this standard? What benefit does it provide to the Ethereum ecosystem? What use cases does this EIP address?
## 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 (go-ethereum, parity, cpp-ethereum, ethereumj, ethereumjs, and [others](https://github.com/ethereum/wiki/wiki/Clients)).