Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
jimstir opened this issue Jun 14, 2024 · 0 comments
Open

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

jimstir opened this issue Jun 14, 2024 · 0 comments

Comments

@jimstir
Copy link
Collaborator

jimstir commented Jun 14, 2024

Reference Issue: vacp2p/rfc#520
Author: kaiserd

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

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

No branches or pull requests

1 participant