EIPs/EIPS/eip-233.md

---
eip: 233
title: Formal process of hard forks
author: Alex Beregszaszi (@axic)
discussions-to: https://ethereum-magicians.org/t/eip-233-formal-process-of-hard-forks/1387
type: Meta
status: Draft
created: 2017-03-23
---

## Abstract

To describe the formal process of preparing and activating 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 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 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.

## 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/).
Update to new EIP header 2018-09-04 19:19:59 +00:00			`---`
			`eip: 233`
			`title: Formal process of hard forks`
			`author: Alex Beregszaszi (@axic)`
Automatically merged updates to draft EIP(s) 233 Hi, I'm a bot! This change was automatically merged because: - It only modifies existing Draft or Last Call EIP(s) - The PR was approved or written by at least one author of each modified EIP - The build is passing 2018-09-19 12:16:29 +00:00			`discussions-to: https://ethereum-magicians.org/t/eip-233-formal-process-of-hard-forks/1387`
Update to new EIP header 2018-09-04 19:19:59 +00:00			`type: Meta`
			`status: Draft`
			`created: 2017-03-23`
			`---`
Add meta EIP for hard forks 2017-03-23 14:35:49 +00:00
			`## Abstract`

Clarify the Accepted state 2017-04-23 16:41:48 +00:00			`To describe the formal process of preparing and activating hard forks.`
Add meta EIP for hard forks 2017-03-23 14:35:49 +00:00
			`## Motivation`

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

			`## Specification`

Update wording to reflect the new EIP process (drafts are merged and pull requests are not kept open) 2018-09-04 19:22:13 +00:00			`A Meta EIP should be created and merged as a Draft as soon as a new hard fork is planned. This EIP should contain:`
Add meta EIP for hard forks 2017-03-23 14:35:49 +00:00			`- the desired codename of the hard fork,`
			`- list of all the EIPs included in the hard fork and`
Mention the require header 2017-03-27 19:57:43 +00:00			`- activation block number once decided and`
			`- the Requires header should point to the previous hard fork meta EIP.`
Add meta EIP for hard forks 2017-03-23 14:35:49 +00:00
Update wording to reflect the new EIP process (drafts are merged and pull requests are not kept open) 2018-09-04 19:22:13 +00:00			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.
Add meta EIP for hard forks 2017-03-23 14:35:49 +00:00
			`## 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/).`