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

Lisk Core Documentation

Table of contents


We release new versions of Lisk Core regularly. Documentation on will keep up to date with version updates. The table below provides an overview about the former releases and documentation versions of Lisk Core.

Version Release date
Documentation reference
v1.4.0 19/01/07 Current version, live on
v1.3.1 18/12/05 Lisk Core 1.3 docs
v1.2.1 18/11/10 Lisk Core 1.2 docs
v1.1.1 18/10/23 Lisk Core 1.1 docs
v1.0.3 18/08/17 Lisk Core 1.0 docs

What is Lisk Core?

Lisk Core is the program that implements the Lisk Protocol. Every machine must set it up in order to run a node that allows for participation in the network. Setting up Lisk Core enables a user to:

  • Contribute to the decentralisation of the Lisk network
  • Explore data recorded on the Lisk blockchain
  • Post transactions to the Lisk blockchain
  • Enable/Disable forging for a registered delegate
  • Configure Lisk Core to specific needs, as required

An instance of Lisk Core is generally referred to in two different ways:

A Lisk Core instance connected to a network is referred to as a Lisk Node.
A Lisk Node connected to other Lisk Nodes is referred to as a Lisk Peer.

Both meanings refer to a machine which, after installing and executing Lisk Core, becomes a server. The server participates in the network and provides blockchain data to its clients.


Lisk Core can be connected to different networks. There are two key public networks, entirely independent of each other, that are always accessible: Mainnet and Testnet.


Mainnet is where the true Lisk economy exists. On this network, Lisk users are able to transfer LSK tokens from one account to another, register accounts as delegates, vote for another delegates or register dApps. It can be explored via the Lisk Explorer.


Testnet is an independent replica of the Lisk Mainnet intended as an area to rehearse upgrades before they take place on the Lisk Mainet. This is where new versions and fixes of Lisk Core are tested. It can be explored via Lisk Testnet Explorer.

Each connects to a network specified in the config file config.json.
When a user decides which network they wish to connect to, they must follow the correspondent tutorial in the Setup section.


The Lisk Core consists of 4 main components:

Node.js serves as the underlying engine for code execution in Lisk Core. Node.js is an open-source, cross-platform JavaScript run-time environment that executes JavaScript code server-side. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient.

Swagger is an open source software framework backed by a large ecosystem of tools that helps developers design, build, document, and consume RESTful Web services. As part of the Lisk Core documentation, the whole API specification can be explored interactively via the Swagger-UI interface.

PostgreSQL is a powerful, open source object-relational database system with over 30 years of active development which has earned it a strong reputation for reliability, feature robustness, and performance. All Information on the Lisk mainchain is stored inside of PostgreSQL databases.

Redis is an open source, in-memory data structure store. Lisk Core mainly uses it to cache API responses. This prevents performance drops in the application, for example when the same API request is sent repeatedly.

Contribute to the Codebase

Everyone is invited to contribute to the Lisk Core project. We welcome and appreciate all contributions.


All necessary information can be found on our Lisk Core Github.

Contribution Guidelines

Please be sure to read and follow our Contribution Guidelines.


If you have any further questions please join our Gitter.

What's next?