From Consensus Paper
Revision as of 07:24, 1 April 2020 by Sorpaas (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This page documents the governance process of Consensus Paper.

Principles[edit source]

Consensus Paper operates under some core principles:

  1. Specifications are identified by their unique names. Unlike other processes, numbers are not used in Consensus Paper, because it's uninformative.
  2. Anyone can start a new specification, by simply creating a new document under a new name. For example, Simple subroutines, Phoenix (new) and Phoenix backward compatibility promise.
  3. Specifications are owned by no one and not addressed by their authors. Everyone can submit changes to specifications (unless a specification is considered "frozen").
  4. Specifications start in status of "under review". From there, the specification can be changed or reviewed. When a specification is adopted by applications, editors will move it to status of "frozen", meaning the specification cannot be changed any more. In "frozen" status, additional review comments or specification errata can still be added.
  5. When conflicts happen and cannot be resolved internally, it is resolved by creating a new specification under a different name. For example, Ethereum family and Ethereum Classic family.