-
Notifications
You must be signed in to change notification settings - Fork 590
/
sample-btcwallet.conf
112 lines (87 loc) · 4.47 KB
/
sample-btcwallet.conf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
[Application Options]
; ------------------------------------------------------------------------------
; Bitcoin wallet settings
; ------------------------------------------------------------------------------
; Use testnet (cannot be used with simnet=1).
; testnet=0
; Use simnet (cannot be used with testnet=1).
; simnet=0
; The directory to open and save wallet, transaction, and unspent transaction
; output files. Two directories, `mainnet` and `testnet` are used in this
; directory for mainnet and testnet wallets, respectively.
; appdata=~/.btcwallet
; ------------------------------------------------------------------------------
; RPC client settings
; ------------------------------------------------------------------------------
; Connect via a SOCKS5 proxy. NOTE: Specifying a proxy will disable listening
; for incoming connections unless listen addresses are provided via the
; 'rpclisten' option.
; proxy=127.0.0.1:9050
; proxyuser=
; proxypass=
; The server and port used for btcd websocket connections.
; rpcconnect=localhost:18334
; File containing root certificates to authenticate a TLS connections with btcd
; cafile=~/.btcwallet/btcd.cert
; ------------------------------------------------------------------------------
; RPC server settings
; ------------------------------------------------------------------------------
; TLS certificate and key file locations
; rpccert=~/.btcwallet/rpc.cert
; rpckey=~/.btcwallet/rpc.key
; Enable one time TLS keys. This option results in the process generating
; a new certificate pair each startup, writing only the certificate file
; to disk. This is a more secure option for clients that only interact with
; a local wallet process where persistent certs are not needed.
;
; This option will error at startup if the key specified by the rpckey option
; already exists.
; onetimetlskey=0
; Specify the interfaces for the RPC server listen on. One rpclisten address
; per line. Multiple rpclisten options may be set in the same configuration,
; and each will be used to listen for connections. 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
; rpclisten=0.0.0.0 ; all ipv4 interfaces on default port
; rpclisten=:: ; all ipv6 interfaces on default port
; rpclisten=:8332 ; all interfaces on port 8332
; rpclisten=0.0.0.0:8332 ; all ipv4 interfaces on port 8332
; rpclisten=[::]:8332 ; all ipv6 interfaces on port 8332
; rpclisten=127.0.0.1:8332 ; only ipv4 localhost on port 8332 (this is a default)
; rpclisten=[::1]:8332 ; only ipv6 localhost on port 8332 (this is a default)
; 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
; Legacy (Bitcoin Core-compatible) RPC listener addresses. Addresses without a
; port specified use the same default port as the new server. Listeners cannot
; be shared between both RPC servers.
;
; Adding any legacy RPC listen addresses disable all default rpclisten options.
; If both servers must run, all listen addresses must be manually specified for
; each.
; legacyrpclisten=
; ------------------------------------------------------------------------------
; RPC settings (both client and server)
; ------------------------------------------------------------------------------
; Username and password to authenticate to btcd a RPC server and authenticate
; new client connections
; username=
; password=
; Alternative username and password for btcd. If set, these will be used
; instead of the username and password set above for authentication to a
; btcd RPC server.
; btcdusername=
; btcdpassword=
; ------------------------------------------------------------------------------
; Debug
; ------------------------------------------------------------------------------
; Debug logging level.
; Valid options are {trace, debug, info, warn, error, critical}
; 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=6062