Background Evaluation Extended Format (BEEF) Transactions
The core proof-carrying transaction container used by current implementations.
SPV foundation
Exchange proof-carrying transactions
Choose current transaction and Merkle-proof containers, then scope them to a transaction or output.
Recommended sequence
Build the boundaries in order
- 01
Encode the proof path
Represent Merkle paths in interoperable binary or unified forms.
- 02
Package the transaction graph
Carry transaction ancestry and proofs in the BEEF family of formats.
- 03
Name the subject
Use transaction-scoped or output-scoped envelopes according to what the receiver must prove.
Take the next step
Turn the map into a working plan
The working set
Standards in this path
Merkle Path Binary Format
We propose a binary format for a Single Merkle Path optimized for storage in a key value database.
BSV Unified Merkle Path (BUMP) Format
We propose the BSV Unified Merkle Path format in both binary and JSON encoding optimized for generation by transaction processors, and also happens to be convenient for proof validating clients. At a high level the format encodes a number of txids which all exist within one particular block, along with each of their merkle paths and the blockHeight. The bloc
Atomic BEEF Transactions
Adds a single subject transaction to a BEEF package for portable verification.
BEEF V2, Txid Only Extension
The BEEF serialization format (as defined in BRC-62) is essentially two things: An array of mined transaction proof validation data (BUMPS BRC-74) An array serialized Bitcoin transactions In practical use, BEEFs are exchanged between parties to build and process new transactions as well as validate arbitrary data recorded on the blockchain. The extension pro
Outpoint BEEF
Scopes a BEEF proof package to one transaction output.
This path is guidance, not a new protocol or maturity designation. Check each BRC’s upstream status note, normative language, and implementation section before shipping.
Editorial policy →