|BITCOIN.CONF(5)||File Formats Manual||BITCOIN.CONF(5)|
bitcoin.conf - bitcoin configuration file
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.
bitcoin.conf should be located in $HOME/.bitcoin
- Enable or disable run on the test network instead of the real *bitcoin* network.
- Connect via a socks4 proxy.
- Use as many *addnode=* settings as you like to connect to specific peers.
- Use as many *connect=* settings as you like to connect ONLY to specific peers.
- Maximum number of inbound+outbound connections.
- Tells *bitcoin* to accept or not accept JSON-RPC commands.
- You must set *rpcuser* to secure the JSON-RPC api.
- You must set *rpcpassword* to secure the JSON-RPC api.
- 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).
- Listen for RPC connections on this TCP port.
- You can use *bitcoin* or *bitcoind(1)* to send commands to *bitcoin*/*bitcoind(1)* running on another host using this option.
- 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':
- Acceptable ciphers (default: TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH)
- Enable or disable attempt to generate bitcoins.
- Enable or disable use SSE instructions to try to generate bitcoins faster.
- Pre-generate this many public/private key pairs, so wallet backups will be valid for both prior transactions and several dozen future transactions.
- 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.
- Allow direct connections for the 'pay via IP address' feature.
USER INTERFACE OPTIONS¶
This manual page was written by Micah Anderson <firstname.lastname@example.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.
|January 2011||bitcoin.conf 3.19|