For the best viewing experience, please turn your phone to portrait mode.

Back to overview

LIP Terminology

LIP - (Lisk Improvement Proposal) a document which technically defines a change of the Lisk protocol, an implementation or non-technical processes surrounding Lisk. The LIP describes the requirements, rationale and motivation for making a change.

The LIP process - the overarching process and guidelines of submitting Lightcurve-championed or Community-championed LIPs.

Champion - The author of a LIP.

Lightcurve-championed LIPs - LIPs authored and submitted by Lightcurve.

Community-championed LIPs - LIPs authored and submitted by community members.

A Standards Track LIP - any change that affects most or all Lisk implementations, such as changes to the network protocol, changes in block or transaction validity rules, or any change that affects the interoperability of applications using Lisk. Standards Track LIPs consist of two parts, a design document and a reference implementation (proof of concept). Within Lightcurve, Standard Track LIPs are generally championed by the Science team.

An Informational LIP - application or network layer, architectural and technical changes specific to the implementation. These are not protocol-level changes. Informational LIPs do not necessarily represent a Lisk community consensus or recommendation, so users wishing to implement their own clients, for example using a language different to Node,js, may ignore these application-specific proposals. Within Lightcurve, Informational LIPs are typically championed by the development teams.

A Process LIP - a process surrounding Lisk, or proposing a change to (or an event in) a process. Process LIPs are like Standards Track LIPs, but apply to areas other than the Lisk protocol itself. They may propose an implementation, but not to Lisk's codebase; they often require community consensus; unlike Informational LIPs, they are more than recommendations, and users are typically not free to ignore them. Examples include procedures, guidelines, changes to the decision-making process, and changes to the tools or environment used in Lisk’s development. Any meta-LIP is also considered a Process LIP. LIP-0001 is an example of a process LIP.

LIP Editor - as a representative of the Lisk Foundation, the LIP editor has the responsibility to ensure every LIP meets all of the requirements stated in the LIP Purpose and Guidelines. They make the final decision on whether to merge a LIP into the LIPs repository.

Lisk Foundation - in this context, the Foundation is responsible for the implementation of the LIP process and the progression through the new roadmap.

We have updated the LIP Guidelines. Here are the main points of change:

  • The guidelines for reaching the status "Proposed" and for proposing a change to the network are less strict
  • A LIP reaches the status "Final" if it is implemented on the chain that is decided to be the Lisk blockchain by the Lisk Foundation.
  • The decision criteria of the Lisk Foundation are made more precise. Decisions with regard to instructing a third party to implement a LIP are based on technical and scientific arguments, feasibility and the objectives of the Lisk Foundation. Decisions with regard to accepting changes/forks are based on several factors, including the acceptance of nodes, delegates and exchanges. You can find the full version of LIP guidelines here.
Written by Lisk - Updated Jun 17