diff options
Diffstat (limited to 'bitcoin.conf')
| -rw-r--r-- | bitcoin.conf | 137 |
1 files changed, 137 insertions, 0 deletions
diff --git a/bitcoin.conf b/bitcoin.conf new file mode 100644 index 000000000000..2e279e4669fd --- /dev/null +++ b/bitcoin.conf @@ -0,0 +1,137 @@ +## +## bitcoin.conf configuration file. Lines beginning with # are comments. +## + +# Network-related settings: + +# Run on the test network instead of the real bitcoin network. +#testnet=0 + +# Run a regression test network +#regtest=0 + +# Connect via a SOCKS5 proxy +#proxy=127.0.0.1:9050 + +# Bind to given address and always listen on it. Use [host]:port notation for IPv6 +#bind=<addr> + +# Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6 +#whitebind=<addr> + +############################################################## +## Quick Primer on addnode vs connect ## +## Let's say for instance you use addnode=4.2.2.4 ## +## addnode will connect you to and tell you about the ## +## nodes connected to 4.2.2.4. In addition it will tell ## +## the other nodes connected to it that you exist so ## +## they can connect to you. ## +## connect will not do the above when you 'connect' to it. ## +## It will *only* connect you to 4.2.2.4 and no one else.## +## ## +## So if you're behind a firewall, or have other problems ## +## finding nodes, add some using 'addnode'. ## +## ## +## If you want to stay private, use 'connect' to only ## +## connect to "trusted" nodes. ## +## ## +## If you run multiple nodes on a LAN, there's no need for ## +## all of them to open lots of connections. Instead ## +## 'connect' them all to one node that is port forwarded ## +## and has lots of connections. ## +## Thanks goes to [Noodle] on Freenode. ## +############################################################## + +# Use as many addnode= settings as you like to connect to specific peers +#addnode=69.164.218.197 +#addnode=10.0.0.2:8333 + +# Alternatively use as many connect= settings as you like to connect ONLY to specific peers +#connect=69.164.218.197 +#connect=10.0.0.1:8333 + +# Listening mode, enabled by default except when 'connect' is being used +#listen=1 + +# Maximum number of inbound+outbound connections. +#maxconnections= + +# +# JSON-RPC options (for controlling a running Bitcoin/bitcoind process) +# + +# server=1 tells Bitcoin-Qt and bitcoind to accept JSON-RPC commands +server=1 + +# Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6. +# This option can be specified multiple times (default: bind to all interfaces) +#rpcbind=<addr> + +# You must set rpcuser and rpcpassword to secure the JSON-RPC api +rpcuser=bitcoin +rpcpassword=secret + +# How many seconds bitcoin will wait for a complete RPC HTTP request. +# after the HTTP connection is established. +rpctimeout=300 + +# By default, only RPC connections from localhost are allowed. +# Specify as many rpcallowip= settings as you like to allow connections from other hosts, +# either as a single IPv4/IPv6 or with a subnet specification. + +# NOTE: opening up the RPC port to hosts outside your local trusted network is NOT RECOMMENDED, +# because the rpcpassword is transmitted over the network unencrypted. + +# server=1 tells Bitcoin-Qt to accept JSON-RPC commands. +# it is also read by bitcoind to determine if RPC should be enabled +#rpcallowip=10.1.1.34/255.255.255.0 +#rpcallowip=1.2.3.4/24 +#rpcallowip=2001:db8:85a3:0:0:8a2e:370:7334/96 +rpcallowip=127.0.0.1 + +# Listen for RPC connections on this TCP port: +rpcport=8332 + +# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind +# running on another host using this option: +rpcconnect=127.0.0.1 + +# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate +# with Bitcoin -server or bitcoind (will be removed in core 0.12) +rpcssl=1 + +# OpenSSL settings used when rpcssl=1 +rpcsslciphers=TLSv1.2+HIGH:TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!3DES:@STRENGTH +rpcsslcertificatechainfile=/etc/bitcoin/server.cert +rpcsslprivatekeyfile=/etc/bitcoin/server.pem + +# Transaction Fee Changes in 0.10.0 + +# Send transactions as zero-fee transactions if possible (default: 0) +#sendfreetransactions=0 + +# Create transactions that have enough fees (or priority) so they are likely to +# begin confirmation within n blocks (default: 2). +# This setting is over-ridden by the -paytxfee option. +txconfirmtarget=2 + +# Miscellaneous options + +# Pre-generate this many public/private key pairs, so wallet backups will be +# valid for both prior transactions and several dozen future transactions. +#keypool=100 + +# 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. (default: 0.00) +paytxfee=0.00 + +# Spam control options + +# Fees smaller than this (in satoshi) are considered zero fee +# (relaying and mining) (default: 0.00005) +-minrelaytxfee=0.00005 + +# Rate-limit free transactions to <n>*1000 bytes per minute +# (will be obsolete in core 0.12) (default: 15) +-limitfreerelay=5 |