neobytes/contrib/debian/examples/dash.conf

125 lines
4.5 KiB
Plaintext
Raw Normal View History

##
2015-04-03 00:51:08 +02:00
## dash.conf configuration file. Lines beginning with # are comments.
##
2011-10-25 22:48:36 +02:00
# Network-related settings:
# Run on the test network instead of the real dash network.
#testnet=0
2011-10-25 22:48:36 +02:00
# Run a regression test network
#regtest=0
2011-10-25 22:48:36 +02:00
# Connect via a SOCKS5 proxy
2011-10-25 22:48:36 +02:00
#proxy=127.0.0.1:9050
2015-03-22 03:05:17 +01:00
# 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. ##
##############################################################
2011-10-25 22:48:36 +02:00
# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:9999
2011-10-25 22:48:36 +02:00
# Alternatively use as many connect= settings as you like to connect ONLY to specific peers
2011-10-25 22:48:36 +02:00
#connect=69.164.218.197
#connect=10.0.0.1:9999
2011-10-25 22:48:36 +02:00
# Listening mode, enabled by default except when 'connect' is being used
#listen=1
2011-10-25 22:48:36 +02:00
# Maximum number of inbound+outbound connections.
#maxconnections=
#
# JSON-RPC options (for controlling a running Dash/dashd process)
#
2011-10-25 22:48:36 +02:00
# server=1 tells Dash-Qt and dashd to accept JSON-RPC commands
#server=0
2011-10-25 22:48:36 +02:00
2015-03-22 03:05:17 +01:00
# 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>
2011-10-25 22:48:36 +02:00
# 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
2015-04-03 00:51:08 +02:00
# How many seconds dash will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
#rpcclienttimeout=30
2011-10-25 22:48:36 +02:00
# 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 Dash-Qt to accept JSON-RPC commands.
2015-04-03 00:51:08 +02:00
# it is also read by dashd 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
2011-10-25 22:48:36 +02:00
# Listen for RPC connections on this TCP port:
2015-04-03 00:51:08 +02:00
#rpcport=9998
2011-10-25 22:48:36 +02:00
# You can use Dash or dashd to send commands to Dash/dashd
2011-10-25 22:48:36 +02:00
# running on another host using this option:
#rpcconnect=127.0.0.1
2011-10-25 22:48:36 +02:00
# Transaction Fee Changes in 0.12.0
2011-10-25 22:48:36 +02:00
2015-03-22 03:05:17 +01:00
# Send transactions as zero-fee transactions if possible (default: 0)
#sendfreetransactions=0
2011-10-25 22:48:36 +02:00
2015-03-22 03:05:17 +01:00
# 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
2011-10-25 22:48:36 +02:00
# 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
2011-10-25 22:48:36 +02:00
# Pay an optional transaction fee every time you send dashs. Transactions with fees
2011-10-25 22:48:36 +02:00
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
#paytxfee=0.00
2011-10-25 22:48:36 +02:00
# User interface options
2015-03-18 00:06:58 +01:00
# Start Dash minimized
2011-10-25 22:48:36 +02:00
#min=1
# Minimize to the system tray
#minimizetotray=1