We discovered the optimum combination was to set a different limit for difficulty increases vs decreases. By doing this we are able to recover or adjust to a 8-10x increase or decrease in net hash within just a few blocks. By having the limits high for both increases and decreases we were able to adjust rapidly to hash swings, but an annoying "oscillation" of block timings emerged. Two fast, then two slow. To fix this we discovered by having lower limits on increases and higher limits on difficulty decreases the oscillation was mitigated and overall performance and re-targeting improved dramatically.
We are now running tests on the network for a few hours to get a running block average and we will also simulate a few more hash swings. We are 99% finished though! Thank you for your support and patience! The extra time we have spent testing over the last 5 days will most definitely pay off for everyone in the long run! With DigiShield we are offering a solution to the re-target problem never seen before in a coin!
[/quote
DigiByte to the moon !!!