EIP-5069 EIP Editor Handbook
No call decision · Other · EIP status Living · created 2022-05-02
A governance document that sets out the role of the EIP editor organization, how its members are selected, and how decisions are made. It covers the EIP institution itself, not protocol code.
Why it is needed
Anyone can submit an Ethereum Improvement Proposal (EIP), but there are specific people who review proposals and maintain the document repository: the EIP editors. However, confusion arises if it is not clearly documented in one place what editors actually do, what they do not do, how new editors are selected, and how decisions are made when opinions diverge. For example, people might misunderstand an editor's approval of a proposal as a guarantee that it is technically correct, or as the editor picking a winner among competing proposals. This document codifies the editors' mission, organizational structure, procedures for joining and leaving, and formal decision-making process, to reduce such misunderstandings and keep the EIP institution operating transparently.
What changes
Today
- The scope and limits of the editors' role are not documented in a single place
- The procedure for adding or removing editors is not codified
- It is unclear who determines whether consensus has been reached when opinions diverge
After EIP-5069
- What editors do (publishing, facilitating discussion, maintaining quality) and what they do not do (deciding winners, giving technical guarantees, managing schedules) is made explicit
- Roles are divided among EIP Editor, Associate Editor, Coordinator, and Keeper of Consensus
- A formal decision-making procedure is established, with a written call for input and a 30-day quorum rule
Who is affected
- EIP authors: It becomes clear what can and cannot be expected of editors. An editor's approval to publish is not a technical guarantee, and implementation schedules or fork inclusion are not within the editors' purview.
- EIP Editor / Associate Editor: The scope of each role's authority is defined. Associate Editors review and approve, but do not participate in governance votes, and their decisions can be overturned by an Editor.
- EIP Coordinator: A role officially recognized for operational tasks such as guiding authors, managing follow-up work, and maintaining documentation, without review or voting authority.
- The community at large: The procedures by which editors are elected and major decisions are made can be verified through published rules.
In depth
Mission: three things we do
The editors' mission has three parts. First, publishing proposals and their history and related discussion so they remain freely accessible for a long time (Publishing Proposals). Second, providing an open forum for discussion to anyone who wishes to participate respectfully (Facilitating Discussion). Third, maintaining the minimum subjective quality bar defined by each proposal's intended audience (Upholding Quality). The document defines editors both as archivists who preserve the community's history and as publishers who announce the latest proposals.
Five things we don't do
Editors do not decide winners among competing proposals; they publish all of them (Decide Winners: not done). Publication is not a guarantee of technical soundness, and not every proposal is deeply vetted (Assert Correctness: not done). Editors do not track implementation status, manage schedules, or decide fork dates or fork contents (Manage: not done). Open-ended registries that anyone can keep adding entries to are not accepted, though completed static lists are allowed (Track Registries: not done). Legal matters such as trademarks, copyright, and patents are the responsibility of authors and implementers, and editors do not provide legal advice. The source text adds that this list is only illustrative and that it reserves the right to reduce its workload wherever possible.
Organizational structure: Editors, Associate Editors, Keeper of Consensus
The organization consists of several EIP Editors, several Associate EIP Editors, and one Keeper of Consensus elected by the editors from among themselves. Editors are responsible for the governance and enforcement of the EIP process, electing the Keeper of Consensus, and managing proposals. Per EIP-1, Associate Editors handle enforcement tasks such as reviewing proposals, approving pull requests, and moving proposals through lifecycle stages, and have editorial discretion, but their decisions can be overturned by an Editor, and they do not participate in governance. In addition to editor duties, the Keeper of Consensus holds two further responsibilities: judging whether rough consensus has been reached, and judging whether a matter already settled may be reopened. The Keeper of Consensus can also resolve disputes involving Associate Editors.
EIP Coordinator
Beyond editors, there are zero or more EIP Coordinators selected by the editors. Coordinators support operational and educational tasks such as helping authors navigate the process, tracking process-related follow-up work, and maintaining related documentation. They do not perform editorial review or decide whether a proposal is accepted or rejected. Editors may delegate mechanical administrative tasks to coordinators. To become a coordinator, in addition to the general editor requirements, one must demonstrate deep understanding of the EIP process and workflow, experience supporting authors, experience coordinating follow-up work and documentation, and the ability to remain neutral on the technical intent and merits of individual EIPs. However, the requirements of critiquing EIP technical content and participating in governance are waived.
Membership requirements
Anyone may apply to become an EIP editor. Detailed qualification criteria are left to individual current editors, but there are four general requirements: strong belief in the mission above, fluency in English (both written and spoken), the ability to read and critique EIPs, and participation in governance. Editors must meet these requirements throughout their tenure, and failing to do so is grounds for removal. Members may delegate part or all of their responsibilities and authority to tools or other people. The requirements for Associate Editors are the same as for Editors, except that governance participation is not expected.
Formal decision-making: calls for input and quorum
Electing the Keeper of Consensus, adding or removing Editors, Associate Editors, or Coordinators, and any potentially contentious decision must follow the formal procedure. Only EIP Editors participate in formal decision-making. The procedure begins with a written call for input notice, and quorum is established only if all editors state an opinion, a vote, or no opinion within 30 days. If not everyone responds within 30 days, quorum shrinks to the editors who responded, and the deadline may be extended under exceptional circumstances. Matters with low potential for controversy, especially decisions affecting only a single proposal, may be handled informally at an editor's discretion, in keeping with the mission.
Decision rules by matter
Any editor may initiate a Keeper of Consensus election, and work continues during the election. Once quorum is met, the editor with the most votes becomes the Keeper of Consensus until the next election; ties are broken by a fairly agreed method (a coin flip on video call, commit-reveal rock-paper-scissors, etc.). Adding an editor requires quorum plus the candidate's consent and no objection from current editors. Removing an editor requires no objection from editors other than the one being removed, and voluntary resignation is possible at any time. If the departing editor was the Keeper of Consensus, a new election begins immediately. Adding and removing deputy editors follows the same no-objection method. Adding and removing coordinators follows rough consensus; coordinators have no vote and do not participate in rough consensus determinations, but may provide operational information and opinions.
Rough consensus and document status
All other decisions are made by rough consensus. Unanimity is not required, but the dominant view of the editors prevails, and dominant is judged not by loudness or persistence but by an overall sense of agreement. The original text states that 51% is not rough consensus and 99% is better than rough. Whether consensus has been reached is judged by the Keeper of Consensus, but every editor's opinion must be heard and understood beforehand. Except for the no-objection rule for adding and removing editors, no one, not even the Keeper of Consensus, holds a veto. This section was written with reference to RFC 2418. This document's status is Living, meaning it is not a finalized standard but a continuously updated document whose content may still change.