Configuration

Table of Contents

Using a network-specific default configuration
Using a custom config file
Enabling plugins

A complete command reference with all available options for starting Lisk Core can be found in the Lisk Core CLI.

Using a network-specific default configuration

To quickly connect your Lisk Core node to a specific network, specify the desired network with the --network or -n flag.

This will use the default config file for the specific network when starting Lisk Core. The default configurations are located in the config folder of Lisk Core.

$ lisk-core start --network=NETWORK (1)

1	`NETWORK` may be `mainnet`, `testnet` or `devnet`.

Using a custom config file

Lisk Core uses the default config for connecting to the Mainnet by default.

However, it is possible to use Lisk Core with a custom config, by specifying the path to the config file with the --config or -c flag.

The custom config file needs to follow the JSON config structure of Lisk Core. A straightforward and easy method is to copy one of the network-specific default configs of Lisk Core and adjust it to your requirements.

/home/lisk/

cp .lisk/lisk-core/config/testnet/config.json custom-config.json
vim custom-config.json

If you intend to connect the node to the Mainnet, change testnet to mainnet in the snippet above.

$ lisk-core start --config=/home/lisk/custom-config.json --overwrite-config

Remember to restart the node for the new config changes to take effect.

Enabling plugins

Plugins, including the HTTP API plugin are not enabled by default. Use the dedicated flags to enable them on application start:

$ lisk-core start --enable-forger-plugin --enable-http-api-plugin

Alternatively, enable the plugins directly in the config file, see Using a custom config file.

For more detailed descriptions of the available plugins, go to the Plugins overview.