Block timestamp - Revision history

Furunodo at 10:06, 13 July 2020

2020-07-13T10:06:11Z

← Older revision		Revision as of 10:06, 13 July 2020
Line 1:		Line 1:
	Each block contains a [http://en.wikipedia.org/wiki/Unix_time Unix time] timestamp. In addition to serving as a source of variation for the [[Block_hashing_algorithm\|block hash]], they also make it more difficult for an adversary to manipulate the block chain.		Each block contains a [http://en.wikipedia.org/wiki/Unix_time Unix time] timestamp. In addition to serving as a source of variation for the [[Block_hashing_algorithm\|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.		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.

Furunodo at 10:05, 13 July 2020

2020-07-13T10:05:14Z

← Older revision		Revision as of 10:05, 13 July 2020
Line 6:		Line 6:

	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.

			See also [[epoch]], [[genesis block]].

	[[Category:Technical]]		[[Category:Technical]]

Belcher: Typos

2019-05-13T16:44:22Z

Typos

← Older revision		Revision as of 16:44, 13 May 2019
Line 1:		Line 1:
	Each block contains a [http://en.wikipedia.org/wiki/Unix_time Unix time] timestamp. In addition to serving as a source of variation for the [[Block_hashing_algorithm\|block hash]], they also make it more difficult for an adversary to manipulate the block chain.		Each block contains a [http://en.wikipedia.org/wiki/Unix_time Unix time] timestamp. In addition to serving as a source of variation for the [[Block_hashing_algorithm\|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 ~~even~~ need to be ~~in order~~. Block times are accurate only to within an hour or two.		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.		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.

Theymos at 16:36, 1 June 2016

2016-06-01T16:36:29Z

← Older revision		Revision as of 16:36, 1 June 2016
Line 1:		Line 1:
	Each block contains a [http://en.wikipedia.org/wiki/Unix_time Unix time] timestamp. In addition to serving as a source of variation for the [[Block_hashing_algorithm\|block hash]], they also make it more difficult for an adversary to manipulate the block chain.		Each block contains a [http://en.wikipedia.org/wiki/Unix_time Unix time] timestamp. In addition to serving as a source of variation for the [[Block_hashing_algorithm\|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 even need to be in order.		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 even need to be in order. 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.		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.

Theymos at 16:35, 1 June 2016

2016-06-01T16:35:27Z

← Older revision		Revision as of 16:35, 1 June 2016
Line 1:		Line 1:
	Each block contains a [http://en.wikipedia.org/wiki/Unix_time Unix time] timestamp. In addition to serving as a source of variation for the [[Block_hashing_algorithm\|block hash]], they also make it more difficult for an adversary to manipulate the block chain.		Each block contains a [http://en.wikipedia.org/wiki/Unix_time Unix time] timestamp. In addition to serving as a source of variation for the [[Block_hashing_algorithm\|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.		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 even need to be in order.

	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.		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.

Theymos: phrasing

2014-09-22T04:15:30Z

phrasing

← Older revision		Revision as of 04:15, 22 September 2014
Line 1:		Line 1:
	Each block contains a [http://en.wikipedia.org/wiki/Unix_time Unix time] timestamp. In addition to serving as a source of variation for the [[Block_hashing_algorithm\|block hash]], ~~there are~~ also ~~validity checks, that~~ make it more difficult for an adversary to manipulate the block chain.		Each block contains a [http://en.wikipedia.org/wiki/Unix_time Unix time] timestamp. In addition to serving as a source of variation for the [[Block_hashing_algorithm\|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.		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.

Theymos at 19:31, 13 January 2011

2011-01-13T19:31:19Z

← Older revision		Revision as of 19:31, 13 January 2011
Line 3:		Line 3:
	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.		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.

	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. ~~A single peer~~ never ~~adjusts your time by~~ more than 70 minutes, however.		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 [[: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.

	[[Category:Technical]]		[[Category:Technical]]

Theymos at 19:28, 13 January 2011

2011-01-13T19:28:35Z

← Older revision		Revision as of 19:28, 13 January 2011
Line 3:		Line 3:
	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.		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.

	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.		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. A single peer never adjusts your time by more than 70 minutes, however.

			Bitcoin uses an unsigned integer for the timestamp, so the [[:Wikipedia:Year_2038_problem\|year 2038 problem]] is delayed for another 68 years.

	[[Category:Technical]]		[[Category:Technical]]

Nanotube: create block timestamp article.

2011-01-13T17:41:52Z

create block timestamp article.

New page

Each block contains a [http://en.wikipedia.org/wiki/Unix_time Unix time] timestamp. In addition to serving as a source of variation for the [[Block_hashing_algorithm|block hash]], there are also validity checks, that 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.

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.

[[Category:Technical]]