Not really a bug, there are protections like the ones I mentioned, and it's inherent/necessary to Bitcoin since the timestamp is used for hash variation as well
protection, as in "pretend" condoms.
This is a huge honking red flag to anyone who has ever worked with the time continuum.
In geophysical surveys we would label this a "BLUNDER".
Did you read the explanation I wrote? It's not based on the atomic clock, it's based on the local time at the node and the offset from the network time/connected nodes
Everyone has worked with the time continuum lol. Do you mine or operate a node? I highly recommend it, you'll learn a lot about Bitcoin in the process, and hardware is cheap right now
BCHD node yes, mining, no.
Mining nodes with clocks that far out of sync lack fundamental credibility.
Their blocks should be rejected unless sync is "credible".
= Byzantine Blunder
I'm not sure what you're babbling about, this poses no risk to the network, and the timestamp has nothing to do with when the transaction is received or confirmed. You're loony mate
