<p>The system called timestamp server in the original whitepaper is currently more often referred to as a "miner".</p>

<p>They timestamp blocks, which combine several transactions, imposing an authorative order on these transactions. This is necessary as the system cannot otherwise decide which of two conflicting but otherwise valid transactions should be accepted.</p>

<p>It's certainly not a general-purpose timestamping system, but that can be built on top of it. See for example <a href="http://github.com/goblin/chronobit" rel="nofollow">ChronoBit</a> or <a href="http://github.com/opentimestamps" rel="nofollow">OpenTimestamps</a>.</p>

CC BY-SA 3.0
2013-06-13T08:14:01.230Z
2013-06-13T08:22:36.817Z
2013-06-13T08:22:36.817Z
Pieter Wuille
<p>In the <a href="http://bitcoin.org/bitcoin.pdf" rel="nofollow">original whitepaper</a> Satoshi proposes a creation of a timestamp server to authenticate that Bitcoin blocks were not created later than at a given time. Has this feature been ever implemented or planned to be implemented? Why would the timestamp server be useful to the Bitcoin client/protocol/community?</p>

<timestamp><whitepaper>
Has the Timestamp Server from the original whitepaper ever been developed?
ThePiachu
# Has the Timestamp Server from the original whitepaper ever been developed?

(Asked by: username_0 on 2013-06-13)

In the [original whitepaper](http://bitcoin.org/bitcoin.pdf) Satoshi proposes a creation of a timestamp server to authenticate that Bitcoin blocks were not created later than at a given time. Has this feature been ever implemented or planned to be implemented? Why would the timestamp server be useful to the Bitcoin client/protocol/community?

**Tags:** timestamp, whitepaper


---

## 1 answers

### Answer by username_1 on 2013-06-13. Score: 4

The system called timestamp server in the original whitepaper is currently more often referred to as a "miner".

They timestamp blocks, which combine several transactions, imposing an authorative order on these transactions. This is necessary as the system cannot otherwise decide which of two conflicting but otherwise valid transactions should be accepted.

It's certainly not a general-purpose timestamping system, but that can be built on top of it. See for example [ChronoBit](http://github.com/goblin/chronobit) or [OpenTimestamps](http://github.com/opentimestamps).


---

