Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

New RFC: 39/WAKU2-CAPABILITY-DISCOVERY #520

Closed
Tracked by #118
kaiserd opened this issue Jul 29, 2022 · 1 comment
Closed
Tracked by #118

New RFC: 39/WAKU2-CAPABILITY-DISCOVERY #520

kaiserd opened this issue Jul 29, 2022 · 1 comment
Labels
track:discovery Discovery track (Secure Messaging/Waku Product)

Comments

@kaiserd
Copy link
Contributor

kaiserd commented Jul 29, 2022

This issue is part of the Waku ambient discovery roadmap (new roadmap issue to be opened in the research repo; will edit/update this description once the roadmap issue is open)
and tracks the editing of a new RFC specifying a Waku capability discovery protocol.

Background

In its first version, it will simply be libp2p identify
with restrictions on specific fields.
Having a separate Waku specification makes sense because

  • the Vac RFC set should comprehensively specify Waku. Capability should not (implicitly) be delegated to an external spec.
  • it allows to expand the protocol in the future, which we plan to do.

Also see #521

@kaiserd kaiserd added the track:waku-specs Waku specs track (RAD) label Jul 29, 2022
@kaiserd kaiserd self-assigned this Jul 29, 2022
@kaiserd kaiserd added track:discovery Discovery track (Secure Messaging/Waku Product) and removed track:waku-specs Waku specs track (RAD) labels Aug 1, 2022
@kaiserd kaiserd removed their assignment Aug 22, 2022
@jimstir
Copy link
Contributor

jimstir commented Jun 14, 2024

Issue moved here

@jimstir jimstir closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
track:discovery Discovery track (Secure Messaging/Waku Product)
Projects
Status: Later/Icebox
Development

No branches or pull requests

2 participants