Merkle proof standardised format
Several documents refer to the same existing merkle proof format, and calling it different things invites confusion. This gives that format a number in this series so other proposals can point at it without ambiguity.
About Merkle proofs, the short chain of hashes that proves a transaction was mined.
AlsoSPV
Reference for an AI
Everything an assistant needs to answer questions about BRC-10 accurately, including what it depends on.
Summary
- Why
- Developers needed one unambiguous name to cite when referring to the Merkle proof format already defined by the TSC, instead of describing it informally each time.
- What
- BRC-10 is the BSV reference identifier for the externally defined TSC Merkle Proof Standardized Format, a way to prove a transaction is included in a block.
- How
- A developer cites BRC-10 by number when describing or depending on the TSC Merkle Proof Standardized Format, and reads the external TSC page for the actual field-level definition.
What this lets you do
- Point to BRC-10 as the canonical name for the TSC Merkle proof format
- Verify a transaction is included in a block using a standard proof structure
- Reference the proof format consistently across BRC-11 and other extending standards
- Avoid inventing a custom proof format when one already exists
Written by claude-sonnet-5 from the specification text. Where the two differ, the original is correct.
The specification
Abstract
This BRC serves as a reference point for the TSC Merkle Proof Standardized Format. It is identified as BRC-10 and is used to avoid ambiguity in referring to the TSC standard, just like other proposals like BRC-11 (which revise or extend this specification) are referenced by their BRC numbers.
Motivation
To avoid ambiguity in referring to the TSC Merkle Proof Standardized Format, it is important to have a specific identifier. The use of BRC-10 as a reference point allows for clear and unambiguous communication among developers and the community. The BRC-10 designation is similar to other proposals, such as BRC-32, which are also referenced by their BRC numbers.
Specification
You can read the TSC standard on the website.
Discussion
As with any other BRC, feel free to open issues in the BRC repository that discuss extensions of BRC-10.