Looks like ocminer discovered the exploit and he was getting attacked.
Sounds like it was one or more parties trying to game the system, not Suprnova.
The dev may know the answer, but I'm siding with Suprnova.
There seems to be an attack going on ... I was ddosed and while I was ddosed I noticed blocks with "high" timestamps which subsequently reject my blocks with the correct time:
02-02-2017 10:27:10.151 TID:E5496700 [Error] <TJSONRPCTcpIpClient> Sending Error JSON RPC id () : Error: Invalid timestamp (New timestamp:1486027668 last timestamp (58999):1486027790) payload:SUPRNOVAROXXXXXXXXXXXXHXpLc/------ timestamp:1486027668 nonce:1303498590
I'm investigating what is actually going on exactly...
Frontend will be fine in a few moments, the DDoS ended.
OK, there are several nodes sending valid blocks with higher timestamps:
02-02-2017 10:45:18.259 TID:F0977700 [Error] <TNetServerClient> Disconecting 89.249.254.45:50962 > Invalid remote timestamp. Difference:227 > 180
Thus making my blocks "invalid" through to too "old" time even though my clock is correct:
02-02-2017 10:44:59.041 TID:F0977700 [Error] <TPCOperationsComp> Invalid new block 59002: Invalid timestamp (New timestamp:1486028696 last timestamp (59001):1486028710)
02-02-2017 10:44:59.041 TID:F0977700 [Error] <TJSONRPCTcpIpClient> Sending Error JSON RPC id () : Error: Invalid timestamp (New timestamp:1486028696 last timestamp (59001):1486028710) payload:SUPRNOVAROXXXXXXXXXXXXRkmq4------- timestamp:1486028696 nonce:3038414114
What those guys exploit is an old bug which was fixed in bitcoin years ago. They send their blocks with a maximum "drift" ahead ..
Example:
It's now 11:30:00 and blockchain is at height 59000
Max Drift is 30 seconds
So they say they solved Block 59001 at 11:30:30 even though it's just 11:30:00 and now my pool finds the next block as 11:30:20 which is BEFORE 11:30:30 so the blockchain rejects the block and says "Nope, your clock is wrong (even though my clock is right!) and I reject your block because the block before was discovered later"...
We need the dev here to fix that..
