The champion of a LIP should first ensure the idea has not already been discussed on the official LIPs mailing list and that the idea is technologically feasible, both in theory and practice.
Once both the originality and technological feasibility of the idea has been firmly established, the champion should then present the idea as a thread of discussion on the LIPs mailing list. This provides the opportunity for an open discussion with the community and the gathering of consent.
Once the idea is deemed to have been sufficiently researched and peer reviewed, and the idea has garnered considerable traction and popularity among the community, the champion is then free to draft the idea formally as a LIP and open a pull request for it on the LIPs repository.
Once the champion has opened a pull request for the LIP, the LIP editor will then assume their responsibility to ensure the LIP meets all the requirements stated in the LIP Purpose and Guidelines. If all the requirements have been met, the LIP editor will edit the LIP according to the LIP Purpose and Guidelines, assign the LIP a number, then merge the LIP into the LIPs repository. The LIP at this stage is given a "Draft" status.
The Lisk Foundation will at this point decide whether to develop the LIP further into a proposal for the Lisk network. This is done with careful consideration towards how much traction and popularity among the community the LIP has garnered and whether it can be feasibly implemented according to the currently proposed roadmap. The LIP at this stage remains in a "Draft" status.
Should the Lisk Foundation decide to include the LIP on its development roadmap. The Lisk Foundation will instruct its contractors (Lightcurve) to develop an "alpha" implementation of the LIP. The LIP at this stage remains in a "Draft" status.
Once development of the "alpha" implementation has been properly finalised and quality assured, the Lisk Foundation will instruct its contractors (Lightcurve) to prepare a "beta/release" candidate for the Lisk testnet. The LIP at this stage is given a "Proposed" status.
Once the release candidate phase has been deemed by both the community and the Lisk Foundation to have completed successfully, the Lisk Foundation will then instruct its contractors (Lightcurve) to prepare a "production" release as a proposal to the Lisk mainnet. The LIP at this stage remains in a "Proposed" status.
Once the "production" release has been prepared, the Lisk Foundation instructs its contractors (Lightcurve) to schedule a release on the mainnet. At this point, the delegates and nodes of the network will be given a final opportunity to accept or reject the release. The LIP at this stage remains in a "Propose" status.
Should the "production" release become accepted by the majority of nodes on the network the LIP stage is given an "Active" status.