forked from novacoin-project/novacoin
-
Notifications
You must be signed in to change notification settings - Fork 122
Sample configuration
CryptoManiac edited this page Mar 14, 2014
·
5 revisions
Please note that the following example isn't purposed for production use. It was placed here to help describe the purpose of some of the settings
# novacoin.conf configuration file. Lines beginning with # are comments.
# Network-related settings:
# Run on the test network instead of the real novacoin network.
#testnet=0
# Connect via a socks4 proxy - default none
#proxy=127.0.0.1:9050
# Accepting incoming connections
#listen=1
# Enable UPnP negotiation with router/firewall to accept incoming connections
#upnp=1
##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=193.23.181.148 ##
## addnode will connect you to and tell you about the nodes ##
## connected to 193.23.181.148. 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 193.23.181.148 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=193.23.181.148
#addnode=91.235.143.61:7777
# ... or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=193.23.181.148
#connect=91.235.143.61:7777
# Maximum number of inbound+outbound connections.
#maxconnections=
# JSON-RPC options (for controlling a running novacoind process)
# 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
# How many seconds novacoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
#rpctimeout=30
# 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):
#rpcallowip=10.1.1.34
#rpcallowip=192.168.1.*
# Listen for RPC connections on this TCP port:
#rpcport=8344
# You can use novacoind to send commands to novacoind
# 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 novacoind
#rpcssl=1
# OpenSSL settings used when rpcssl=1
#rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
#rpcsslcertificatechainfile=server.cert
#rpcsslprivatekeyfile=server.pem
# 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
# Data directory path, your keys store, copy of blockchain and unspent outputs index are stored here.
#datadir=D:\NovaCoin
# Wallet file name
#wallet=wallet.dat
# Checkpoints policy (possible values are strict and advisory)
#cppolicy=strict
# Require a confirmations for change (disabled by default)
#confchange=0
# Enforce transaction scripts to use canonical PUSH operators
enforcecanonical=1