Topic: Solo Mining Digibytes - NVIDIA ccminer - July 2017 (Read 6178 times)

Hi

What changes need to be done in order to mine with ASIC devices like antminer S9?

Thanks

I think that we hit digi when it first came out and did well. I like it when the diff either drops back down or sticks to a lower area where the newer guys can get in a start mining something and see a result. A lot of people leave because they either have no desire to buy into coins or no money, and they have nothing that they can do to produce any. Coins like digi make it possible for them to get a foot in the door.

How to setup Solo mining with ASIC devices (such as A2000 on QUBIT?

can this be setup for a L3 miner... i really lost my self trying to do that, thx

With the increasing difficulty I believe that only above 2 or 3 Gh/s it's worth to solo mine... if the diff come back to the past month levels it should become again interesting to solo mine.

How is your guys luck so far solo mining? Mine seem to be atrocious. I've got 1.25GH/s on Groestl (about 20 Pascal GPU's) and on my pool am used to finding 2-4 blocks a day at least, yet I've been solo mining for 3 whole days now and only found 2.

I ran some difficulty calculations and the formula given by The_Miner and should be getting about 1 block every 8 hours or 3 a day, which is on par with what I found in my pool.

Am I just very unlucky or is anyone else having similar results?

I used Skein for a day with the Alexis78 fork and Groestl for the other two days, each algorithm found one block respectively when it should have been around 12 for the total duration. I know there is high variance in payouts and a good amount of luck involved when solo mining, but I can't help but think that that's a lot.

As of last night I switched back to my pool and have been running 10 hours and already found 2 blocks for the pool, the same it took me 3 days to mine solo. The only difference is that when solo mining I am using the Nanashi miner linked in this thread vs the Alexis78 fork of CCMiner on my pool. The Alexis fork has a better hashrate on Skein (not sure about Groestl), but not THAT big of a difference.

Ignore the error:

JSON key data not found
JSON invalid data (len 0 <> 128) error

It depends on the miner and it should be caused from the fact that between one block and the other there is no actually data to mine. The error is always coming between the blocks. If hash rate is coming you are mining.

To estimate how long will take to get a block mined you can use the following calculation (it's not sure, it's probability):

time in hours = difficulty * 2^32 / your hash rate / 3600

For instance, if you have 1GH/s rig, assuming the Digibyte difficulty stays at 10,000 for long enough to find a block, you will mine a block in average every 12 hours.

10,000 * 2^32 / 1,000,000,000 / 3600

Consider that the difficulty of Digibyte lately is jumping quite a lot... if you don't have a decent hash rate don't solo mine. 1GH/s it's already borderline, below 1.5 or 2GH/s I would not solo mine.

so how can i tell if I'm actually mining, i get tons of the JSON key data not found JSON invalid data (len 0 <> 128),

followed by my miner and hashrate and current block is xxxxxx followed by more of the above

any suggested minimum hash power needed to try solo? I mean min hash power to be worth try it instead of a long wait disappointment of not getting any block at all after week.

No waste of share rate in connections to pool, no pool fee, less fees spent for transactions... depending on your hash power you can reach also a good 10% increase in rewards...

Whats the advantage of solo mining DGB?

 With the Alex78 fork, yes.

 They do well on DGB-Groetsl too though, but the truvot (sp) fork seems to work better there.

