We wanted to give another update to let you know that we are testing and comparing the Kimoto Gravity Well implementation against our own custom re-target code. We wanted to make sure we release the best possible solution for the current multi-pool problem. As no one has been able to give us a technical description of KMG, nor can we find much reading material on it we are testing exactly how it performs under load with DigiByte code.
We have recompiled and tested about thirty different code configurations over the past few days. We are timing re-targets and averaging them out over several hours. We are also simulating up to a 40 fold instant hash increase or decrease. We want to find the best possible solution that will serve DigiByte many years into the future.
We apologize for the delays, but we would rather do things right the first time then have to re-fork and re-update a few weeks or months later.
Slow and right is definitely better than fast and fail We have recompiled and tested about thirty different code configurations over the past few days. We are timing re-targets and averaging them out over several hours. We are also simulating up to a 40 fold instant hash increase or decrease. We want to find the best possible solution that will serve DigiByte many years into the future.
We apologize for the delays, but we would rather do things right the first time then have to re-fork and re-update a few weeks or months later.
Much agreed.
