6.7.2 Manage local settings

The platform operation parameters are set by the configuration files located in the «DGT-Matagami/CORE/etc» directory. They are then written to the DAG and synchronized:

• Network configuration and its topology are described in the «dgt.net.static», «dgt.net.dyn» and «dgt.net.map» files (see 6.7.1.1)

• General settings are described in the «dgt.conf.static» file

#	Parameter	Default Value	Description
1	dgt.net.time_to_live	2	Number of broadcasts for broadcast messages
2	dgt.ping.counter	0	Counter of ping requests in the network topology, changed by the ping transaction of the topology processor, issued by an external service to check the status of the node
3	dgt.dag.step	4	Step between DAG branch points (after 4 blocks between branches, a new branch will appear)
4	dgt.fbft.leader_shift	0	Defines the change of leader in the cluster (0 – not allowed, 1 – allowed)
5	dgt.fbft.arbiter_shift	0	Defines an arbitrator change
6	dgt.fbft.max_feder_peer	6	The number of nodes in a cluster by default. Can be overridden on a per-cluster basis with the ‘maxpeer’ parameter – see 6.7.1.1
7	dgt.fbft.auto_cluster	1	Allow automatic creation of clusters (if set to 1)
8	dgt.fbft.max_public_cluster	2	Number of public clusters
9	dgt.dag.max_branch	6	Number of DAG “colours”: by default, the number of colours corresponds to the different branches of each cluster; for example, six (6) clusters in a static topology (see 6.7.1.1)
10	dgt.consensus.block_timeout	6.3	Activation of the block formation timer
11	dgt.consensus.min_wait_time	0.01	Minimum waiting time for establishing consensus
12	dgt.consensus.max_wait_time	0.06	Maximum waiting time for establishing consensus prior to start of block closure, affects the number of transactions included in a block
13	dgt.publisher.send_batches	0	Packet forwarding whether packets should be broadcasted to other nodes as soon as they are received by the initiating node
14	dgt.publisher.max_batches_per_block	5	Limit on the number of packets in a block, compliments the time limits
15	dgt.consensus.algorithm	f-bft	f-bft consensus
16	dgt.consensus.version	0.1	Version of the consensus engine
17	dgt.consensus.pbft.full	1	Full cycle f-bft when set to 1, truncated (“fast”) version for debugging purposes
18	dgt.consensus.pbft.max_log_size	20	Log size

• Certificate settings are defined by the «DGT-Matagami/CORE/certificate.json» file (see also 6.3.4). Certificates are used to connect to a private segment and must be edited before the node is launched for the first time. Main parameters (X.509 format) include:

- COUNTRY_NAME: abbreviated name of the country in which the node is running (ex. “CA”)

- STATE_OR_PROVINCE _NAME: region, for example, “ONTARIO”

- LOCALITY_NAME: city of place, for example “BARRIE”

- ORGANIZATION_NAME: the name of the organization, for example “DGT”. Leave this field set to DGT if run by an individual

- COMMON_NAME: mnemonic name of the node, e.g. “John’s node”

- DNS_NAME: network name, for example, “dgt.world”

- EMAIL_ADDRESS: email of the site administrator, for example, “[e-mail]”

- PSEUDONYM: server name or other ID, e.g. MTG-CORE-12.DELL.1

- JURISDICTION_COUNTRY_NAME: name of the jurisdiction, for example, “CA”

- BUSINESS_CATEGORY: this field is provided when the certificate is approved by the segment owner/administrator. Leave this field unchanged for test runs.

- USER_ID: network user number, this field is provided when the certificate is approved by the segment owner/administrator. Leave this field unchanged for test runs.

Working with certificates is done through the transaction family xcert (see 6.5). The certificate is created with the private and public keys in the moment of first launch.

• Monitoring system settings (Grafana, see 6.8.4) are defined by configuration files in the «DGT-Matagami/CORE/etc/Grafana» directory