Solomining on new Digibyte core wallet v6.14.2
In Digibyte v6.14.2 "getwork" is gone. It now uses getblocktemplate.
So if you want to mine on the new wallet you have to change your configs!
These instructions are for people that already know how to solo mine.
LINUX:Step 1. Generate an rpcauth code to put in your digibyte.conf file by going to this link
https://github.com/digibyte/digibyte/tree/6.14.0/share/rpcuser and download and put the file in your digibyte root folder.
Step 2. Run it by typing “python ./rpcuser.py [user]” ([user] can be what you choose to put in)It will show you something like this.
“String to be appended to digibyte.conf:
rpcauth=user:1335d15a52c8c24ef246b73bf4b9741$44d37ba0cb46191f11749c3217c7e497da5e01f8e8e01bd501bb35fbfcc0c9ba
Your password: l147_CovTnVvV4P0W5p8qa1B5Gs88EDqMo5OI9Fmo8Y= “
Step 3. Remove rpcuser/rpcpassword from your existing digibyte.conf file.
Step 4. Put the rpcauth=user:1335d15a52c8c24ef246b73bf4b9741$44d37ba0cb46191f11749c3217c7e497da5e01f8e8e01bd501bb35fbfcc0c9ba in your digibyte.conf file
Use the password for your mining rig for example.
-u user -p l147_CovTnVvV4P0W5p8qa1B5Gs88EDqMo5OI9Fmo8Y=
WINDOWS:Step 1. You cant generate an rpcauth code because you need to install python first. So the easiest way ist to use existing rpcauth.
Step 2. Remove rpcuser/rpcpassword from your existing digibyte.conf file.
Step 3. Put the rpcauth=user:1335d15a52c8c24ef246b73bf4b9741$44d37ba0cb46191f11749c3217c7e497da5e01f8e8e01bd501bb35fbfcc0c9ba in your digibyte.conf file
This is the digibyte.conf:
server=1
listen=1
rpcport=14022
rpcallowip=192.168.222.0/24
algo=qubit
rpcauth=user:1335d15a52c8c24ef246b73bf4b9741$44d37ba0cb46191f11749c3217c7e497da5e01f8e8e01bd501bb35fbfcc0c9ba
rpcallowip=192.168.222.0/24 => You can change this to your Network or only one IP in your LAN!
algo=qubit => change algo you want to mine
digibyte.conf file has to be in your digibyte folder. => C:\Users\accountname\AppData\Roaming\DigiByte
Step 4. Change your bat or config for your miner!
At this example i use algo=qubit so i want to mine qubit.
I use the cpuminer.
If you use other algo and other miners just read the help.txt which comes with your miningsoftware!
This is the mining.bat for cpuminer:
cpuminer -a qubit --url=192.168.222.202:14022 -u user -p l147_CovTnVvV4P0W5p8qa1B5Gs88EDqMo5OI9Fmo8Y= --no-stratum --no-getwork --no-extranonce --coinbase-addr=D8i1mDnjqpXGwyCrFJT9qbSYuYtdoW7bJc
Use the gernerated password and the user with the name user!
-u user -p l147_CovTnVvV4P0W5p8qa1B5Gs88EDqMo5OI9Fmo8Y=
INFO:
-n, --nfactor neoscrypt N-Factor
--coinbase-addr=ADDR payout address for solo mining
--coinbase-sig=TEXT data to insert in the coinbase when possible
--no-longpoll disable long polling support
--no-getwork disable getwork support
--no-gbt disable getblocktemplate support
--no-stratum disable X-Stratum support
--no-extranonce disable Stratum extranonce support
--no-redirect ignore requests to change the URL of the mining server
p.s. big thx to twebit!
I just wanted to say thank you reSI. I found your post very informative. I was even able to get the rpcuser.py to run on Windows to get my own rpcauth and password.
I am hoping you or the community can provide some direction. I am unable to get my Antminer S7 to see the "wallet", for a lack of a better term. I have have spent a number of days Googling, but can only find references to the old getwork system and very little on the new blocktemplate system using IP based miners.
Antminer:
http://192.168.1.26:14022 (IP of Computer with wallet) Worker: Plainname Status: Dead. (RPC generated password in the miner config field).
My digibyte.conf file: (located at: "C:\Users\Mary\AppData\Roaming\DigiByte")
server=1
listen=1
rpcport=14022
rpcallowip=192.168.1.0/24 ***(Antminer IP is 192.168.1.103)
rpcconnect=127.0.0.1
algo=sha256d
rpcauth=MYUSERNAME:SALTSTRING$HASHSTRING
addnode=IP (6 entries)
The wallet (v6.14.2.0-4fbe88b-DGB) has 12 connections (In: 4 / Out:
.
I am hoping, once I can get the Antminer to see the wallet, than I can then move forward with getting bfgminer working. But after reading a post by the Irishman, I am not very hopeful at this point.
I sincerely appreciate yours and this communities time.
Thank you.
