Any word on Kimoto or something similar being implemented before we retarget. I have a feeling once difficulty drops the whale/whales will return.
I'm thinking about implementing some changes to set a much lower retarget window, maybe 100 blocks. In opinions on this? I could implement kimoto but it seems like more of a project.
I'm thinking that 100 blocks is about 4 hours, so it would be not very fruitful for someone to jump on like the whale did and jump the difficulty.
We are still on the same block hours after he left, how long would it take for us to get through 100 at this point?
Since the last difficulty adjustment we've went through 120 blocks, so we would already be at a lower difficulty
how long till we could do the hardfork?
I can have the code ready in a couple hours if all of the pools are ready to update their daemons
as long as its today or tomorrow, i can do a quick recompile, tuesday, on andward i need 24 hours notice..
Any word on Kimoto or something similar being implemented before we retarget. I have a feeling once difficulty drops the whale/whales will return.
I'm thinking about implementing some changes to set a much lower retarget window, maybe 100 blocks. In opinions on this? I could implement kimoto but it seems like more of a project.
I'm thinking that 100 blocks is about 4 hours, so it would be not very fruitful for someone to jump on like the whale did and jump the difficulty.
Currently about 1 hr per block... We are looking at around a month to retarget.
Even at retarget every 10 blocks, it would be 10 hrs, but we probably wont see such big disparities like now.
I dont like hardfork if we can just update retarget frequency. That sounds like a much smaller change to solve this issue.
How hard would a dynamic retargeting formula be to implement? Eg, if projected retarget rate goes above 1 day, it adjusts things to retarget in the near future
James
something like how long did the last x blocks take > 24 retarget in 5 blocks ?
Maybe something that is a bit more accurate. For example, if the target block time is exceeded by some factor that indicates a disconnect between current network hashrate, then we can retrigger retargeting after one block.
Extreme case would be if we are waiting for 17 hours on a single block, then clearly there is no need to wait for 4 more blocks! Since the goal for DRK is around a minute, anything over 10 minutes would seem to be statistically valid indicator that a retarget might be needed. At over an hour, there would be no doubt.
There must be some coin that already does dynamic retargeting? Alternatively, just retarget every block, then no need for semi-reliable stochastic methods