lbcwallet/sample-btcwallet.conf
Josh Rickmar 17ebf9461f Rename connect option to rpcconnect.
The connect option is already used by btcd to force a connection to
other full node peers.  Wallet does not talk directly with these
peers, so the connect option is being renamed to something unique for
an RPC client connection.
2014-05-06 13:25:56 -05:00

93 lines
3.7 KiB
Text

[Application Options]
; ------------------------------------------------------------------------------
; Bitcoin wallet settings
; ------------------------------------------------------------------------------
; Use mainnet.
; mainnet=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.
; datadir=~/.btcwallet
; Maximum number of addresses to generate for the keypool
; keypoolsize=100
; Whether transactions must be created with some minimum fee, even if the
; calculated transaction priority is high enough to allow a free tx
; disallowfree = false
; ------------------------------------------------------------------------------
; 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
; 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 'mainnet', 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=:18332 ; all interfaces on port 18332
; rpclisten=0.0.0.0:18332 ; all ipv4 interfaces on port 18332
; rpclisten=[::]:18332 ; all ipv6 interfaces on port 18332
; rpclisten=127.0.0.1:18332 ; only ipv4 localhost on port 18332 (this is a default)
; rpclisten=[::1]:18332 ; only ipv6 localhost on port 18332 (this is a default)
; rpclisten=127.0.0.1:18337 ; only ipv4 localhost on non-standard port 18337
; rpclisten=:18337 ; all interfaces on non-standard port 18337
; rpclisten=0.0.0.0:18337 ; all ipv4 interfaces on non-standard port 18337
; rpclisten=[::]:18337 ; all ipv6 interfaces on non-standard port 18337
; ------------------------------------------------------------------------------
; RPC settings (both client and server)
; ------------------------------------------------------------------------------
; Username and password to authenticate to btcd a RPC server and authenticate
; new client connections
; username=
; password=
; ------------------------------------------------------------------------------
; 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