> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-whitepaper-series/section-3-timestamp-server-bitcoin-whitepaper/timestamped-hashes.md).
# Timestamped Hashes
The concept of **timestamped hashes** is foundational to the integrity and security of the Bitcoin blockchain. As articulated by Satoshi Nakamoto in the Bitcoin Whitepaper, a **Bitcoin block comprises an ordered set of transactions** that each validly spend existing **unspent transaction outputs (UTXOs) into new transaction outputs**. The network treats each transaction as a distinct item or event, and the blocks are constructed using the hashed transaction messages as inputs into the block's own hash function.
When a node discovers a valid block, it broadcasts the transactions as part of that block. The hash of the transaction message serves as **proof that the transaction existed at the time the block was found**. This broadcast mechanism ensures that all nodes in the network are aware of the new block, which **can either be accepted or rejected based on consensus rules**. This process is essential for maintaining the integrity of the blockchain, as it **prevents double-spending** and ensures that all transactions are accounted for.
The timestamping process not only provides a historical record of transactions but also establishes a **chain of trust** among participants in the network. Each block's header must include the hash of the previous block, creating a continuous chain of timestamped hashes. This linkage reinforces the validity of each block and the transactions it contains, as **any attempt to alter a block would require recalculating the hashes of all subsequent blocks, an impractical task given the computational power required.**
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-whitepaper-series/section-3-timestamp-server-bitcoin-whitepaper/timestamped-hashes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
