EOSIO Enhancement Proposals Directory

What is an EEP?

EEP stands for EOSIO Enhancement Proposal. An EEP is a design document providing information to the EOSIO community, or describing a new feature for EOSIO or its processes or environment. All EEPs should provide a concise technical specification of the feature as well as rationale for the feature. The EEP author is responsible for building consensus within the community and documenting dissenting opinions for the proposal.

Criteria for submitting EEP

An EEP must meet certain minimum criteria. It must provide a clear and complete description of the proposed enhancement and provide technical specification and use cases. The enhancement must also represent a net improvement to the EOSIO protocol and how it will benefit the community. Learn more about EEPs guidelines and submission requirements.

How to submit an EEP?
  1. Review EEP-1 to understand the format and guidelines
  2. Fork the repository by clicking “Fork” on the main EOSIO/EEPs page
  3. Add your EEP to your fork of the repository
  4. Submit a “Pull Request” to the EOSIO/EEPs repository for an EEPs editor to review your submission and marge it into the main repository
  5. Once an EEP is ready to progress past the draft phase, the EEPs editor will mark your proposal “Ready for Review” and set a meeting to discuss the proposal.

EEP status terms

Draft: the EEP is currently a work in progress and has not yet been submitted

Submitted: the final draft of the EEP has been submitted by the EEP author

Ready for Review: the EEP has been reviewed by an EEP editor and has been added to the agenda for the next EEP review meeting

Accepted: the EEP was analyzed and discussed by the EEP reviewers and has sufficient support for implementation

Under Development: the EEP is currently under development

Pending PR Review: the EEP implementation is currently being reviewed for final acceptance

Final: the EEP has been successfully implemented and is now active

Deferred: the EEP has been shelved for future consideration

Living: this is similar to Final, but denotes an EEP which requires regular updates for accuracy (good for token/wallet standards)

Archived: the EEP is no longer under consideration (withdrawn by author, not enough support for the proposal, etc.)

EEP types

EEPs are separated into a number of different types, and each may have its own list of EEPs. The four main EEP types are: Standard, Informational, Meta, and Archived. It is highly recommended that a single EEP contain a single key proposal or new idea. The more focused the EEP, the more successful it is proven to be.

Standard – Core

Improvements requiring a consensus fork, as well as changes that are not necessarily consensus critical but may be relevant to “core dev” discussions

EEP Number Title Author Status
2 Josh Kauffman, Alexandre Bourget, Marc-Antoine Ross, Stephane Duschesneau, Matthieu Vachon Draft
8 Corvin Meyer auf der Heide Draft
EEP Number
2
Author
Josh Kauffman, Alexandre Bourget, Marc-Antoine Ross, Stephane Duschesneau, Matthieu Vachon
Status
Draft
EEP Number
8
Author
Corvin Meyer auf der Heide
Status
Draft

Standard – Networking

Includes improvements around the p2p protocol

EEP Number Title Author Status
5 Alexandre Bourget Draft
6 Alexandre Bourget, Richard Reiner, Guillaume Babin, Mathieu Boulianne Draft
EEP Number
5
Author
Alexandre Bourget
Status
Draft
EEP Number
6
Author
Alexandre Bourget, Richard Reiner, Guillaume Babin, Mathieu Boulianne
Status
Draft

Standard – Interface

Includes improvements around client API specifications and standards, and also certain language-level standards like contract ABIs. For contract ABIs, it aligns with the eosio.contracts repo and discussion should primarily occur in that repository before an EEP is submitted to the EOSIO/EEPs repository

EEP Number Title Author Status
3 Buddy Deck Under Development
7 Aaron Cox, Johan Nordberg Under Development
EEP Number
3
Author
Buddy Deck
Status
Under Development
EEP Number
7
Author
Aaron Cox, Johan Nordberg
Status
Under Development

Meta

Describes a process surrounding EOSIO or proposes a change to (or an event in) a process. Process EEPs are like Standards Track EEPs but apply to areas other than the EOSIO protocol itself.

EEP Number Title Author Status
1 EOS Canada Team Ready for Review
EEP Number
1
Author
EOS Canada Team
Status
Ready for Review

EEPs is not a channel to obtain funding through Block.one. The purpose of EEPs is to create an official channel for open source collaboration, community ideas and input for the EOSIO protocol.