Quote from: SirChiko on July 02, 2014, 08:43:08 PM

Quote from: tdcooper99 on July 02, 2014, 06:54:36 PM

Struggling to solo mine... can anyone tell me if Digibyte is solo minable using the latest (v2.9.1) client?

Even if it would be you won't mine anything with wallet miner as it mines with CPU.

Ha! I guess that was a pretty dumbass newb style post.... "Duh... it's not working, someone tell me why" Embarrassed

It was late and naturally I just assumed the rest of the world understands exactly what I mean all the time Grin

. Anyway, moving on... no of course I'm not trying to CPU mine. I am trying to solo mine with my Zeusminer ASICs... and from what I can gather, having always previously mined using pools, you run the wallet/client software fully synced... ensuring you have a coinname.conf (ie. digibyte.conf) file populated as per the info on the first post of this thread and then in cgminer instead of a :port you use either "localhost:port" if running on the same machine or :port if it's not local... ie on another LAN machine. In my case, I am running my Zeusminers from a Raspberry Pi... and my wallet/client is on a Windows VM hosted elsewhere on my LAN.

I am essentially following the method described here, and it sounds very straightforward:

http://www.miningpools.info/solo-mining/

....and also this is from a thread on Litecointalk....

Quote from: jrose120 on January 09, 2014, 09:48:10 PM

Step one: Setup your wallet and get it synced up (whatever coin you choose, lower the difficulty the better for you)

Step two: Type this into your run box. %appdata% then find the folder for your coin, eg. Casino Coin

Step three: Write a config file, go into the coin's folder, create a txt document. Rename the document to "casinocoin.conf" (all coins use the same format, coin name followed by conf) without the quotes. Make sure there isn't .txt extension at the end or it won't work. Place the following into you conf file. Make sure the file is saved in the %appdata%/casincoin folder, substitute your coin's name for casino.

rpcuser=yourusername
rpcpassword=yourpassword
server=1
rpcport=47970 (WDC uses port 1102, but you can try any port you want, it will work if it's not already in use)
server=1
rpcallowip=192.168.1.* (whatever address your mining rigs are at, if it's running locally skip this step)
rpcconnect=127.0.0.1
gen=0 (set this to zero, or it will use your CPU for mining)
maxconnections=100

Step four: Copy the following files into your coins %appdata%/your coin's name directory if they aren't already there. Most coins come with these three files so you can just grab them out of one of their folders and copy it into the coin you want. If they are already there, great, if not copy minered.exe, libcurl-4.dll, and pthreadGC2.dll into the coin's folder. Your antivirus will probably go off when you do this. Just tell it to put minered.exe back and to keep on going. Or disable your antivirus for this step if you don't know how to allow an exception. Most viruses use the code from that file, so it's flagged regardless.

Step five: Close your client wallet, check task manager to make sure it's not still running, if it is kill it. With your conf file saved and in place reopen your client wallet. It won't look any different when it's running. But now you can connect your mining rig to it. I'm only familiar with CGMiner, but I think the idea is the same with most of the different programs out there.

Step six: Use the failover only command in combination with at least 2 backup mining pools. If your using two different computers, one for a wallet (solo pool), and one as a miner, than you'll setup your miner like this: This is just an example, you'll have to enter your own information. If you want logging enabled then you'll have to create a cgminerlog folder in the route of C:\.

"\cgminer.exe --scrypt -w 256 --thread-concurrency 21712 --no-submit-stale --auto-fan --temp-cutoff 92 --gpu-powertune 20 --gpu-reorder -I 20 --failover-only 2>c:\cgminerlog\logfile.txt --sharelog c:\cgminerlog\share.log -o 192.168.1.100:1234 -u xxx -p xxx -o stratum+tcp://backup_mining_pool_1:1234 -u xxx -p xxx -o stratum+tcp://backup_mining_pool_2:1234 -u xxx -p xxx -o stratum+tcp://backup_mining_pool_3:1234 -u xxx -p xxx -o stratum+tcp://backup_mining_pool_4:1234 -u xxx -p xxx

If your running your wallet locally, substitute "localhost" in place of your ip address. You'll still need to specify a host port, eg. localhost:1234

Step seven: Watch the little windows popup saying "incoming transaction", just like this one, it popped up a few seconds ago. I'm currently mining lottocoin.

Ok, so what I am using is as follows:

My digibyte.conf (located in %appdata%\roaming\digibyte)

Code:

rpcuser=
rpcpassword=
rpcallowip=
listen=1
server=1
daemon=1
gen=0
rpcport=14022
port=12024
addnode=216.250.125.121
addnode=74.208.230.160
addnode=74.112.204.202
addnode=46.4.32.220
addnode=198.27.109.88
addnode=54.204.36.33
addnode=198.41.184.140
addnode=144.76.94.182
addnode=95.85.50.188
addnode=162.159.240.70

My command line to start mining (this works with normal pools without fault):

Code:

./cgminer -o stratum+tcp://:14022 -u -p --chips-count 96 --ltc-clk 328 --nocheck-golden -S /dev/ttyUSB0 -S /dev/ttyUSB1 -S /dev/ttyUSB2

And the result:

Code:

[2014-07-03 08:32:27] Started cgminer 3.1.1
[2014-07-03 08:32:27] Probing for an alive pool
[2014-07-03 08:33:27] No servers were found that could be used to get work from.
[2014-07-03 08:33:27] Please check the details from the list below of the servers you have input
[2014-07-03 08:33:27] Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers
[2014-07-03 08:33:27] Pool: 0 URL: stratum+tcp://:14022 -u -p
[2014-07-03 08:33:27] No servers could be used! Exiting.