> 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/bsv-theory/simplified-payment-verification/transaction-acceptance.md).

# Transaction Acceptance

> He can't check the transaction for himself, but by linking it to a place in the chain, he can see that a network node has accepted it, and blocks added after it further confirm the network has accepted it.
>
> \- Satoshi Nakamoto, Bitcoin Whitepaper

![](/files/hyviIYn9eD6WNxxxfdS7)

By being able to validate that the hash of the transaction itself (the TXID) can be probably shown to exist in a block that has been accepted and built upon by the network, a user can safely say that the transaction is valid.

This allows a user with a set of block headers to build a verifiable history of all transactions that are relevant to their needs and provides a clear and simple means to demonstrate that proof to other peers on the network. This is important for any application that builds upon information that is stored on the ledger and allows users to ensure that the information is valid and exists in a block.


---

# 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 dynamically by asking a question.

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

```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-theory/simplified-payment-verification/transaction-acceptance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.