What happened
On-chain watchers noticed over the weekend that a Bitcoin block mined at a higher height carried a Unix timestamp earlier than the block immediately before it. Screenshots circulated on X suggesting the chain had somehow 'run backward in time. ' Galaxy Digital's head of research, Alex Thorn, pushed back in a detailed thread, picked up by BeInCrypto on Saturday afternoon.
Thorn's point is narrow and technical. Timestamps in Bitcoin blocks are set by the miner who finds the block, not by any central clock or network consensus. Miners are free to write any value into the timestamp field, within two consensus bounds.
The field is advisory metadata, not the ordering mechanism.
Why it matters
The confusion matters because it keeps resurfacing. Every few months, a new cohort of Bitcoin users discovers the timestamp rule and assumes something is broken. It isn't.
The hash chain, where each block commits to the previous block's hash, is what enforces canonical order. Timestamps are a loose, miner-reported field that Bitcoin's consensus rules check only lightly. Specifically, a block's timestamp has to be greater than the median of the previous 11 blocks' timestamps, and it cannot be more than two hours ahead of the node's own clock.
Everything else is legal. A miner who sets a timestamp one second ahead of that median floor can produce a block that chronologically 'precedes' the one before it by wall-clock seconds. That is a feature of how Satoshi built the protocol, not a defect.