Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add meta EIP for hard forks #233

Merged
merged 11 commits into from
Sep 18, 2018
Merged

Add meta EIP for hard forks #233

Changes from 1 commit
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
7856d3e
Add meta EIP for hard forks
axic Mar 23, 2017
84c4f86
Mention the require header
axic Mar 27, 2017
490c7b7
Rename to EIP 233
axic Apr 23, 2017
e9d6824
Clarify the Accepted state
axic Apr 23, 2017
c7cc2e9
Require the Yellow Paper to be up-to-date
axic Apr 23, 2017
784d0a2
Merge branch 'master' into hardforks
axic Sep 4, 2018
6406626
Update to new EIP header
axic Sep 4, 2018
1067c3f
Update wording to reflect the new EIP process (drafts are merged and …
axic Sep 4, 2018
73c1d20
Remove the requirement of keeping the Yellow Paper up to date (this s…
axic Sep 4, 2018
f1eb682
Merge branch 'master' into hardforks
Souptacular Sep 18, 2018
d80ffe0
Merge branch 'master' into hardforks
Souptacular Sep 18, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions EIPS/eip-draft_hardforks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
## Preamble

EIP: <to be assigned>
Title: Formal process of hard forks
Author: Alex Beregszaszi
Type: Meta
Status: Draft
Created: 2017-03-23

## Simple Summary

To describe the formal process of preparing and activating hard forks.

## Abstract

To provide a process of coordination on hard forks.

## Motivation

Today discussions about hard forks happen at various forums and sometimes in ad-hoc ways.

## 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:
- the desired codename of the hard fork,
- list of all the EIPs included in the hard fork and
- activation block number once decided.

The draft pull request shall be updated with summaries of the decisions around the hard fork. It should move in to `Accepted` state once the changes are frozen and in to the `Final` state once the hard fork has been activated.

The Yellow Paper should be kept updated with the hard fork changes. It could either refer to the fork codename or the EIP number of the fork.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably worth mentioning that it is a not a blocker for the activation to have an outdated Yellowpaper - if we follow the practice of today.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Depends if this is to be prescriptive or proscriptive. If the latter, then I would propose EIPs should be formalised as Yellow Paper revisions prior to implementation. This would help avoid the subtle consensus issues stemming from the informal nature of EIPs.


## Rationale

A meta EIP for coordinating the hard fork should help in visibility and traceability of the scope of changes as well as provide a simple name and/or number for referring to the proposed fork.

## Copyright

Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).