> For the complete documentation index, see [llms.txt](https://bsv.brc.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bsv.brc.dev/transactions.md).

# Transactions

- [Everett-style Transaction Envelopes](https://bsv.brc.dev/transactions/0008.md)
- [Simplified Payment Verification](https://bsv.brc.dev/transactions/0009.md)
- [Merkle proof standardised format](https://bsv.brc.dev/transactions/0010.md)
- [TSC Proof Format with Heights](https://bsv.brc.dev/transactions/0011.md)
- [Raw Transaction Format](https://bsv.brc.dev/transactions/0012.md)
- [TXO Transaction Object Format](https://bsv.brc.dev/transactions/0013.md)
- [Transaction Extended Format (EF)](https://bsv.brc.dev/transactions/0030.md)
- [Merkle Path JSON format](https://bsv.brc.dev/transactions/0058.md)
- [Compound Merkle Path Format](https://bsv.brc.dev/transactions/0061.md)
- [Background Evaluation Extended Format (BEEF) Transactions](https://bsv.brc.dev/transactions/0062.md)
- [Simplified Payment Verification](https://bsv.brc.dev/transactions/0067.md)
- [Merkle Path Binary Format](https://bsv.brc.dev/transactions/0071.md)
- [BSV Unified Merkle Path (BUMP) Format](https://bsv.brc.dev/transactions/0074.md)
- [Graph Aware Sync Protocol](https://bsv.brc.dev/transactions/0076.md)
- [Scalable Transaction Processing in the BSV Network](https://bsv.brc.dev/transactions/0083.md)
- [Atomic BEEF Transactions](https://bsv.brc.dev/transactions/0095.md)
- [BEEF V2 Txid Only Extension](https://bsv.brc.dev/transactions/0096.md)
- [SubTree Unified Merkle Path (STUMP) Format](https://bsv.brc.dev/transactions/0119.md)
- [Multicast Transaction Frame Format](https://bsv.brc.dev/transactions/0124.md)
- [Multicast Transaction NACK Retransmission Protocol](https://bsv.brc.dev/transactions/0126.md)
- [Multicast Subtree Group Announcement Frame Format](https://bsv.brc.dev/transactions/0127.md)
- [Multicast Extended Transaction Frame Format](https://bsv.brc.dev/transactions/0128.md)
- [IPv6 Multicast Group Address Assignments](https://bsv.brc.dev/transactions/0129.md)
- [Multicast Transaction Frame Fragmentation](https://bsv.brc.dev/transactions/0130.md)
- [Multicast Block Announcement Frame Format](https://bsv.brc.dev/transactions/0131.md)
- [Multicast Subtree Data Frame Format](https://bsv.brc.dev/transactions/0132.md)
- [Multicast Coinbase Transaction Frame Format](https://bsv.brc.dev/transactions/0133.md)
- [Multicast Anchor Transaction Frame Format](https://bsv.brc.dev/transactions/0134.md)
- [Multicast Block Header Frame Format](https://bsv.brc.dev/transactions/0135.md)
- [Multicast Shard Manifest Announcement Protocol](https://bsv.brc.dev/transactions/0139.md)
- [Multicast Transaction Bundle Frame Format](https://bsv.brc.dev/transactions/0142.md)
- [Subtree Data Frame Format](https://bsv.brc.dev/transactions/0143.md)
- [Block Frame Format](https://bsv.brc.dev/transactions/0144.md)
- [Multicast Shard Domain Partitioning and the BEEF Object Plane](https://bsv.brc.dev/transactions/0148.md)
- [Multicast BEEF Object Frame Format](https://bsv.brc.dev/transactions/0149.md)
- [Outpoint BEEF](https://bsv.brc.dev/transactions/0158.md)
- [Subject BEEF](https://bsv.brc.dev/transactions/0233.md)


---

# 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://bsv.brc.dev/transactions.md?ask=<question>&goal=<user_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.