True, the only one I found is the ccminer-nanashi v1.7.6 r6 (https://github.com/nicehash/ccminer-nanashi/releases).
Regarding RPC removal, you are perfectly right, it should work fine keeping it for old wallets, I just wanted to have a guide from scratch for whoever does not even have a wallet installed... normally I've seen Digibytes mined on pools.



You can change the Algo in the config file and in the command string for ccminer.

Ain't Nvidia better on Skein?

Nice guide but too bad virtually no miner supports --no-getwork and --coinbase-addr.

Not even Tpruvot's fork, let alone private miners.


There's no reason to remove RPC - which still works with older wallet versions.

I've seen different guides on how to solo mining DigiBytes, but none of them was explaining how to do it with ccminer. The following guide is based on several forum threads and few researches and tries.

It is quite simple and assuming to start from scratch this is what you should do (the guide is based on what I’ve done on Windows 10 x64, but it should work also with a different OS).

1.   Download the official Wallet V6.14.2 from https://digibyte.co/digibyte-wallets
2.   Install the Wallet
3.   Launch the Wallet (to allow the generation of all the required files such as wallet.dat etc.), but do not synchronize
4.   Close the Wallet
5.   Open your Wallet link and add the “--server” parameter (in my case the target is "C:\Program Files\DigiByte\digibyte-qt.exe" --server)
6.   Download the Digibyte blockchain (.zip file) from http://cryptochainer.com/dir/ (this is to speed up the synchronization of the wallet)
7.   Copy the .zip file to the Digibyte folder, located in /Users/%YOUR_USER%/AppData/Roaming/DigiByte
8.   Create backup of wallet.dat file (this is your actual wallet)
9.   Delete all files & folders, except for wallet.dat and the .zip file
10.   Unzip the .zip file directly into the folder
11.   Delete the .zip file

If the original wallet.dat was moved, copy wallet.dat back to the DigiByte folder. Always make backups of your wallet.dat files.

12.   From Windows Explorer create a new text file in the Digibyte folder (/Users/%YOUR_USER%/AppData/Roaming/DigiByte) and rename it as DigiByte.conf
13.   In the DigiByte.conf file add the following parameters:

From the above parameters, you may change the “algo” if you want to run something different from myr-groestl and you can also change the “rpcallowip” if you are running the wallet on a machine different from your rig. You can also change “rpcauth”, but you will need to run the python script (https://github.com/digibyte/digibyte/tree/6.14.0/share/rpcuser) to calculate the auth code, so you can simply leave the values like they are here.

14.   Save the file
15.   Launch the Wallet (through the link with the “--server” parameter)

Let the wallet synchronize (it should not take long since you have already downloaded a good portion of the blockchain). Once the wallet is synchronized you have a ready-to-solo-mine wallet.

At this point you need a version of ccminer that supports the “--no-getwork” and “--coinbase-addr=” parameters. I found that the “ccminer-nanashi v1.7.6 r6” fork is working well, but if you find any other version supporting the same parameters than you are still ok.

16.   Download “ccminer-nanashi v1.7.6 r6” from https://github.com/nicehash/ccminer-nanashi/releases
17.   Create a new ccminer-solo.bat file and copy the below launch string

Of course, change the coinbase-addr with the address you can find from your wallet (File > Receiving Addresses…) and you can also change the IP in case you are running the wallet on a different machine. Also, you can change the intensity. I’m using “-i 20” with the 1080ti, but you can set the same intensity you use while mining on pools. Username and Password are already set to match the key you configured in the DigiByte.conf file, if you generated the key on a different username using the python script, then you need to change also username and password here.

18.   Only when the wallet is completely synchronized launch the ccminer-solo.bat file
19.   Done! You are solo mining DigiBytes!

If you overclocked or changed the settings of the GPUs, remember that the stability can change, so monitor the miner and the GPUs. In my case I had to reduce of 20 points the OC from +180 to +160 to avoid crashes, but that depends on many different variables, so check again the stability of your GPUs.
If it happens, don’t bother about the “JSON key ‘data’ not found” error message that pops out constantly, it is only because during the block switch there is no actual data to work on.

To slightly increase the hash rate you can try also the following steps:

20.   Create a new pump-the-beast.bat file with the following text

21.   Launch the pump-the-beast.bat file (it does nothing but increasing the I/O load of your machine, not sure why, but on my Windows 10 x64 machine increases the hash rate of some points)

If you feel like rewarding me with your first solo block do not hesitate to donate DigiBytes to my address “D8Bf9PpGvMhXw72XqvqAnyQaPqPvLwgDSH”. It would be really appreciated.