Skip to content

RSK node configuration

Jump to bottom
Meri Herrera edited this page Jun 14, 2018 · 3 revisions

This article explains how to configure your RSK node:

v0.4.3 or later

From RskJ version 0.4.3 it is not necessary to have a config file to run the node because it can take a default configuration for each network. However, if you need to configure something different to default values, you can set your own config preferences.

v0.4.2 or earlier

If you were using RskJ version 0.4.2 or earlier and you want to preserve your configuration, you must:

  1. Migrate your config file to upgrade it to the last version using the config migration tool.
  2. Specify your own config file path when you run your node.

Setting your own config preferences

It is a bit different if:

to run the node.

Remember: You need to restart the node if you've changed any configuration option

Using Ubuntu, Azure, AWS or Docker

Your node's config file is in /etc/rsk. Default configurations are defined there and they are the same as these ones.

You should edit the config related with the network you are using (mainnet.conf, testnet.conf, regtest.conf). Check here all the configuration options you could change.

Using java command

1. Create a .conf file

You can create a file with the configuration options that you want to replace from the default. Default configurations are defined here.

The extension of the file must be .conf. Check here all the configuration options you could change.

As an example, if you want to change the default database directory, your config file should only contain:

database {
    dir = /new/path/for/database
    reset = false
}

2. Specify your config file path

To apply your configuration options, you need to set your own config file's path when you run your node. It could be done:

  • Running the node with de java command, add -Drsk.conf.file=path/to/your/file.conf
  • Compiling the node with IntelliJ, add to VM options: -Drsk.conf.file=path/to/your/file.conf

Developers Portal

Clone this wiki locally