BITCOIN.CONF(5)

NAME
bitcoin.conf - bitcoin configuration file

SYNOPSIS
All command-line options (except for '-conf') may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file.

The configuration file is a list of 'setting=value' pairs, one per line, with optional comments starting with the '#' character.

The configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, bitcoind(1) will look for a file named bitcoin.conf(5) in the bitcoin data directory, but both the data directory and the configuration file path may be changed using the '-datadir' and '-conf' command-line arguments.

LOCATION
bitcoin.conf should be located in $HOME/.bitcoin

NETWORK-RELATED SETTINGS

testnet=['1'|'0']
    Enable or disable run on the test network instead of the real *bitcoin* network.

proxy='127.0.0.1:9050'
    Connect via a socks4 proxy.

addnode='10.0.0.2:8333'
    Use as many *addnode=* settings as you like to connect to specific peers.

connect='10.0.0.1:8333'
    Use as many *connect=* settings as you like to connect ONLY to specific peers.

maxconnections='value'
    Maximum number of inbound+outbound connections.

JSON-RPC OPTIONS

server=['1'|'0']
    Tells *bitcoin* to accept or not accept JSON-RPC commands.

rpcuser='username'
    You must set *rpcuser* to secure the JSON-RPC api.

rpcpassword='password'
    You must set *rpcpassword* to secure the JSON-RPC api.

rpcallowip='192.168.1.*'
    By default, only RPC connections from localhost are allowed. Specify as many *rpcallowip=* settings as you like to allow connections from other hosts (and you may use * as a wildcard character).

rpcport='8332'
    Listen for RPC connections on this TCP port.

rpcconnect='127.0.0.1'
    You can use *bitcoin* or *bitcoind(1)* to send commands to *bitcoin*/*bitcoind(1)* running on another host using this option.

rpcssl='1'
    Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate with *bitcoin* '-server' or *bitcoind(1)*. Example of OpenSSL settings used when *rpcssl*='1':

-rpcsslciphers=<ciphers>
    Acceptable ciphers (default: TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH)

rpcsslcertificatechainfile='server.cert'

rpcsslprivatekeyfile='server.pem'

MISCELLANEOUS OPTIONS

gen=['0'|'1']
    Enable or disable attempt to generate bitcoins.

4way=['0'|'1']
    Enable or disable use SSE instructions to try to generate bitcoins faster.

keypool='100'
    Pre-generate this many public/private key pairs, so wallet backups will be valid for both prior transactions and several dozen future transactions.

paytxfee='0.00'
    Pay an optional transaction fee every time you send bitcoins. Transactions with fees are more likely than free transactions to be included in generated blocks, so may be validated sooner.

allowreceivebyip='1'
    Allow direct connections for the 'pay via IP address' feature.

USER INTERFACE OPTIONS

min=['0'|'1']
    Enable or disable start bitcoind minimized.

minimizetotray=['0'|'1']
    Enable or disable minimize to the system tray.

SEE ALSO
bitcoind(1)

AUTHOR
This manual page was written by Micah Anderson <micah@debian.org> for the Debian system (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 or any later version published by the Free Software Foundation. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL.