(Solo) Mining KushCoins – Windows 10 Setup

Download a KushCoin package at

https://github.com/kushcoin/KushCoin/releases


Extract contents of the zip to a new folder.


Run Kushcoin-qt.exe once(from the files above) .

You can close Kushcoin-qt after its loaded up.


In the search or run bar of windows type %appdata% (or you can type it directly into the address bar of file manager)

Open the KushCoin file directory located in appdata


Create a new .conf file named kushcoin.conf (Use notepad, “Save As”, mark “All files” instead of “Text file”)

put it into the %appdata%kushcoin/  file

include the following in the conf file:

### kushcoin.conf configuration file. Lines beginning with # are comments.
### Uncomment and edit options you wish to use.

## JSON-RPC options (for controlling a running kushcoin-qt/kushcoind process)

# server=1 tells kushcoin to accept JSON-RPC commands.

server=1
listen=1
daemon=1

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
# You should create your own new random password.
# The username and password MUST NOT be the same.

rpcuser=kushcoinrpc
rpcpassword=201

# How many seconds kushcoin 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=
#rpcallowip=192.168.1.*

# Listen for RPC connections on this TCP port:
rpcport=8332

# You can use kushcoind to send commands to kushcoin-qt/kushcoind
# 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 kushcoin -server or kushcoind
#rpcssl=1

# OpenSSL settings used when rpcssl=1
rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
rpcsslcertificatechainfile=server.cert
rpcsslprivatekeyfile=server.pem

port=9385

## Network-related settings:

# Run on the test network instead of the real kushcoin network.
#testnet=1

# Connect via a socks proxy
#proxy=127.0.0.1:9050

# Select the version of socks proxy to use (4-5, default: 5)
#socks=5

# Use proxy to reach tor hidden services (default: same as -proxy)
#tor=

##############################################################
## 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 attempt connection to specific peers
addnode=192.168.1.*
addnode=45.50.106.152:9385
#or use as many connect= settings as you like to connect ONLY to specific peers:
#connect=192.168.1.20:8333

# Do not use Internet Relay Chat to find peers.
noirc=0

# Maximum number of inbound+outbound connections.
#maxconnections=125

# Miscellaneous options

# Pre-generate this many public/private key pairs, so wallet backups will be valid
# after future transactions.
#keypool=100

# Add an optional transaction fee every time you send kushcoins.
#paytxfee=0.01

# Add timestamps to debug.log
#logtimestamps=1

# User interface options

# Start kushcoin minimized
#min=1

# Minimize to the system tray
minimizetotray=0

Now with your .conf file placed in the %appdata%kushcoin directory, you can restart Kushcoin-qt (it will load the conf file we made automatically from appdata). At this point it should connect to at least one peer.


If your not connecting, you can go to the conf file and add more nodes, just add the following line with the ip of the trusted node you substituted in for 192.168*.*.

addnode=192.168.*.*


To start mining using a GPU:

Now you can grab the GUIminer-Scrypt program from the following link

http://mc2.xwebnetwork.com/storage/guiminer-scrypt_win32_binaries_v0.05.zip


Unzip GUIminer to a folder of your choosing

Start the guiminer program

Host: 127.0.0.1

Port: 8332

User: kushcoinrpc

pass: 201

No stratum for solo mining.

The rest of the settings you will need to read the readme of the miner and research online for the best values. They have defaults for many cards already.


Now with Kushcoin-qt open first, and synced, you can start mining on GUIminer. and it should communicate with kushcoin through the rpc client.

the settings in conf file need to match the settings in guiminer. If you copied the conf from above and the guiminer settings it should be working now.


*Check firewalls and routers to keep port 9385 open for kushcoin to communicate with other users on the system.

 

To mine for a pool you just need to swap the info in guiminer for the credentials provided by the mining pool.

Leave a Reply

Your email address will not be published. Required fields are marked *