ELIP is a design document that can be submitted to describe new features or a process for the Elastos community.  An ELIP provides concise technical specifications and rationale for new methods.

You can read it in more detail in either English or Chinese here.

To join in the discussion on the CR Forums, go here.

Find the github here.

This should become the main mechanism for improving Elastos technology and an effective ELIP would be met with majority approval by the community. Therefore, an ELIP will be managed by CR Consensus. Authors of an ELIP have the responsibility to listen to community comments and revise and maintain their ELIP.  


Elastos is building a blockchain-driven smart World Wide Web. Its infrastructure includes:

  • Blockchain
  • Wallet
  • Network Service
  • Storage Service
  • Application and Runtime

Therefore, the technical scope of ELIP can be in any one or more of these five items. In addition to the Elastos platform technology, improvements can be proposed to the Elastos community through ELIP, including CR suggestions, issues, and processes.


There are three types of ELIPs: standards tracking, process, and informational. The standards tracking ELIP relates to changes in the design and implementation of Elastos infrastructure, which have a global impact, such as the modification of blockchain consensus, the modification of network protocols, and the modification of service interfaces.

The process ELIP describes a process surrounding Elastos, or proposes a change to a process. Implementations may also be proposed in the ELIP, but should not involve changes to the Elastos platform codebase. In general, the process ELIP needs to gain community consensus.

The Informational ELIP describes the design issues of Elastos, or provides general guidelines or information to the Elastos community, but does not propose new features. It does not necessarily need consensus or support from the Elastos community.

Status and workflow

The ELIP process begins with a new idea for Elastos. Each potential ELIP must have an initiator who can initiate a discussion in the forum or mailing list they deem appropriate.  They must build community consensus around an idea. Once the initiator believes that the proposal is likely to be accepted, a copy of the ELIP should be submitted to the CR website.

The ELIP submitted is subject to a preliminary review by CR Secretariat and needs to meet certain minimum standards to be accepted. It may be rejected if the proposal is too unfocused or too broad.

Once the author believes that the draft is mature, and no further modification is needed, the draft ELIP is ready for CRC voting. The CR Secretariat shall process and review the ELIP again so that it falls within specific criteria.  If the ELIP passes the review, it’s submitted to CRC for voting as a normal proposal. The reviewing process should not be longer than one week. Once the ELIP is submitted, the subsequent processing flow is the same as any CR proposal process.

The CRC should complete the vote for the ELIP within one week with the ELIP set for voting as a “Last Call” status, which means that the ELIP is in the public voting period. If the number of negative votes in a week does not reach 10% of the total number of votes, the status of ELIP will be officially accepted. Otherwise, the ELIP is rejected.

The standards tracking ELIP, however, consists of two parts, a design document and a reference implementation. Once the ELIP is accepted, with the same methods as other ELIP acceptance, the reference implementation must be completed, during which the status of the ELIP is “In Progress”. Only when the reference implementation is complete and the completion criteria are reached, the status is changed to final.

During the completion of the reference implementation, if the author finds that the ELIP proposal has defects that need to be corrected, then the ELIP can be updated, and the ELIP is automatically changed to the draft state after the correction, and must once again go through the CR consensus process.

The ELIP can also be deferred. When there is no progress in an ELIP, the ELIP author or CR Secretariat can set the status of the ELIP as deferred. CR Secretariat can set the deferred ELIP back to a draft as needed.

The ELIP can also be replaced by a different ELIP, making the original ELIP obsolete. This may occur in the case of Informational ELIPs. For example, API version 2 can replace API version 1, and the status of the replaced ELIP is superseded.

The flow chart of ELIP processing is as follows:


Each ELIP will be rewarded after it is accepted and upon completion. According to the workload and the value of ELIP, the amount could be between 20 ELA and 100 ELA. The author of ELIP proposes the amount to the secretariat when submitting an ELIP. The amount is decided through CR Consensus. An ELIP may also be rejected if the reward is set unreasonably. After the ELIP is accepted, a 50% reward will be issued and when the ELIP is completed, and the remaining 50% will be issued.


Please enter your comment!
Please enter your name here