Running on mainnet
Grab the latest release (or, if you prefer, compile yourself using the instructions below) You can also download the latest release from the Signum homepage.
In the conf directory, copy node-default.properties into a new file named node.properties and modify this file to suit your needs (See "Configuration" section below)
To run the node, double-click on signum-node.exe (if on Windows) or run java -jar signum-node.jar. On most systems, this will show you a monitoring window and create a tray icon to show that the Signum node is running. To disable this, run java -jar signum-node.jar --headless instead.
The config file is mainnet ready! If you copy the above file, your node can connect to the mainnet and load the chain.
No configuration change is needed to run the node for the mainnet with the default options. All default/recommended parameters are defined in code by the Signum Node, but you can overwrite the parameter within the config file to suit your needs. The default values for the available settings are shown in the config file as commented out.
By default, Signum Node uses SQLite(file-based) as a database. If you like to use MariaDB, you will need to adjust your conf/node.properties:
Please modify the DB.Url to your specifications (port 3306 is the standard port from MariaDB) and also set the DB. Username and DB.Password according to your setup for the created database.
By default, the UPnP port forwarding is activated. You can deactivate the node on a VPS by setting it to "no".
If you run the minimum requirement, you can turn off the indirectIncomingService in the config file to reduce CPU and file usage. By default, this parameter is activated.