This could be a problem ...
I pulled all my hash from the network around block 142,410 ... it then ran ok for the next 12+ hours until block 142,473 where the difficulty has now suddenly jumped to 1,000+ the highest digibyte has ever seen... could be stuck on this block for a long time.
I could probably clear it, but am getting a bit bored throwing away my own money to push the blockchain along ... especially as the Devs have not come forward and explained the cause of the problem. Happy to support them if they come up with a solution and need hashing power, but until then I have retreated to the side lines.
Also, does anyone know of a way to monitor the DGB network hashrate? All the usual sources no longer work since the introduction of the new wallet.
First off, thank you very much for putting your hash toward the network and trying to help us ll get over the hump. We dont expect anyone to mine for days on end with no return. As for the problem we have mentioned it several time over the past couple months.
The problem is not with DigiShield alone as it worked fine until we combined it with the 0.9.1 protocol in April (you can see this on several charts.) DigiShield with the 0.6 Bitcoin protocol works great for several coins still and it still works for Dogecoin. We screwed up and did not do enough testing when we released the 0.9.1 wallet. We figured since no hard fork was required everything with the difficulty adjustment would stay the same.
What basically happens with the 2.9.1 protocol is when a sudden hash spike occurs blocks are sometimes discovered only milliseconds apart. Combine this with a single block average (DigiShield only goes back to the previous block) and you get an astronomically high inflated difficulty.
The next problem is when the hash rate drops and the difficulty eventually drops it drops too low and an oscillating effect occurs & the process repeats itself.
The best way to overcome this is with a steady increase in hash, not a sudden spike. Also, a consistent hash base will be a huge improvement. Starting tomorrow we will begin adding hash to the network and we will publicly post the days target hash-rate. This will help speed things up considerably. We ask if you have some hash to contribute we could definitely use it.
We dont expect people to do this for weeks on end but if we could get a rotation going that would be great.
@Digibyte
Thanks for the response, much appreciated.
I admit I don't have all the answers but if it is the new protocol that is causing the problem then it is a concern that it will rear its head after the wallet passes block 145,000. The explanation you gave is plausible, but NOT the whole story and it doesn't explain what I have been observing, examples:
A. Block 142,272 - 142,273 took over 5 hours to find the block at a difficulty of 1022 ... by your reckoning Digishield would then reduce the difficulty far to much ... but it actually increased to 1300+
B. Whilst pointing several GHs of hash at the network I was finding several groups of consecutive blocks, looking at these I often found two or more blocks in quick succession (seconds apart) but rather than increasing the difficulty as you suggest it actually reduced it for the next blocks.
C. It is true the difficulty is oscillating, but it is also oscillating at far too high a range. It never reduces the difficulty to a point where you would find a block on average every minute (ie the correct difficulty) ... any idea why it fails to retarget to the correct level? Even when there has been very little hash pointing at the network it still oscillates roughly in the range 200-400.
D. By increasing the network hash rate x6 I thought the difficulty may have gone up ... but it actually stayed the same and still oscillated in that same range.
Do you have any idea why the hashrate has jumped to record levels over the last two blocks? I just want to make sure we don't replicate that and get it permanently stuck at an even higher difficulty.
Interesting there are no problems with other coins using Digishield, Doge you might expect as it maintains a consistent very high hashrate ... but I would have thought some other coins may have had similar problems by now. Could it be unique to Digibyte and a stray line of code that is not included in other coins?
Anyway, hopefully this will all be resolved and we can cruise to block 145k in no time.
Happy to help with the hash power if you set a daily target. Is there somewhere we can check the Digibyte Network hashrate? Most of the original sources seem to have 'broken' since the wallet update.
