I’ve created a conf file on the next path:
C:UsersNAMEAppDataRoamingBitcoinbitcoin.conf
Once I run the Bitcoind file, nothing occurs. My command line window turns into unresponsive as if it is ready. I’ve waited ~1 hour, and my laptop is fairly highend (i7 processor, 16gb ram).
I wish to run the server and hearth some instructions on the bitcoind server.
I’ve the next conf file:
# bitcoin.conf configuration file. Strains starting with # are feedback.
# Community-related settings:
# Run on the check community as a substitute of the true bitcoin community.
#testnet=0
# Join by way of a socks4 proxy
#proxy=127.0.0.1:9050
##############################################################
## Fast Primer on addnode vs join ##
## As an instance as an example you employ addnode=4.2.2.4 ##
## addnode will join you to and let you know concerning the ##
## nodes related to 4.2.2.4. As well as it can inform ##
## the opposite nodes related to it that you just exist so ##
## they will hook up with you. ##
## join won't do the above while you 'join' to it. ##
## It should *solely* join you to 4.2.2.4 and nobody else.##
## ##
## So for those who're behind a firewall, or produce other issues ##
## discovering nodes, add some utilizing 'addnode'. ##
## ##
## If you wish to keep personal, use 'join' to solely ##
## hook up with "trusted" nodes. ##
## ##
## For those who run a number of nodes on a LAN, there is no want for ##
## all of them to open numerous connections. As a substitute ##
## 'join' all of them to at least one node that's port forwarded ##
## and has numerous connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################
# Use as many addnode= settings as you want to hook up with particular friends
#addnode=69.164.218.197
#addnode=10.0.0.2:8333
# ... or use as many join= settings as you want to attach ONLY
# to particular friends:
#join=69.164.218.197
#join=10.0.0.1:8333
# Don't use Web Relay Chat (irc.lfnet.org #bitcoin channel) to
# discover different friends.
#noirc=0
# Most variety of inbound+outbound connections.
#maxconnections=
# JSON-RPC choices (for controlling a working Bitcoin/bitcoind course of)
server=1 #tells Bitcoin-QT to just accept JSON-RPC instructions.
#server=0
# You will need to set rpcuser and rpcpassword to safe the JSON-RPC api
rpcuser=USERNAME_IVE_CHOSEN
rpcpassword=PASSWORD_IVE_CHOSEN
# What number of seconds bitcoin will wait for an entire RPC HTTP request.
# after the HTTP connection is established.
#rpctimeout=30
# By default, solely RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you want to permit connections from
# different hosts (and you might use * as a wildcard character):
#rpcallowip=10.1.1.34
#rpcallowip=192.168.1.*
# Hear for RPC connections on this TCP port:
#rpcport=8332
# You should use Bitcoin or bitcoind to ship instructions to Bitcoin/bitcoind
# working on one other host utilizing this selection:
#rpcconnect=127.0.0.1
# Use Safe Sockets Layer (also called TLS or HTTPS) to speak
# with Bitcoin -server or bitcoind
#rpcssl=1
# OpenSSL settings used when rpcssl=1
#rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
#rpcsslcertificatechainfile=server.cert
#rpcsslprivatekeyfile=server.pem
# Miscellaneous choices
# Set gen=1 to try to generate bitcoins
#gen=0
# Use SSE directions to attempt to generate bitcoins sooner.
#4way=1
# Pre-generate this many public/personal key pairs, so pockets backups will likely be legitimate for
# each prior transactions and several other dozen future transactions.
#keypool=100
# Pay an elective transaction charge each time you ship bitcoins. Transactions with charges
# are extra probably than free transactions to be included in generated blocks, so could
# be validated sooner.
#paytxfee=0.00
# Enable direct connections for the 'pay by way of IP tackle' characteristic.
#allowreceivebyip=1
# Person interface choices
# Begin Bitcoin minimized
#min=1
# Decrease to the system tray
#minimizetotray=1
Any concepts learn how to make the server work?
