There's a lot of discussion regarding DIGI. I just want to make some observations/statements:
DIGI is working. If gazo is a profitability script based MP, and they are pulling less than 10% of the blocks(8.76% currently), than it could be argued that CM would be in the same boat. And it could further be argued that gazo and CM would be fighting for that 8.76%. We wanted a response to MPs, and we have it.
It seems like that for sure! Although I'm really curious what happens when CM joins again.
Profit for dedicated miners is up. There is no arguing that. When 40% of the blocks are going back to the miners, and not CM's wallet, that's a win in my book.
Very happy to read this!
Block times are off, that is true. When I woke up this morning we were at a 00:03:44 block time for 24 hours, which was a true 24 hours since the change. There have been some longer blocks, but mostly because we've hit some pretty high difficulties. The difficulty isn't overreacting, it's reacting. When blocks are found in less than 30 seconds from difficulty 1000 up to 2000, it's going to go up. The good thing is that it drops back down like it's supposed to though. We come back to a more reasonable follow-up block, rather than dropping too low. Now, if that block isn't solved in time, you're going to go lower. It's just the nature of a single block retarget.
We had some lucky blocks and miners joining the 1.3.1 network after they found CM had left. I think these large hashrate joins caused some diff spikes, but can't be sure.
A second point on time is that DIGI is best suited for block times closer to, but not less than, 1 minute. I'm not saying that we're running a broken version of DIGI, but rather I think that Kilo's original suggestion of halving the block time is something worth looking at in the future. Note... not the immediate future, but at some point down the long road ahead.
Totally agree here. We should only do this if somehow the slower blockrate becomes a real problem. (too many transactions or confirm times, etc.)
Until then, let's wait and see how a higher hashrate will stabilize the blockrate back to 1 per 2.5 minutes.
I just want to know if people are happy with the change, or if we're experiencing buyer's remorse. I'd love to hear an official response from the devs as well.
-Fuse
GJ is still observing Fuse, but from my non-dev perspective it looks good. I think GJ will give it a few days before making a statement.
It will take more time to get to a good conclusion, but I already did some quick analysis.
I have a "time series database" connected to the Guldencoin Explorer backend and I'm gathering block time and count metrics with it.
The graphs I rendered let us see some interesting stuff, I made a screenshot and edited it with comments and marks.
Full resolution:
https://i.imgur.com/zBkFefi.png
