Abstract
Outpoint BEEF is Atomic BEEF 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 / BRC-96 BEEF. Use for proofs scoped to a specific output (e.g. 1Sat tip provenance in BRC-150).
Specification
| Atomic BEEF (BRC-95) | 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.
- Completeness is profile-defined. Outpoint BEEF alone does not define sat ordering, inscription rules, or BSV-21 admission — see BRC-159 / BRC-160 / BRC-150 / BRC-176.
- 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 (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).