v1.2.8 error: Does that mean a 28s block was rejected ?
2017-02-22 00:16:00 SEVERE: Block not accepted
nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 79996588 current time is 79996560, previous block timestamp is 79996072
at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:849)
at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:45)
at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
@Merlin44
If the block timestamp is 79996588 and the current time is 79996560 ... it seams to be a block out of the future.
But seriously, there were issues with nodes running their system-time out of sync ... after it was announced, the problem seams fixed.
https://forums.burst-team.us/topic/4114/keep-your-system-time-in-sync-pleaseI also added a note about sync time to the github release page.
Basically if you find a block but you have your system time not in sync, it may not get accepted... like in this case.
The timestamp has nothing to do with the deadline.