Correct me if I'm wrong, but I took a look at the change history for the code and based on what I know about the attack, we shouldn't be seeing the next block for another 1 hour and 55 minutes.
Since the window was changed from 2 hours to 5 minutes, I think that we need to wait for wallclock time to catch up to the last block (#1606949), which I guess is about 2 hours into the future.
Also, based on the 10 minute wait time between mined blocks, it would actually be 2 hours, 5 minutes.
-MK
(for a python coder, I've been reading way too much C lately)
Sound theory. Anyone verify this claim?
I just restarted my wallet (the new version). It caught up to 1606949, and is stuck there. I do see in my debug.log that some older wallets are publishing later blocks. I suspect that those are the blocks that will be orphaned when the timer runs out?
-MK
Evertime Im getting the following error the offset is getting lower. think we are in fact waiting for it to reach 0, its actually dropping really fast
23:35:38: ntime warning: value 1515214991 (5a50588f) offset -1653 secs from uid 131
Maybe the attacker was only mining 1 hour in the future. based on your log entry, we have about 25 minutes to go, until we start seeing new blocks on the official chain.
