I think GIL may have run into the negative retarget block issue too. This is where a block is generated with a timestamp lower than the previous one (ie going back in time), which causes the difficulty retargeting algorithm to fail.
If this is the case (I haven't checked the code) mining will not be possible, and nodes may be banning peers if they receive a block they don't think is right. For example:
ProcessBlock: ACCEPTED
received block c917ebe57e73f3b2db34
nActualTimespan = 106327 before bounds
GetNextWorkRequired RETGILET
nTargetTimespan = 160 nActualTimespan = 640
Before: 1e0ffff0 00000ffff0000000000000000000000000000000000000000000000000000000
After: 1e0fffff 00000fffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 192.241.136.248:64574
The retarget issue can only be fixed with a client update (hard fork)
I can't easily see what has happened to recent blocks because both my nodes refuse to sync past the very first 3 blocks...
BTW, anyone note that "RETARGET" was changed to "RETGILET" in the above debug output? Indiscriminate search & replace ARG->GIL in the source.
