This question already has an answer here:

Will other nodes refuse the mined block if the timestamp is too far apart from local or UTC timestamp or will they blindely accept the block if the PoW is correct?

marked as duplicate by flygoing, Achala Dissanayake, Richard Horrocks, shane, Ismael Dec 19 '18 at 20:00

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.


It depends on the client, but currently Geth and Parity reject blocks that are more than 15 minutes later than local clock time. That is, if my node sees that it's 12:00pm, and you mine a block with a timestamp of 12:20pm, then my node will not process that block.

The white paper https://github.com/ethereum/wiki/wiki/White-Paper clearly indicates for block validation: """...Check that the timestamp of the block is greater than that of the referenced previous block and less than 15 minutes into the future """

  • Your comment guided me to github.com/ethereum/EIPs/blob/master/EIPS/eip-1482.md I'm not sure what's the current status. It's just an informal protection in geth and parity implementation. It's defined by some other formal spec? I've seen some ¿audited code? in OpenZeppelin using the timestamp (github.com/OpenZeppelin/openzeppelin-solidity/blob/master/…). With no spec-protection for block timestamp shifts, I think the only safe measure is to use external oracles to input the "physical time" outside the Ethereum network. – earizon Dec 18 '18 at 14:58
  • You're correct that it's not defined in the yellow paper. I think that EIP is greatly needed just to make sure the official specification follows implementation, but all major clients implement this same or a stricter future timestamp check. – flygoing Dec 18 '18 at 15:57

Not the answer you're looking for? Browse other questions tagged or ask your own question.