Skip to content

BRC-128: SSM transport note #168

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sirdeggen merged 1 commit into from
Jul 30, 2026
Merged

BRC-128: SSM transport note #168

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions transactions/0128.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,6 +148,10 @@ BRC-128 frames are fully compatible with the existing multicast infrastructure:
BRC-124 frames. The cache indexes by `(HashKey, SeqNum)`, not payload content.
- **Downstream consumers** — applications that receive forwarded frames inspect
payload bytes 4–9 to determine whether to parse as BRC-12 raw or BRC-30 EF.
- **Transport** — BRC-128 frames are byte-identical on the wire under ASM and
SSM. Multicast addressing, scopes, and the SSM `(S,G)` join and
source-discovery model are inherited from [BRC-124](./0124.md) and specified
in [BRC-129](./0129.md); the source is the emitting proxy (`senderIPv6`).

BRC-124 (BRC-12 payload) and BRC-128 (BRC-30 EF payload) frames can be
intermixed on the same multicast group without conflict.
Expand Down Expand Up @@ -238,3 +242,4 @@ Note that the headers are byte-identical; only the payload differs.
Subtree ID concept referenced in the frame header
- [BRC-124: Multicast Transaction Frame Format](./0124.md) — Header format
reused by this specification
- [BRC-129: Multicast Group Address Assignments](./0129.md) — SSM/ASM addressing, scopes, and `(S,G)` source discovery