Re: ★★ DigiByte ★★ [DGB] DigiShield v2.0 Now Live ✈ Mandatory Update ✔

Quote

// Maximum 400% adjustment...
bnResult *= 200;

Is there something we are over looking here? With a much higher (actual) hash load will this adjustment act differently? What are the dangers of allowing very large diff swings like this?

Also, with a higher difficulty # like the 10-20 range we currently see, will we see any other phenomena that we can't test in the low hash test-net environment? Are we on the right path? What are your thoughts?

I think this might give miners a lot (as in, A LOT) of rejects as soon as the difficulty adjusts, unless your tests say otherwise.

Good point to consider! Thanks for the feedback! We will look at that more in depth.

Told you so.. Tongue

Quote from: canman on March 01, 2014, 06:18:39 PM

hey digibyte. been mining at coinium and since the new diff took place the diff has been all over the place. never consistant. it will go from 8 to 9 then jump to 12 to 15 then back now to 7. cna you explain as to why it does this. and im getting much more rejects with this new diff change. plz explain.

Probably he is talking about shares reject.. How is that connected to the coin?

We have not noticed an increase in rejects. We have, however, noticed an increase the amount of coins we mine as the diff/reward is more consistent that before when we would be "stuck" for a few hours following a large hash down swing.

Yes there are some big jumps and dips in the difficulty. Its suppose to do that with big up or down turns in net hash. It is far more responsive to net hash changes then the Kimoto Gravity well. Which be by the way, we found could still get "stuck" for awhile with a large hash down turn. It also can get isntamined for awhile with a large hash increase.

We now have the most responsive difficulty retarget system of any coin out there. It litterally only takes 2-4 blocks to adjust to a doubling of the net hash or a massive downswing.