you're going to wish you had something in place to handle the ten or fifty-fold increase in hashrate.
That is why the team works on the simulator to get the best algo to handle pooljumps and big waves.
https://github.com/GeertJohan/diffsimIt is being worked on. Question is wether there should come a temporary solution by implementing Digi as suggested by Fuse first and later on the custum made algo. This should have been done a few days ago, but there were found some mistakes, that could have made it more worse.
There was some kind of consensus about implementing Digi first without the tests on the sim. The team agreed on that, but was canceled because of some errors. That is the situation we are now atm.
I'm fully aware of what occurred, and the issues could've been resolved instantly before initiating change. I find it underwhelming that the team couldn't simply agree to deploy the temporary solution, having been tweaked. What happened is what's been happening, the ongoing delay.
Simulators are wonderful, I've dealt with them in the past, I'm very familiar with difficulty projection. They are long-term goals however. You need a short-term solution right now, and the fact I even have to emphasize this is unfortunate, because it shows lacking foresight on part of whoever is claiming to lead this. This should never have been an issue from the start.
I believe this is why there's mounting frustration, because the need to take action has long passed, and yet, there is no action. I don't mine this coin and have never bought into it, but have been keeping an analysis on it. I believe it has great capability, but things are taking a swift turn for the worse lately.
I'm merely trying to say, from a non-invested analytical point of view, you are in a very dangerous spot right now, and ignoring the need for immediate action by focusing on a long term goal, is quite possibly the worst thing that could be done.
