Rebuilds certain database tables on basis of the local blockchain data. Must be followed by an integer, that specifies the last delegate round that should be part of the rebuild. If 0 is specified, all rounds are rebuilt.

LISK_CHILD_PROCESS_MODULES

Comma separated list of modules, that shall be loaded in a separate process. To enable inter process communication, set ipc.enabled to true inside the config.json file.

Utility scripts

There are a couple of command line scripts that facilitate users of lisk to perform handy operations.

All scripts are located under ./scripts/ directory and can be executed directly by node scripts/<file_name>.

Generate Config

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

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

Update Config

This script keeps 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 versions of the Lisk, this scripts will do it for you.

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.

Creating snapshots

For creating snapshots the most convenient way, it is recommended to use Lisk Core from binary distribution.
Just execute the script lisk-snapshot.sh, what will perform all necessary steps to create a snapshot of the blockchain.

To create a snapshot manually, perform the following steps:

Example: Creating a snapshot for Lisk Mainnet.

The template database should be the one defined in components.storage.database in the config.json file of Lisk Core.
Its recommended to document the current block height of the snapshot and to include it in the snapshots' filename.

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.

What's next?

When accessing our website, we obtain and process your personal data. We also use cookies to improve your experience on our site. To find out more about our use of your data, read our updated privacy policy To continue using our website, click „I accept“.