Skip to content

protocol: extended-discovery beacon message types (0x08/0x09) #21

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
TeoSlayer merged 1 commit into from
Jun 21, 2026
+10 −0
Merged

protocol: extended-discovery beacon message types (0x08/0x09) #21

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
10 changes: 10 additions & 0 deletions protocol/header.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,4 +85,14 @@ const (
BeaconMsgRelay byte = 0x05
BeaconMsgRelayDeliver byte = 0x06
BeaconMsgSync byte = 0x07 // gossip: beacon-to-beacon node list exchange

// Extended discovery for endpoints that cannot infer a relayed frame's
// destination implicitly. A standard endpoint owns a single node id, so
// BeaconMsgRelayDeliver (0x06 = [0x06][srcNodeID(4)][frame]) carries no
// destination. An endpoint registered via BeaconMsgDiscoverEx (same wire
// shape as BeaconMsgDiscover: [0x08][nodeID(4)]) instead receives
// BeaconMsgRelayDeliverDest = [0x09][srcNodeID(4)][destNodeID(4)][frame...].
// Opt-in: endpoints registered with 0x01 keep receiving 0x06.
BeaconMsgDiscoverEx byte = 0x08
BeaconMsgRelayDeliverDest byte = 0x09
)
Loading