# 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](https://dgtnetwork.gitbook.io/dgt-docs/6.-administrator-guide/6.7.1-dgt-topology#id-6.7.1.1-dgt-topology-settings))
* General settings are described in the «`dgt.conf.static`» file

<table data-header-hidden><thead><tr><th width="70"></th><th width="278"></th><th width="88"></th><th></th></tr></thead><tbody><tr><td>#</td><td>Parameter</td><td>Default Value</td><td>Description</td></tr><tr><td>1</td><td><code>dgt.net.time_to_live</code></td><td>2</td><td>Number of broadcasts for broadcast messages</td></tr><tr><td>2</td><td><code>dgt.ping.counter</code></td><td>0</td><td>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</td></tr><tr><td>3</td><td><code>dgt.dag.step</code></td><td>4</td><td>Step between DAG branch points (after 4 blocks between branches, a new branch will appear)</td></tr><tr><td>4</td><td><code>dgt.fbft.leader_shift</code></td><td>0</td><td>Defines the change of leader in the cluster (0 – not allowed, 1 – allowed)</td></tr><tr><td>5</td><td><code>dgt.fbft.arbiter_shift</code></td><td>0</td><td>Defines an arbitrator change</td></tr><tr><td>6</td><td><code>dgt.fbft.max_feder_peer</code></td><td>6</td><td>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</td></tr><tr><td>7</td><td><code>dgt.fbft.auto_cluster</code></td><td>1</td><td>Allow automatic creation of clusters (if set to 1)</td></tr><tr><td>8</td><td><code>dgt.fbft.max_public_cluster</code></td><td>2</td><td>Number of public clusters</td></tr><tr><td>9</td><td><code>dgt.dag.max_branch</code></td><td>6</td><td>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)</td></tr><tr><td>10</td><td><code>dgt.consensus.block_timeout</code></td><td>6.3</td><td>Activation of the block formation timer</td></tr><tr><td>11</td><td><code>dgt.consensus.min_wait_time</code></td><td>0.01</td><td>Minimum waiting time for establishing consensus</td></tr><tr><td>12</td><td><code>dgt.consensus.max_wait_time</code></td><td>0.06</td><td>Maximum waiting time for establishing consensus prior to start of block closure, affects the number of transactions included in a block</td></tr><tr><td>13</td><td><code>dgt.publisher.send_batches</code></td><td>0</td><td>Packet forwarding whether packets should be broadcasted to other nodes as soon as they are received by the initiating node</td></tr><tr><td>14</td><td><code>dgt.publisher.max_batches_per_block</code></td><td>5</td><td>Limit on the number of packets in a block, compliments the time limits</td></tr><tr><td>15</td><td><code>dgt.consensus.algorithm</code></td><td>f-bft</td><td>f-bft consensus</td></tr><tr><td>16</td><td><code>dgt.consensus.version</code></td><td>0.1</td><td>Version of the consensus engine</td></tr><tr><td>17</td><td><code>dgt.consensus.pbft.full</code></td><td>1</td><td>Full cycle f-bft when set to 1, truncated (“fast”) version for debugging purposes</td></tr><tr><td>18</td><td><code>dgt.consensus.pbft.max_log_size</code></td><td>20</td><td>Log size</td></tr></tbody></table>

* Certificate settings are defined by the «DGT-Matagami/CORE/certificate.json» file (see also [6.3.4](https://dgtnetwork.gitbook.io/dgt-docs/6.-administrator-guide/6.3-dgt-core-setup-private-public-network/6.3.4-attach-node-to-existing-network)). 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, “<adminmail@mail.com>”

\-          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.

&#x20;\-          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](https://dgtnetwork.gitbook.io/dgt-docs/6.-administrator-guide/6.5-dgt-cli-and-base-transaction-families)). The certificate is created with the private and public keys in the moment of first launch.

* Monitoring system settings (Grafana, see [6.8.4](https://dgtnetwork.gitbook.io/dgt-docs/6.-administrator-guide/6.8-dgt-maintenance/6.8.4-log-and-monitoring)) are defined by configuration files in the «DGT-Matagami/CORE/etc/Grafana» directory
