Lisk Core


The Lisk Core blockchain client is an implementation of the Lisk protocol that verifies data (blocks and transactions) against the protocol rules and keeps the network secure.

To provide a high level overview, the main functionalities are listed below:

  • The possibility to connect to a subset of peers in the Lisk mainchain’s P2P network.

  • To synchronize with the Lisk blockchain including requesting, forwarding and processing of the blocks, which also contain the transactions.

  • To maintain the transaction pool, which might contain a subset of unconfirmed transactions.

  • To request and forward the unconfirmed transactions.

  • To possibly generate new blocks when running a validator node.

Furthermore, Lisk Core nodes are able to store all current addresses, balances, and transactions.

With the latest version of Lisk Core, there will be new configurable settings and the modules described in the Modules sub-section will also be used.


The Lisk Core v4 makes full use of the modules defined by Lisk SDK v6. Apart from the aforementioned modules, Lisk Core has an additional module called the Legacy module.

  • The Legacy module maintains all accounts on the Lisk mainchain that received balance transfers to their address in the old 8-byte format, and for which no public key is associated. The Legacy module also implements a command allowing validators without a BLS key to register one.


The Lisk Core can be connected to different networks. Please be aware that there are two key accessible public networks existing which are entirely independent of each other. These networks are covered below in this section.

Table 1. Public networks of Lisk
Network Port (default)






The Mainnet is where the true Lisk economy exists. Within this network the Lisk users can transfer LSK tokens from one account to another, register accounts as validators, and vote for other validators.

Mainnet blockchain explorer


The Testnet is an independent replica of the Lisk Mainnet, whose main function is to test the upgrades first before they are run on the Lisk Mainnet. Subsequently, this is where new/updated versions and fixes of the Lisk Core are tested.

To start using the Testnet, please download your free LSK Testnet from the Testnet faucet.

To connect to the Testnet via Lisk Desktop, simply enable the "Network Switcher" in the settings and then use it to switch the network to Testnet.


Table 2. Available APIs for Lisk nodes
API Transport Architecture Port (default) Comment Reference

RPC Endpoints



Depends on the network, see: Networks

To enable, enable RPC websockets in the node config.

RPC endpoints

The Lisk API documentation can be found here.


The native token for the Lisk Mainchain is the LSK. Each LSK is further subdivided into 108 Beddows. At this time there are no other tokens supported.