From d37911f46373ef95bb185f464fbc88f3e53b2b17 Mon Sep 17 00:00:00 2001 From: Alex Beregszaszi Date: Mon, 27 Mar 2017 20:57:43 +0100 Subject: [PATCH] Mention the require header --- EIPS/eip-draft_hardforks.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/EIPS/eip-draft_hardforks.md b/EIPS/eip-draft_hardforks.md index c92dbf3b..de83d782 100644 --- a/EIPS/eip-draft_hardforks.md +++ b/EIPS/eip-draft_hardforks.md @@ -24,9 +24,10 @@ Today discussions about hard forks happen at various forums and sometimes in ad- 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. +- 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 `Accepted` state once the changes are frozen and in to the `Final` state once the hard fork has been activated. +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 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.