Skip to content

Operational Configuration

Eric Voskuil edited this page Mar 20, 2017 · 20 revisions

Default configuration is generally optimal for operational use with the exception of values that cannot be optimally defaulted due to lack of contextual information. The following settings are recommended and otherwise defaults are sufficient. See also initial configuration and additional information below.

[log]
# debug_file = debug.log
# error_file = error.log
# archive_directory = archive
rotation_size = 10000000

[network]
inbound_connections = 8
outbound_connections = 8
channel_expiration_minutes = 1440
# self = 0.0.0.0:0

[database]
# directory = blockchain
flush_writes = false
# cache_capacity = 10000

[blockchain]
cores = 32

[node]
block_poll_seconds = 60
relay_transactions = true

[server]
query_workers = 1
subscription_limit = 1000
heartbeat_interval_seconds = 5
block_service_enabled = true
transaction_service_enabled = true

Log

See Initial Configuration.

Network

These settings re-enable the defaults after Initial Configuration. Also setting self advertises the address to peers so that the node will start to receive incoming connections.

Database

See Initial Configuration.

Blockchain

See Initial Configuration.

Node

Transaction relay should be re-enabled once the node is synchronized. Block polling can be set to 60 seconds once synchronized in order to reduce the occurrence of redundant block downloads.

Server

These settings re-enable the server endpoints and address subscription.

Clone this wiki locally