Diff went down to 1
that ridiculous
and if someone says the fork works cause on average we have a normal block time, then i want you to try to send coin when diff is high and stuck.
The current oscillations are entirely due to the days we spent at a 108+ diff and 10+ hour block time. The fork basically walked the coin off a difficulty cliff, and it needs some time to settle down.
Is the current version ideal? No. Does it work much much better than either of the last two? Absolutely it does. There are occasional waits of a few hours for 6 confirms, but it's still usable.
I would like an update with a couple more tweaks, but this is close to a coin that can survive and thrive despite high hashpower attacks.
Finally some logical, level-headed input.
Alright, so my intial reaction to the results is two-fold:
1. THis still needs to level out some, but the extreme diff drops are empowering the pools to hit us and cause a slingshot effect. THis current method is indeed much more functional than it was before.
2. I think 36 Block SMA might be too long, and I raised those concerns with my team before the fork. The coin is reacting to what happened 6 hours previous, to be blunt, that's dumb, we need to react to what's happening now, but with a smoother to prevent unnecessary spikes or drops from lucky or unlucky blocks. I also agree with what you said previously that 12% might be too much, as that allows 600% per 6 hours, where as before it was only 400%. I think overall this algo can be functional with some more tweaking. Perhaps 12 or 18 blocks would provide enough smoothing without slowing down the reaction time so much. Right now it takes 18 blocks for the averaging to really start kicking in, that's a lot IMO, especially for a 10 minute coin. I think reasonably that we could almost half the 12% to 6% and still get the desired effect, without causing crippling hyper-inflation.
I have suggested the gravity well idea to the team, but hozer suggested there was a flaw with the algorithm, I'll let him elaborate on that.