SON configuration - Version 1.6.0
Configuration file
The config.ini file consist of all the necessary details to configure the node based on the operator's requirements. It has the option to enable/disable the use of specific asset, endpoint, wallets, etc.,
The set of active plugin options such as witness, debug_witness, account_history, market_history, and peerplay_sidechain are available.
There are other set of plugins such as elastic_search, es_object, snapshot, and delayed_node available to use based on the operator's requirements. (Disabled by default)
The config.ini can be divided into two section,
End point configuration
Plugin options (only active configurations are explained here)
1. End point configuration
The user must provide the details such as which network interfaces & ports to listen on and which seed nodes to use for peer discovery. Also, to be a SONs operator, the relevant plugin must be enabled.
The default configuration file looks as follows:
# Endpoint for P2P node to listen on
p2p-endpoint = 0.0.0.0:9777
# P2P nodes to connect to on startup (may specify multiple times)
# seed-node =
# JSON array of P2P nodes to connect to on startup
seed-nodes = []
# Pairs of [BLOCK_NUM,BLOCK_ID] that should be enforced as checkpoints.
# checkpoint =
# Endpoint for websocket RPC to listen on
rpc-endpoint = 127.0.0.1:8090
# Endpoint for TLS websocket RPC to listen on
# rpc-tls-endpoint =
# The TLS certificate file for this server
# server-pem =
# Password for this certificate
# server-pem-password =
# File to read Genesis State from
genesis-json = /peerplays/son-genesis.json
# Block signing key to use for init witnesses, overrides genesis file
# dbg-init-key =
# JSON file specifying API permissions
# api-access =
# Whether to enable tracking of votes of standby witnesses and committee members. Set it to true to provide accurate data to API clients, set to false for slightly better performance.
# enable-standby-votes-tracking =
# Space-separated list of plugins to activate
plugins = account_history accounts_list affiliate_stats bookie market_history witnessOnly the essential details to configure SON node is mentioned below. The operator must provide their details for configuration. Example configuration values as follows:
2. Plugin Options
The list of active plugins available in the config file are,
witness
debug_witness
account_history
market_history
peerplay_sidechain
2.1 witness
The witness plugin default config is provided below and there is no manual configuration required if the SON operator is not also a block-producing witness on the same machine.
2.2 debug_witness
The debug_witness default config is provided below. By default the keys will be added after the node creation,
2.3 account_history
The account_history default config is provided below and no manual changes are required unless your use case necessitates it.
2.4 market_history
The market_history default config is provided below and no manual changes are required unless required.
2.5 peerplays_sidechain
This plugin consists of all the necessary details about various asset, IPs, private keys, wallet details, and API endpoints. In order to make the SON node work as required, the operator must carefully input their values and requirement in this configuration.
The default plugin configuration is mentioned below,
An example configuration to enable basic requirements for a SON node is explained below,
Config file contains all the default public/private keys for SON account, no changes are required here. But unused key pairs may be removed.
List of keypairs is ordered. The first one belongs to sonaccount1, last to sonaccount16
How to find the value of a SON account?
By using the cli_wallet, the SON account information, private key can be collected. Execute the below command in the wallet,
The config parameter should look like the below example,
Last updated
Was this helpful?