> 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/0233.md).

# Subject BEEF

David Case (<david.case@shruggr.cloud>)

## Abstract

**Subject BEEF** is [Atomic BEEF](/transactions/0095.md) in shape (a prefix and a subject transaction id in front of a [BRC-96](/transactions/0096.md) BEEF V2) without BRC-95's restriction to the subject's ancestors. The subject names which transaction the bag is about. Anything else in the bag is allowed: a profile decides what must be present.

## Specification

|                  | Atomic BEEF ([BRC-95](/transactions/0095.md)) | Subject BEEF (this BRC)                   |
| ---------------- | --------------------------------------------- | ----------------------------------------- |
| Prefix (4 bytes) | `0x01010101`                                  | `0x5709beef`                              |
| Subject          | TXID (32 bytes)                               | TXID (32 bytes)                           |
| Body             | BEEF                                          | BEEF V2 ([BRC-96](/transactions/0096.md)) |
| Graph            | Ancestors of the subject transaction          | Any transactions                          |
| Fail if          | Subject tx missing, or unrelated txs present  | Subject tx missing                        |

```
5709beef                                                 // prefix
2222222222222222222222222222222222222222222222222222222222222222 // subject TXID
0200beef                                                 // BEEF V2 (example)
...
```

## Notes (informative)

* A reader MUST NOT apply BRC-95's ancestor rule or strip transaction bodies from a Subject BEEF. Re-encoding it as Atomic BEEF may drop transactions a profile requires.
* Completeness is profile-defined (e.g. [BRC-176](/tokens/0176.md)). Subject BEEF alone says only which transaction is the subject.
* The distinct prefix lets a strict Atomic BEEF reader fail cleanly instead of rejecting a valid bag as malformed Atomic BEEF.
* For a subject output rather than a transaction, use [Outpoint BEEF](/transactions/0158.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/0233.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.