Subtree Data Frame Format
The list of transaction hashes making up a subtree also needs to travel over an ordinary byte stream, not just one-to-many delivery. This defines that form and how a receiver takes it in.
8 standards
Block structure
The parts of a block rather than the transactions inside it: headers, the coinbase transaction, and the subtrees that large blocks are announced and transferred in.
Also searched as block header, coinbase, subtree, anchor, block announcement.
What Merkle root means
A single hash at the top of a tree built from every transaction in a block, stored in the block header. Any change to any transaction changes it.
Open in the glossaryFiled under
All 8 sit in Transactions, so browsing that topic finds the same standards.
Start with
BRC-144
Block Frame Format
A block pushed over a stream connection needs an agreed layout for its header, its parts and its first transaction. This defines it.
Filed under Transactions
Standards about this
Block structure is the main subject of these 2.
143 144 Block Frame Format
A block pushed over a stream connection needs an agreed layout for its header, its parts and its first transaction. This defines it.
Standards that touch it
These are about something else, and deal with block structure on the way.
11 TSC Proof Format with Heights
Merkle proofs identify the block they belong to by its hash, which means anyone checking one has to keep every block hash to look it up. This argues for using the block's height instead, roughly halving what a lightweight client needs to store.
83 Scalable Transaction Processing in the BSV Network
Handling very high transaction volume means doing as much as possible at the same time, while some checks must still happen in order. This describes how that work is divided across the network so throughput rises without correctness slipping.
131 Multicast Block Announcement Frame Format
Clients need to know when a new block arrives, and polling for it wastes time and bandwidth. This pushes the block's summary to everyone listening as soon as it exists.
132 Multicast Subtree Data Frame Format
Knowing a subtree exists is not the same as having the transaction hashes in it. This defines a frame carrying those contents to everyone subscribed, so nobody has to request them.
133 Multicast Coinbase Transaction Frame Format
The first transaction in a block is a special case, and it does not travel with the ordinary transaction stream. This says how it is carried and who receives it.
135 Multicast Block Header Frame Format
A client that only tracks block headers should not have to receive a whole block announcement to get one. This carries the eighty-byte header on its own.
Usually read alongside
Concepts that keep appearing on the same standards as this one.
Was this helpful?