Quote from: barwizi on June 03, 2013, 05:47:45 PM

anyone got an idea how long it will take to clear these three blocks? and is that hash rate i see correct?

No, the hashrate reported by clients is an estimate. Im not sure what its based on. Look at the actual block timestamps going back and make your own estimate, along with how the weather, the FED's announcement of QE4 and the price of tea in china will affect recent block hashing rates

grep "new best" debug.log is handy in that respect, and you can even do grep 'new best' debug.log | tr -s " " "," >> blocktimes.csv and import it into a spreadsheet and play with the numbers. Then make some deep pronouncement about hashrates and difficulty.

When you've figured that out, go make a mint on TRC cuz I cant figure out why the diff STILL goes up and down. Its a weird social phenomenon.

I see about .8 to 1.2 hrs per block, but luck works too, we had a 4 minute block this morn and a 4 hour. So who knows. And hashrates are coming on and offline constantly. Make a guess.

If you read the code, the max retarg downwards is /16, and it will likely be that becasue of the slow blocktimes back 135 blocks, so we're looking at 4.32556 /16 = .27 diff. that will be 16x faster blocks than .8 to 1.2 hrs average, so something like 3 to 4.5 minutes, but no one knows.

Quote from: gica_contra on June 03, 2013, 05:43:29 PM

you should have done this from the start. waiting for dificulty 24 before the first reward doubling was stupid Undecided

understatement. yes, thats the whole reason for this. if it HAD made it to 24 it woulda been ok, but its like a rocket failing to achieve orbit. so close yet so far.

sent 1.0 to EPgVazGU13FrKUedcTVARR52vfnoF9aFgN
sent 1.0 to EemVzD8FRBvjpxEDTLGzqvVZG2HTRttUYa