And so you know EXACTLY what the net hash rate is going to be and how long it will take to solve the next block, thus predicting the new difficulty BEFORE the coin can. I'd like to know how.... And if you could... You should make a pool that has 100% profitability for CGA...
Ah I see, so you're relying on KGW to change the diff every block and therefore make the diff input to fmod(block, diff) unpredictable.
Interesting point there tho... I will have to dig into KGW a bit more - is it based on ntime or broadcast time? If I recall correctly, it's purely based on nTime differences (but I could be totally wrong).
If nTime based, then you could calculate the nTime required on the next block to produce an anomaly, and use that nTime, no?
Edit:
Yup... it definitely looks that way - so... here's what I'm thinking:
Kimoto's gravity well uses:
PastRateActualSeconds = BlockLastSolved->GetBlockTime() - BlockReading->GetBlockTime();
As it's key adjustment variable... now, given that GetBlockTime is:
int64 GetBlockTime() const
{
return (int64)nTime;
}
That means unless I am missing something, it should be possible to make EVERY block you mine an anomaly by carefully selecting the nTime you use on your block. Mind you, this is a rather quick thought and I definitely could be missing something.
