Repository navigation
Description
Note
🤖 GPT-6 via Codex drafting on behalf of @marcinczenko
Part of Use Service Discovery — #32. Related: MixTransport DHT proxy deliverable #34 and implementation #41.
Objective
Use service discovery to find suitable DHT proxies and perform provider lookups through those proxies over MixTransport.
Storage PR #1581 implements the first MixTransport-based proxy exchange. Storage PR #1582 introduces service discovery, including DHT Mix proxies. This task starts by assessing how those changes fit together; it does not assume additional implementation is necessary.
Service discovery finds a proxy. The subsequent DHT proxy exchange asks that proxy for content providers. Keep those operations and their privacy implications distinct.
Follow-up
- Recheck both PRs and record exact specification, dependency, and code revisions.
- Trace proxy advertisement, service lookup, record validation, proxy selection, and MixTransport stream establishment. Map relevant code and tests; identify what #1582 already provides.
- Verify discovered records supply the required identity, compatible service/protocol information, and usable Mix public addressing. Identify gaps rather than assuming XPR and signed peer records are interchangeable.
- Discuss bootstrap/discovery privacy, refresh and expiry, failures, and interaction with static configuration. Preserve no direct client-side DHT fallback for provider lookups requested through Mix.
- Record findings and agreed decisions; propose only the remaining integration changes and tests.
- Validate a dynamically discovered compatible proxy serving a provider lookup over MixTransport, plus unsuitable records, unavailable proxies, and bounded failure behavior.
Working records
Interactive investigation note: Service Discovery for MixTransport DHT Proxies, in the Logos Storage Obsidian vault, 10 Notes/. It is a local working note, not yet published. Keep essential decisions and acceptance evidence in this issue or linked repository documentation so team access does not depend on the vault.
Start with the Logos specification and Nim implementation.
This is a planning placeholder. General attribute-query discovery is background, not an agreed requirement. Implementation remains paused pending investigation and scope agreement.
Activity