status-im
/
EIPs
mirror of https://github.com/status-im/EIPs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update wording to reflect the new EIP process (drafts are merged and pull requests are not kept open)

This commit is contained in:
Alex Beregszaszi 2018-09-04 20:22:13 +01:00 committed by Hudson Jameson
parent 2acea6ec7f
commit 35b75c130d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
EIPS/eip-233.md
View File

@ -17,13 +17,13 @@ Today discussions about hard forks happen at various forums and sometimes in ad-
## Specification
A Meta EIP should be created as a draft as a pull request as soon as a hard fork is planned. This EIP should contain:
A Meta EIP should be created and merged as a *Draft* as soon as a new hard fork is planned. This EIP should contain:
- the desired codename of the hard fork,
- list of all the EIPs included in the hard fork and
- activation block number once decided and
- the **Requires** header should point to the previous hard fork meta EIP.
The draft pull request shall be updated with summaries of the decisions around the hard fork. It should move in to the `Accepted` state once the changes are frozen (i.e. all referenced EIPs are in the `Accepted` state) and in to the `Final` state once the hard fork has been activated.
The draft shall be updated with summaries of the decisions around the hard fork. It should move in to the `Accepted` state once the changes are frozen (i.e. all referenced EIPs are in the `Accepted` state) and in to the `Final` state once the hard fork has been activated.
The Yellow Paper must be kept updated with the hard fork changes. It could either refer to the fork codename or the EIP number of the fork. The hard fork cannot be activated before the Yellow Paper is updated.