Beersy
BRC-134

Multicast Anchor Transaction Frame Format

The first transaction in a chain has to arrive before any that depend on it, or the rest cannot be checked. This gives it its own frame so it can be treated as the prerequisite it is.

About Multicast, sending one transaction to many listeners at once.

AlsoFormatsFrames

Jeff Harrischanged 11 Nov 20264 min read

Reference for an AI

Everything an assistant needs to answer questions about BRC-134 accurately, including what it depends on.

Summary

Why
are needed by every listener regardless of shard, so they cannot be routed through the per-shard sharding scheme used for ordinary transactions.
What
BRC-134 is a frame format, version 0x06, for delivering chained transactions to every subscriber over a shared control-plane multicast group instead of per-shard groups.
How
A proxy stamps a and into a 92-byte header carrying 0x06 and sends it to the multicast group, where listeners detect gaps and retry endpoints resend on NACK.

What this lets you do

  • Route anchor transactions to a single control-plane multicast group so no subscriber misses them
  • Reuse the layout with a new frame version byte for anchor frames
  • Give anchor frames an independent flow identity via a virtual HashKey ingredient
  • Recover missed anchor frames through the same NACK and retry mechanism as shard frames
  • Stamp HashKey and SeqNum at the proxy so listeners can detect gaps

Written by claude-sonnet-5 from the specification text. Where the two differ, the original is correct.

magic+ver+txidhashkey+seqnumpayloadpayload0

The specification

Abstract

This BRC defines a new (0x06) for distributing chained transactions over the IPv6 multicast fabric. An is the root (first) transaction in a chain of dependent transactions. Because all subsequent transactions in the chain reference the anchor as an input, every subscriber must receive it regardless of which shard its TxID would otherwise hash to.

This BRC is licensed under the Apache License 2.0.

Motivation

The multicast fabric shards ordinary transactions across per-shard multicast groups based on the top bits of each TxID. Chained anchor transactions cannot be sharded this way because:

  1. Dependency root — all dependent (chained) transactions in the set reference the anchor's TxID as an input. A subscriber that misses the anchor cannot validate any dependent transaction in the chain.
  2. Unpredictable placement — the anchor's TxID is not known in advance by subscribers; they cannot pre-join the correct shard group.
  3. Cross-shard span — the chain may span many shards. The anchor itself might hash to shard 0 while dependents are spread across shards 1–15. Every subscriber needs the anchor irrespective of which shards they follow.
  4. Visibility over confirmation — anchor transactions do not need to be confirmed before use; they need only to be visible and valid. Wide visibility is the primary requirement.

BRC-134 addresses this by routing anchor frames to the group (FF0E::B:FFFE), the same global control channel used for and (BRC-131, BRC-133). All subscribers join this group unconditionally.

Specification

Control-Plane Multicast Group

Anchor frames are delivered on the GroupBlockBroadcast group:

IndexCompressed AddressConstant
0xFFFEglobalFF0E::B:FFFEGroupBlockBroadcast

The global scope (FF0E) ensures anchor transactions cross site boundaries and reach all geographically distributed subscribers. The group index 0xFFFE is in the reserved control-plane range and never overlaps with data-plane shard groups (maximum shard group index is 0x0FFF for shard_bits=12).

The address is shown in form (FF0E::B:FFFE), intra-domain only under RFC 8815; inter-domain and geographically distributed delivery uses the SSM address FF3E::B:FFFE (see BRC-129). The frame format and NACK path are unchanged. Anchors are user-submitted, so under SSM their source set (the emitting proxies, senderIPv6) is broader than the miner-only block and coinbase sources; receivers (S,G)-join 0xFFFE per the source set distributed per BRC-129.

Frame Header Format (92 bytes)

The BRC-134 header is layout-identical to BRC-124. Infrastructure components that inspect the Magic, , or fields read correct values at the same offsets.

OffsetSizeAlignFieldValue /
04—Network Magic0xE3E1F3E8 (BSV mainnet P2P magic)
42—Protocol Ver0x02BF (703, BSV large-block baseline)
61—Frame Version0x06 — BRC-134 anchor transaction
71—Reserved0x00
8328BTxIDSHA256d of the anchor transaction (internal byte order)
4088BHashKeyXXH64(senderIPv6 ∥ ∥ zeros); stamped by proxy
4888BSeqNumMonotonic per-sender counter; stamped by proxy; 0 = unset
56328BLayoutPad32All zeros (no scope for anchor frames)
884—PayloadLenSize of anchor transaction payload in bytes (uint32 BE)
92*—PayloadRaw serialised anchor transaction (no P2P )

Key distinction from BRC-124: the version byte at offset 6 is 0x06 rather than 0x02. All other field offsets and sizes are identical. The LayoutPad32 field at bytes 56–87 is always zeros — anchor frames have no subtree scope. The field is kept for layout uniformity: the proxy TCP reader, stamping path, listener, and retry endpoint all share the single HeaderSize constant.

Payload encoding: The payload is a raw BSV serialised transaction — version (4 bytes LE), input vector, output vector, locktime (4 bytes LE) — identical to the encoding used in BRC-12/BRC-124 frames.

Sequencing and Retransmission

BRC-134 frames participate in the same NACK-based reliability mechanism as BRC-124 shard frames:

  • The proxy stamps HashKey = XXH64(senderIPv6 ∥ 0xFFF9 ∥ zeros) and SeqNum (monotonic per sender) in-place before forwarding. The virtual index 0xFFF9 gives anchor frames an independent flow identity from BRC-131 block frames, which both travel on the same GroupBlockBroadcast multicast address. If the frame arrives pre-stamped (SeqNum != 0), it is forwarded verbatim.
  • Listeners observe (anchorGroupIdx=0xFFF9, zeroSubtreeID, HashKey, SeqNum, TxID) for gap detection and dispatch NACKs to retry endpoints on gap.
  • Retry endpoints join FF0E::B:FFFE and cache BRC-134 frames by HashKey ∥ SeqNum. On NACK, the frame is retransmitted to FF0E::B:FFFE.

Constants Reference

NameValueDescription
FrameVerV60x06BRC-134 chained anchor transaction frame version
GroupBlockBroadcast0xFFFEControl-plane multicast group index (shared with BRC-131/BRC-133)
GroupAnchorFlow0xFFF9Virtual HashKey ingredient; anchor flow identity (never a multicast address)

References

Was this helpful?

Search Beersy

Search standards by number, title, author or topic