Difference between revisions of "Block timestamp"
| Line 7: | Line 7: | ||
Expected review by: 25 October 2019 | Expected review by: 25 October 2019 | ||
| − | + | Reviewed Brendan Lee 22 October. Minor edits | |
| Line 19: | Line 19: | ||
Bitcoin uses an unsigned integer for the timestamp, so the [[:Wikipedia:Year_2038_problem|year 2038 problem]] is delayed for another 68 years. | Bitcoin uses an unsigned integer for the timestamp, so the [[:Wikipedia:Year_2038_problem|year 2038 problem]] is delayed for another 68 years. | ||
| − | |||
| − | |||
Revision as of 05:25, 22 October 2019
DISCLAIMER
This article is a direct copy of the original https://en.bitcoin.it/wiki/Block_timestamp and has not been checked for correctness or edited.
11 October 2019
Expected review by: 25 October 2019
Reviewed Brendan Lee 22 October. Minor edits
Each block contains a Unix time timestamp. In addition to serving as a source of variation for the block hash, they also make it more difficult for an adversary to manipulate the block chain.
A timestamp is accepted as valid if it is greater than the median timestamp of previous 11 blocks, and less than the network-adjusted time + 2 hours. "Network-adjusted time" is the median of the timestamps returned by all nodes connected to you. As a result block timestamps are not exactly accurate, and they do not need to be. Block times are accurate only to within an hour or two.
Whenever a node connects to another node, it gets a UTC timestamp from it, and stores its offset from node-local UTC. The network-adjusted time is then the node-local UTC plus the median offset from all connected nodes. Network time is never adjusted more than 70 minutes from local system time, however.
Bitcoin uses an unsigned integer for the timestamp, so the year 2038 problem is delayed for another 68 years.