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

# Outpoint BEEF

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

## Abstract

**Outpoint BEEF** is [Atomic BEEF](/transactions/0095.md) with a **subject outpoint** instead of a subject transaction id. Encoding, inclusion, and validation follow BRC-95 except as in the table below. The body is a standard [BRC-62](/transactions/0062.md) / [BRC-96](/transactions/0096.md) BEEF. Use for proofs scoped to a specific output (e.g. 1Sat tip provenance in [BRC-150](/tokens/0150.md)).

## Specification

|                  | Atomic BEEF ([BRC-95](/transactions/0095.md)) | Outpoint BEEF (this BRC)                                                                                        |
| ---------------- | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| Prefix (4 bytes) | `0x01010101`                                  | `0x16a7beef`                                                                                                    |
| Subject          | TXID (32 bytes)                               | TXID (32 bytes) + vout (uint32 LE, 4 bytes)                                                                     |
| Body             | BEEF                                          | BEEF (same rules)                                                                                               |
| Graph            | Ancestors of the subject **transaction**      | Bundle of transaction proofs needed for the subject **outpoint** (profile-defined; not limited to tx ancestors) |
| Fail if          | Subject tx missing, or unrelated txs present  | Any transaction required for the proof is missing                                                               |

```
16a7beef                                                 // prefix
2222222222222222222222222222222222222222222222222222222222222222 // subject TXID
00000000                                                 // subject vout (uint32 LE)
0200beef                                                 // BEEF V2 (example)
...
```

## Notes (informative)

* The embedded BEEF MAY include transactions that are not ancestors of the subject tx (e.g. funding spent beside a 1Sat tip). That is intentional for profiles such as [BRC-150](/tokens/0150.md).
* Completeness is profile-defined. Outpoint BEEF alone does not define sat ordering or inscription rules — see [BRC-159](/tokens/0159.md) / [BRC-160](/tokens/0160.md) / [BRC-150](/tokens/0150.md).
* Bundle size grows with whatever the profile requires. For 1Sat tip→origin remittance, prefer extending a prior package and omitting oversized bags rather than dropping required input sources; see [BRC-150](/tokens/0150.md) (*Scalability*).
* Do not nest this envelope inside BRC-150 `beefB64`. Basket remittance stays the JSON object; Outpoint BEEF is a parallel binary wire format (gateways, other transports).


---

# 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://bsv.brc.dev/transactions/0158.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.