178e60a66e
The debuglevel parameter has accepted subsystems in additional to an overall level for quite some time, but the sample config file was not updated to reflect that. This commit updates the sample config file accordingly.
173 lines
7.9 KiB
Plaintext
173 lines
7.9 KiB
Plaintext
[Application Options]
|
|
|
|
; ------------------------------------------------------------------------------
|
|
; Data settings
|
|
; ------------------------------------------------------------------------------
|
|
|
|
; The directory to store data such as the block chain and peer addresses. The
|
|
; block chain takes several GB, so this location must have a lot of free space.
|
|
; The default is ~/.btcd/data on POSIX OSes, $LOCALAPPDATA/Btcd/data on Windows,
|
|
; ~/Library/Application Support/Btcd/data on Mac OS, and $home/btcd/data on
|
|
; Plan9. Environment variables are expanded so they may be used. NOTE: Windows
|
|
; environment variables are typically %VARIABLE%, but they must be accessed with
|
|
; $VARIABLE here. Also, ~ is expanded to $LOCALAPPDATA on Windows.
|
|
; datadir=~/.btcd/data
|
|
|
|
|
|
; ------------------------------------------------------------------------------
|
|
; Network settings
|
|
; ------------------------------------------------------------------------------
|
|
|
|
; Use testnet.
|
|
; testnet=1
|
|
|
|
; Connect via a SOCKS5 proxy. NOTE: Specifying a proxy will disable listening
|
|
; for incoming connections unless listen addresses are provided via the 'listen'
|
|
; option.
|
|
; proxy=127.0.0.1:9050
|
|
; proxyuser=
|
|
; proxypass=
|
|
|
|
; The SOCKS5 proxy above is assumed to be Tor (https://www.torproject.org).
|
|
; If the proxy is not tor the the following my be used to prevent using
|
|
; tor specific SOCKS queries to lookup addresses (this increases anonymity when
|
|
; tor is used by preventing your IP being leaked via DNS).
|
|
; noonion=1
|
|
|
|
; Use an alternative proxy to connect to .onion addresses. The proxy is assumed
|
|
; to be a Tor node. Non .onion addresses will be contacted with the main proxy
|
|
; or without a proxy if none is set.
|
|
; onion=127.0.0.1:9051
|
|
|
|
; ******************************************************************************
|
|
; Summary of 'addpeer' versus 'connect'.
|
|
;
|
|
; Only one of the following two options, 'addpeer' and 'connect', may be
|
|
; specified. Both allow you to specify peers that you want to stay connected
|
|
; with, but the behavior is slightly different. By default, btcd will query DNS
|
|
; to find peers to connect to, so unless you have a specific reason such as
|
|
; those described below, you probably won't need to modify anything here.
|
|
;
|
|
; 'addpeer' does not prevent connections to other peers discovered from
|
|
; the peers you are connected to and also lets the remote peers know you are
|
|
; available so they can notify other peers they can to connect to you. This
|
|
; option might be useful if you are having problems finding a node for some
|
|
; reason (perhaps due to a firewall).
|
|
;
|
|
; 'connect', on the other hand, will ONLY connect to the specified peers and
|
|
; no others. It also disables listening (unless you explicitly set listen
|
|
; addresses via the 'listen' option) and DNS seeding, so you will not be
|
|
; advertised as an available peer to the peers you connect to and won't accept
|
|
; connections from any other peers. So, the 'connect' option effectively allows
|
|
; you to only connect to "trusted" peers.
|
|
; ******************************************************************************
|
|
|
|
; Add persistent peers to connect to as desired. One peer per line.
|
|
; You may specify each IP address with or without a port. The default port will
|
|
; be added automatically if one is not specified here.
|
|
; addpeer=192.168.1.1
|
|
; addpeer=10.0.0.2:8333
|
|
; addpeer=fe80::1
|
|
; addpeer=[fe80::2]:8333
|
|
|
|
; Add persistent peers that you ONLY want to connect to as desired. One peer
|
|
; per line. You may specify each IP address with or without a port. The
|
|
; default port will be added automatically if one is not specified here.
|
|
; NOTE: Specifying this option has other side effects as described above in
|
|
; the 'addpeer' versus 'connect' summary section.
|
|
; connect=192.168.1.1
|
|
; connect=10.0.0.2:8333
|
|
; connect=fe80::1
|
|
; connect=[fe80::2]:8333
|
|
|
|
; Maximum number of inbound and outbound peers.
|
|
; maxpeers=8
|
|
|
|
; How long to ban misbehaving peers. Valid time units are {s, m, h}.
|
|
; Minimum 1s.
|
|
; banduration=24h
|
|
; banduration=11h30m15s
|
|
|
|
; Disable DNS seeding for peers. By default, when btcd starts, it will use
|
|
; DNS to query for available peers to connect with.
|
|
; nodnsseed=1
|
|
|
|
; Specify the interfaces to listen on. One listen address per line.
|
|
; NOTE: The default port is modified by some options such as 'testnet', so it is
|
|
; recommended to not specify a port and allow a proper default to be chosen
|
|
; unless you have a specific reason to do otherwise.
|
|
; listen= ; all interfaces on default port (this is the default)
|
|
; listen=0.0.0.0 ; all ipv4 interfaces on default port
|
|
; listen=:: ; all ipv6 interfaces on default port
|
|
; listen=:8333 ; all interfaces on port 8333
|
|
; listen=0.0.0.0:8333 ; all ipv4 interfaces on port 8333
|
|
; listen=[::]:8333 ; all ipv6 interfaces on port 8333
|
|
; listen=127.0.0.1:8333 ; only ipv4 localhost on port 8333
|
|
; listen=[::1]:8333 ; only ipv6 localhost on port 8333
|
|
; listen=127.0.0.1:8336 ; only ipv4 localhost on non-standard port 8336
|
|
; listen=:8336 ; all interfaces on non-standard port 8336
|
|
; listen=0.0.0.0:8336 ; all ipv4 interfaces on non-standard port 8336
|
|
; listen=[::]:8336 ; all ipv6 interfaces on non-standard port 8336
|
|
|
|
; Disable listening for incoming connections. This will override all listeners.
|
|
; nolisten=1
|
|
|
|
|
|
; ------------------------------------------------------------------------------
|
|
; RPC server options - The following options control the built-in RPC server
|
|
; which is used to control and query information from a running btcd process.
|
|
;
|
|
; NOTE: The RPC server is disabled by default if no rpcuser or rpcpass is
|
|
; specified.
|
|
; ------------------------------------------------------------------------------
|
|
|
|
; Secure the RPC API by specifying the username and password. You must specify
|
|
; both or the RPC server will be disabled.
|
|
; rpcuser=whatever_username_you_want
|
|
; rpcpass=
|
|
|
|
; Specify the interfaces for the RPC server listen on. One listen address per
|
|
; line. NOTE: The default port is modified by some options such as 'testnet',
|
|
; so it is recommended to not specify a port and allow a proper default to be
|
|
; chosen unless you have a specific reason to do otherwise.
|
|
; rpclisten= ; all interfaces on default port (this is the default)
|
|
; rpclisten=0.0.0.0 ; all ipv4 interfaces on default port
|
|
; rpclisten=:: ; all ipv6 interfaces on default port
|
|
; rpclisten=:8334 ; all interfaces on port 8334
|
|
; rpclisten=0.0.0.0:8334 ; all ipv4 interfaces on port 8334
|
|
; rpclisten=[::]:8334 ; all ipv6 interfaces on port 8334
|
|
; rpclisten=127.0.0.1:8334 ; only ipv4 localhost on port 8334
|
|
; rpclisten=[::1]:8334 ; only ipv6 localhost on port 8334
|
|
; rpclisten=127.0.0.1:8337 ; only ipv4 localhost on non-standard port 8337
|
|
; rpclisten=:8337 ; all interfaces on non-standard port 8337
|
|
; rpclisten=0.0.0.0:8337 ; all ipv4 interfaces on non-standard port 8337
|
|
; rpclisten=[::]:8337 ; all ipv6 interfaces on non-standard port 8337
|
|
|
|
; Specify the maximum number of concurrent RPC clients for standard connections.
|
|
; rpcmaxclients=10
|
|
|
|
; Specify the maximum number of concurrent RPC websocket clients.
|
|
; rpcmaxwebsockets=25
|
|
|
|
; Use the following setting to disable the RPC server even if the rpcuser and
|
|
; rpcpass are specified above. This allows one to quickly disable the RPC
|
|
; server without having to remove credentials from the config file.
|
|
; norpc=1
|
|
|
|
|
|
; ------------------------------------------------------------------------------
|
|
; Debug
|
|
; ------------------------------------------------------------------------------
|
|
|
|
; Debug logging level.
|
|
; Valid levels are {trace, debug, info, warn, error, critical}
|
|
; You may also specify <subsystem>=<level>,<subsystem2>=<level>,... to set
|
|
; log level for individual subsystems. Use btcd --debuglevel=show to list
|
|
; available subsystems.
|
|
; debuglevel=info
|
|
|
|
; The port used to listen for HTTP profile requests. The profile server will
|
|
; be disabled if this option is not specified. The profile information can be
|
|
; accessed at http://localhost:<profileport>/debug/pprof once running.
|
|
; profile=6061
|