You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Proposal: decentralized service discovery through signed peer announcements
#1408
I’ve built an experimental service discovery feature for Yggdrasil. The idea is to help decentralized mesh networks discover services without relying on central DNS servers or service directories, while continuing to use existing IPv6 applications.
Nodes advertise named services with an IPv6 address, port, and transport (TCP, UDP, or both). Discovered services are available through yggdrasilctl getServices; automatic DNS resolution is not included.
The current rules:
Discovery and forwarding are enabled by default. No services are published unless explicitly configured.
Announcements are signed with the publisher’s Ed25519 key. Endpoints must belong to its key-derived node address or /64 subnet. Invalid announcements are neither stored nor forwarded.
With forwarding enabled, each new announcement is forwarded once to connected peers, excluding the incoming peer and original publisher. Cached foreign announcements are not periodically resent or replayed to new peers.
Duplicate or older announcements are ignored. A newer signed timestamp permits another forwarding round and updates the cached services.
Publishing defaults to every 15 minutes, configurable between 5 and 60 minutes. Announcements expire 60 minutes after their signed timestamp; forwarding never extends this.
Nodes without this feature ignore the additional message type and continue normal operation.
The prototype was developed with AI assistance, reviewed and manually tested by me on macOS. Automated tests pass with the race detector.
Would this be a useful addition to Yggdrasil itself, or would you prefer discovery to remain a separate application? I’d appreciate feedback before proposing a PR.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I’ve built an experimental service discovery feature for Yggdrasil. The idea is to help decentralized mesh networks discover services without relying on central DNS servers or service directories, while continuing to use existing IPv6 applications.
Nodes advertise named services with an IPv6 address, port, and transport (TCP, UDP, or both). Discovered services are available through yggdrasilctl getServices; automatic DNS resolution is not included.
The current rules:
The prototype was developed with AI assistance, reviewed and manually tested by me on macOS. Automated tests pass with the race detector.
More details, configuration examples, and implementation
Would this be a useful addition to Yggdrasil itself, or would you prefer discovery to remain a separate application? I’d appreciate feedback before proposing a PR.
All reactions