Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ##
- ## bitcoin.conf configuration file. Lines beginning with # are comments.
- ##
- # Wallet and Data settings:
- # Directory that contains the blockchains
- datadir=/mnt/crypto-currency/bitcoin
- # Load wallet file (within data directory)
- wallet=main-wallet.dat
- # 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
- addnode=173.31.108.79:8333
- addnode=124.171.164.75:8333
- addnode=88.238.152.170:8333
- addnode=73.242.201.39:8333
- addnode=81.169.180.9:8333
- addnode=59.110.50.141:10101
- addnode=24.171.76.137:8333
- addnode=125.170.189.32:8333
- addnode=91.37.1.187:8333
- addnode=188.129.102.53:8333
- addnode=90.230.64.156:8333
- addnode=27.223.201.54:8333
- addnode=121.43.38.26:8333
- addnode=46.244.52.154:8333
- addnode=76.175.106.199:8333
- addnode=66.103.169.36:8333
- addnode=85.214.197.165:8333
- addnode=149.202.184.186:8333
- addnode=81.155.251.247:8333
- addnode=149.202.177.168:8333
- addnode=86.13.149.80:8333
- addnode=94.60.167.232:8333
- addnode=186.18.102.252:8333
- addnode=66.43.209.193:8333
- addnode=62.101.171.109:8333
- addnode=58.218.200.146:8333
- addnode=90.149.81.79:8333
- addnode=188.226.141.208:8333
- addnode=80.34.35.221:8333
- addnode=82.10.189.96:8333
- addnode=84.112.18.49:8333
- addnode=88.116.212.122:8333
- addnode=104.34.199.125:8333
- addnode=95.84.153.136:8333
- addnode=151.66.159.120:8333
- addnode=109.154.254.172:30000
- addnode=31.41.247.133:8333
- addnode=84.46.4.66:8333
- addnode=83.249.47.62:8333
- addnode=78.53.0.7:8333
- #nodelist
- # 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=0
- 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=Ulysseys
- #rpcpassword=YourSuperGreatPasswordNumber_DO_NOT_USE_THIS_OR_YOU_WILL_GET_ROBBED_385593
- rpcuser=coal
- rpcpassword=<pw>
- # How many seconds bitcoin will wait for a complete RPC HTTP request.
- # after the HTTP connection is established.
- #rpcclienttimeout=30
- # 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=192.168.0.0/24
- # Listen for RPC connections on this TCP port:
- #rpcport=8332
- rpcport=3859
- # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
- # running on another host using this option:
- #rpcconnect=127.0.0.1
- # 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: 1).
- # This setting is over-ridden by the -paytxfee option.
- #txconfirmtarget=n
- # 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.
- #paytxfee=0.00
- # User interface options
- # Start Bitcoin minimized
- #min=1
- # Minimize to the system tray
- #minimizetotray=1
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement