# Chain of Timestamped Hashes

<figure><img src="/files/VEcDbgYe0ApiYjMgai1N" alt=""><figcaption></figcaption></figure>

*Each timestamp includes the previous timestamp in its hash, forming a chain, with each additional timestamp reinforcing the ones before it.*

\- Satoshi Nakamoto, Bitcoin Whitepaper

The **chain of timestamped hashes** is a critical feature of the Bitcoin blockchain, where each timestamp includes the hash of the previous timestamp, forming **a continuous and secure chain**. As stated by Satoshi Nakamoto, this structure is essential for maintaining the integrity of the blockchain. Each **block's header must contain the hash of the block upon which it is built**, creating a single chain of valid blocks that traces back to the very first block ever created, known as the **Genesis block**.

In this system, a single block can have multiple child blocks, but only one of those children can become part of the permanent **longest chain** of proof-of-work. This design **incentivizes nodes to collaborate and compete** to ensure their valid blocks are included in the chain. As new blocks are added, the cumulative proof of work increases, enhancing the security of older transactions. This means that as time progresses, **transactions become more secure due to the increasing amount of computational work** that has been applied to the blocks that follow.

The chain of proof-of-work forms a distinct **Directed Acyclic Graph (DAG)** separate from the transaction ledger, commonly referred to as the **Timechain** or **Blockchain**. This chain serves as an immutable record of all transactions and the order in which they occurred. Any transaction that contradicts a previously recorded event, such as a double spend, is deemed invalid and cannot be included in the longest chain of proof of work.

It is important to note that **while valid transactions may be created, they can still be excluded from the longest chain if they are not correctly broadcast or if they do not pay sufficient transaction fees**. Such transactions may persist in local versions of the transaction DAG but will never become a permanent part of the ledger. If these transactions are lost from local memory, they are effectively erased, underscoring the importance of proper transaction management within the Bitcoin network.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-whitepaper-series/section-3-timestamp-server-bitcoin-whitepaper/chain-of-timestamped-hashes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.