Quote from: MikeRG2880 on April 24, 2018, 01:10:57 PM

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.

Good question, don't know why some nodes seem to run 'one hour in the future' and nodes on the correct time accepted 'future' blocks. Guess to fix this without some kind of update, all nodes have to sync their time and disable PoS/PoW mining for one hour...

Quote from: Xantor1234 on April 24, 2018, 03:49:24 PM

IMHO it _should_ fork as the blocks from that point are obviously wrong and only 'cheaters' profit.

Indeed, it should have forked, but did not. Undecided