Skip to content

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

Merged
TeoSlayer merged 1 commit into
mainfrom
feat/beacon-extended-discovery
Jun 21, 2026
Merged

protocol: extended-discovery beacon message types (0x08/0x09)#21
TeoSlayer merged 1 commit into
mainfrom
feat/beacon-extended-discovery

Conversation

@TeoSlayer

Copy link
Copy Markdown
Contributor

Adds two opt-in beacon message types for endpoints that cannot infer a relayed frame's destination implicitly.

  • BeaconMsgDiscoverEx (0x08) — same wire shape as BeaconMsgDiscover ([0x08][nodeID(4)]); registers a node id and requests destination-carrying delivery.
  • BeaconMsgRelayDeliverDest (0x09) — [0x09][srcNodeID(4)][destNodeID(4)][frame...]; final-hop delivery that includes the destination node id, so a receiver that fronts more than one node id can route it.

Standard single-identity endpoints are unaffected: a node registered with 0x01 keeps receiving 0x06. Constants only — the beacon-side handling is a companion PR in pilot-protocol/beacon.

@codecov

codecov Bot commented Jun 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@TeoSlayer TeoSlayer merged commit 29d3315 into main Jun 21, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants