Skip to content

beacon: optional destination-carrying relay delivery (0x08/0x09)#35

Merged
TeoSlayer merged 2 commits into
mainfrom
feat/dest-carrying-relay-delivery
Jun 21, 2026
Merged

beacon: optional destination-carrying relay delivery (0x08/0x09)#35
TeoSlayer merged 2 commits into
mainfrom
feat/dest-carrying-relay-delivery

Conversation

@TeoSlayer

Copy link
Copy Markdown
Contributor

Implements the beacon side of the opt-in extended-discovery message types.

  • Endpoints that register via BeaconMsgDiscoverEx (0x08) are tracked in a dstNodes set.
  • Their final-hop relay frames are delivered as BeaconMsgRelayDeliverDest (0x09 = [0x09][src(4)][dest(4)][frame]) so a receiver fronting more than one node id can resolve which one the frame is for.
  • All other endpoints keep receiving legacy BeaconMsgRelayDeliver (0x06). Fully backward-compatible / opt-in.

Depends on pilot-protocol/common#21 (the 0x08/0x09 constants). CI will be red until that merges and a common release is bumped in here.

teovl added 2 commits June 21, 2026 15:15
v0.5.4 adds BeaconMsgDiscoverEx (0x08) and BeaconMsgRelayDeliverDest (0x09)
which this PR references in server.go.
@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 8fc66a4 into main Jun 21, 2026
5 of 6 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