Sharkie, it's been more than a week since the issue started. Your confidence is misplaced. The "facts" better come in 20 leather-bound volumes, otherwise I can't see what they were doing all this time.
Speaking of facts, these blocks are funny:
https://chainz.cryptoid.info/ion/block.dws?189483.htmTimestamp: 1497625600
Previous block timestamp: 1497629456 (more than an hour LATER although the actual time between blocks was just a few seconds)
Next block timestamp: 1497629456 (same as two blocks ago)
Edit for readability - block timestamps go like this: 9456 --> 5600 (block number 189483) --> 9456, where 9456 is the ~ correct time. I can't think of any good reason why that middle block would have a timestamp of an hour ago. And of course it's "mined" by that super-lucky masternode, so there's that.
I'm guessing this nonsense has something to do with fucking up the difficulty adjustments. Typically there are time drift restrictions in the code, AFAIK BTC checks the average timestamps of previous blocks as well as time reported by connected nodes but it only adjusts difficulty every 2016 blocks so any timestamp manipulation would be quite pointless. ION adjusts every block.