Recently, Block.one officially launched the EOSIO Feature Enhancement Proposal (EEPs) program. The goal of the program is to extend the open source model and drive a more stable, higher performing, secure, and innovative EOSIO.
In the official release, Block.one stated.
"We believe it is important to tap into the collective knowledge and talent of our global community. Through the EEPs program, protocol improvements and new features will be discussed and developed."
The goal of the EEPs program is to continue to evolve and expand EOSIO and to give the community a voice in defining its future.
The EEPs program's intent is to further develop and expand EOSIO and to give the community a role in shaping its vision for the future.
Anyone can take part in the program by submitting a proposal or providing technical feedback on one that has already been submitted. Each EEP proposal should follow the standards and contain thorough documentation explaining the new features and their impact on the community.
A technical definition, community benefits or use cases, and the justification for the feature should all be included in the EEP. The EEP author is in charge of bringing the community together and documenting differing viewpoints. This method is chain-independent and solely pertains to the EOSIO protocol.
Currently Block.one has released the first EEP detailing the purpose and operation of the EEP program. existing proposals from EOS Canada and Greymass are included in the new EEPs proposal library: Click to view EEPs proposal library
Currently, in addition to the proposed EOSIO token standard, Block.one is introducing a new proposal to allow the creation of a common API for token checks and contract verification checks.
In the future, the EEP proposal will be taken by Block.one as an input to the EOSIO roadmap. SEP supports the open-source community approach in which a more robust EOSIO may be built by a community.