Quote from: Dunkelheit667 on April 23, 2018, 05:11:20 PM

Quote from: dnp on April 23, 2018, 05:06:22 PM

i'm noticing new blocks arriving consistently 1 hour into the future the last couple days.

Just found this in my debug.log. Yes, seems to be an issue with timestamps:

Code:

CheckStake() : new proof-of-stake block found
hash: 782039806d45cb037e7b07e74ec1637058a8b5959b2d5d2fe348847a5a21b840
proofhash: 0000014da281be708a96c9d89efb2c1707cb6bd7838eb97b8312cac76282e3fd
target: 00000fa8ee0e0000000000000000000000000000000000000000000000000000
CBlock(hash=782039806d45cb037e7b07e74ec1637058a8b5959b2d5d2fe348847a5a21b840, ver=6, hashPrevBlock=74a4e46d294ce8880ab4f52e36a8239f55f5a28b9f3ad1b8439aa5f3de298bfd, hashMerkleRoot=ddc9251240bd996c2fca910c2992d73ad3fafe54012923bfd44a87079e616799, nTime=1524503117, nBits=1d00b1c6, nNonce=0, vtx=2, ...)
...
ERROR: AcceptBlock() : block's timestamp is too early
ERROR: ProcessBlock() : AcceptBlock FAILED
ERROR: CheckStake() : ProcessBlock, block not accepted

Edit:
Yeah, guess there is something wrong with nTime/ntp.cpp? The following workaround 'fixed' my 'issue', but it's really... shady.

1) Close the UnitedSciFi client. Sync your system time.
2) Disable time syncing and set your local system time to current time + one hour.
3) Enable the NTP server on your local machine: https://www.interfacett.com/blogs/creating-standalone-ntp-server-windows/
4) Start the UnitedSciFi client.

PoS worked again.

Curiosity question: to my untrained eye, won't the client fix also require forking/checkpoint from where the problem happened (181997?) since currently the UTC timestamps of all the blocks since then are wrong? Trying to conceptualize how miners with the correct time could get back on the current longest chain without kludging the client to mess with how timestamps are agreed to.