Closed kaiserd closed 10 months ago
Should we also move 5/SECURE-TRANSPORT to vac research as an alternative to 35/WAKU2-NOISE?
I'd say yes, as far as I currently see, this would be part of:
raw RFC(standards): Status 1:1 chat
<- I will instantiate this issue now to make it more clear.
In the future, the Status 1:1 chat could be based on: (not within the current MVP timeline)
Waku e2e messaging
Which would use 35/WAKU2-NOISE
@rymnc @fryorcraken closing this issue, as I believe the important app protocols have been moved to rfc.vac.dev. Feel free to reopen if I'm missing something.
Background / Motivation
This roadmap is part of Vac Secure Messaging (SeM). It lists work on protocols running on Waku core protocols and components.
Status 1 mio users Milestone
Overview over the integration of these tasks into the Status MVP
Milestones and Issues