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.

Sign up for GitHub

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

Jump to bottom

Draft milestone: Waku Capability Discovery/Push #118

Closed
3 of 5 tasks
Tracked by #116
kaiserd opened this issue Aug 1, 2022 · 4 comments
Closed
3 of 5 tasks
Tracked by #116

Draft milestone: Waku Capability Discovery/Push #118

kaiserd opened this issue Aug 1, 2022 · 4 comments
Labels
track:discovery Discovery track (Secure Messaging/Waku Product)

Comments

@kaiserd
Copy link
Contributor

kaiserd commented Aug 1, 2022 •
edited
Loading

This milestone issue tracks the specification and implementation of identify and identify/push
as simple Waku v2 capability discovery and capability push, respectively.

Note

For now, we only cover the frist issue of this milestone, which specifies identify and identify/push as libp2p protocols that may directly be used by Waku v2. The reason is that these two protocols are anyway used by the libp2p connection establishment layer Waku v2 is based on.
The rest of the tasks, namely introducing new Vac specific protocols with better anonymity properties, will be addressed in the future.

Issues
@kaiserd kaiserd mentioned this issue Aug 1, 2022
Closed
8 tasks
@kaiserd kaiserd self-assigned this Aug 1, 2022
@kaiserd kaiserd added the track:discovery Discovery track (Secure Messaging/Waku Product) label Aug 1, 2022
@kaiserd kaiserd mentioned this issue Aug 1, 2022
Closed
4 tasks
@kaiserd kaiserd added the milestone Milestone issue with a subset of issues within a specific track label Aug 16, 2022
@oskarth
Copy link
Contributor

oskarth commented Aug 24, 2022

@kaiserd

  1. Is it accurate that this is in icebox? I.e. not planned to be worked on for long period
  • if so makes sense to unassign yourself
  1. Is this one of the most immediate milestones for the Discovery track after PEX?

@kaiserd kaiserd removed their assignment Aug 24, 2022
@kaiserd
Copy link
Contributor Author

kaiserd commented Aug 24, 2022 •
edited
Loading

@oskarth

  1. Is it accurate that this is in icebox? I.e. not planned to be worked on for long period

yes. Until we decide to move on from libp2p identify.
Because libp2p uses identify anyways, and we don't need any functionality past that for now, we decided to use stock identify for now.

  • if so makes sense to unassign yourself

done

  1. Is this one of the most immediate milestones for the Discovery track after PEX?

There is no immediate milestone after PEX on the Discovery track for now. They are all "future work".
I moved this milestone into "future items" on the roadmap.
(I'll work on anonymity after PEX, as anonymity has more immediate impact.)

@oskarth
Copy link
Contributor

oskarth commented Aug 24, 2022

The is no immediate milestone after PEX on the Discovery track for now. They are all "future work".

I'll remove the milestone label then too, that way it is more clear what "now" and "next" looks like for each track.

@oskarth oskarth changed the title Waku Capability Discovery/Push Draft milestone: Waku Capability Discovery/Push Aug 24, 2022
@oskarth oskarth removed the milestone Milestone issue with a subset of issues within a specific track label Aug 24, 2022
@kaiserd
Copy link
Contributor Author

kaiserd commented Nov 23, 2023

Ownership of this issue has been moved to Waku: waku-org/pm#101

@kaiserd kaiserd closed this as not planned Won't fix, can't repro, duplicate, stale Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
track:discovery Discovery track (Secure Messaging/Waku Product)
Projects
Secure Messaging (SeM)
Status: Later/Icebox
Milestone
No milestone
Development

No branches or pull requests
2 participants
@oskarth @kaiserd