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

Lisk Core Source Administration

This section details how to manage a Source installation of Lisk Core. Source installations for use in production are recommended to use a process manager. PM2 is included in the installation document and will be used in this reference.

Basic Commands

Command Description
pm2 start --name lisk app.js Starts Lisk using app.js
pm2 stop lisk Stop Lisk using app.js
pm2 restart lisk Restarts Lisk using app.js
pm2 delete lisk Stops Lisk processes and cleans up pm2 entries for Lisk
pm2 logs Displays the logs of the Lisk process

Start Source Install with PM2

pm2 start --name lisk app.js

After the process is started, its runtime status and log location can be retrieved by issuing the following command:

pm2 show lisk

To stop Lisk after it has been started with pm2, issue the following command:

pm2 stop lisk

Restart Source Install with PM2 (useful for reloading changes to config.json)

pm2 restart lisk

Delete Source Installation with PM2 (useful if removing Lisk Core or rebuilding the source installation entirely)

pm2 delete lisk

View Realtime Logs (useful for troubleshooting issues)

pm2 logs

Command Line Options

There are plenty of options available that you can use to override configuration on runtime while starting Lisk Core.

node app.js -p [port] -a [address] -c [config-path] -n [network]

or with pm2, e.g.:

pm2 start lisk -p [port] -a [address] -c [config-path] -n [network]

You can pass any of devnet (default), alphanet, betanet, testnet or mainnet for the network option.
Each of these options can be appended on command line. There are also few ENV variables that can be utilized for this purpose.

Option ENV Variable Config Option Description
LISK_NETWORK Which configurations set to use, associated to lisk networks. Any of this option can be used devnet, alphanet, betanet, testnet and mainnet. Default value is devnet.
LISK_CONFIG_FILE Path the custom configuration file, which will override values of config/default/config.json
LISK_WS_PORT wsPort TCP port for P2P layer
LISK_ADDRESS address Listening host name or ip
LISK_FILE_LOG_LEVEL fileLogLevel Log level for file output
LISK_CONSOLE_LOG_LEVEL consoleLogLevel Log level for console output
LISK_CACHE_ENABLED cacheEnabled Enable or disable cache. Must be set to true/false
LISK_DB_NAME db.database PostgreSQL database name to connect to
LISK_DB_HOST PostgreSQL database host name
LISK_DB_PORT db.port PostgreSQL database port
LISK_DB_USER db.user PostgreSQL database username to connect to
LISK_DB_PASSWORD db.password PostgreSQL database password to connect to
LISK_REDIS_HOST Redis host name
LISK_REDIS_PORT redis.port Redis port
LISK_REDIS_DB_NAME redis.db Redis database name to connect to
LISK_REDIS_DB_PASSWORD redis.password Redis database password to connect to
LISK_PEERS peers.list Comma separated list of peers to connect to in the format,
LISK_API_PUBLIC api.access.public Enable or disable public access of http API. Must be set to true/false
LISK_API_WHITELIST api.access.whiteList Comma separated list of IPs to enable API access. Format,
LISK_FORGING_DELEGATES forging.delegates Comma separated list of delegates to load in the format publicKey|encryptedPassphrase,publicKey2|encryptedPassphrase2
LISK_FORGING_WHITELIST forging.access.whiteList Comma separated list of IPs to enable access to forging endpoints. Format,
Number of round for which take the snapshot. If none specified it will use the highest round available.


  • All ENV variables restricted with operating system constraint of ENV variable maximum length.
  • Comma separated lists will replace the original config values. e.g. If you specify LISK_PEERS, original peers.list specific to network will be replaced completely.

Utility scripts

There are couple of command line scripts that facilitate users of lisk to perform handy operations.
All scripts are are located under ./scripts/ directory and can be executed directly by node scripts/<file_name>.

Generate Config

This script will help you to generate unified version of configuration file for any network. Here is the usage of the script:

Usage: node scripts/generate_config.js [options]
 -h, --help               output usage information
-V, --version            output the version number
-c, --config [config]    custom config file
-n, --network [network]  specify the network or use LISK_NETWORK

Argument network is required and can by devnet, testnet, mainnet or any other network folder available under ./config directory.

Update Config

This script keep track of all changes introduced in Lisk over time in different versions.
If you have one config file in any of specific version and you want to make it compatible with other version of the Lisk, this scripts will do it for you.

Usage: node scripts/update_config.js [options] <input_file> <from_version> [to_version]
 -h, --help               output usage information
-V, --version            output the version number
-n, --network [network]  specify the network or use LISK_NETWORK
-o, --output [output]    output file path

As you can see from the usage guide, input_file andfrom_version are required.
If you skip to_version argument changes in config.json will be applied up to the latest version of Lisk Core.
If you do not specify --output path the final config.json will be printed to stdout.
If you do not specify --network argument you will have to load it from LISK_NETWORK env variable.


This script is really useful in development. It will initialize the components of Lisk and load these into nodejs REPL.

Usage: node scripts/console.js
 initApplication: Application initialization inside test environment started...
initApplication: Target database - lisk_dev
initApplication: Rewired modules available
initApplication: Fake onBlockchainReady event called
initApplication: Loading delegates...
initApplication: Delegates loaded from config file - 101
initApplication: Done
lisk-core [lisk_dev] >

Once you get the prompt, you can use modules, helpers, logic, db and config objects and play with these in REPL.

Rebuild from a snapshot

In some scenarios it is recommended to restore the blockchain from a snapshot. The command blocks below will perform this process. The URL can be substituted for another blockchain.db.gz snapshot file if desired.


pm2 stop lisk
dropdb lisk_main
createdb lisk_main
gunzip -fcq blockchain.db.gz | psql -d lisk_main
pm2 start lisk


pm2 stop lisk
dropdb lisk_test
createdb lisk_test
gunzip -fcq blockchain.db.gz | psql -d lisk_test
pm2 start lisk

What's next?