Roadmap(SeM): Application Protocols

[kaiserd]

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

• raw RFC(standards): Status communities #166
  • Scaling Status Communities : Potential Problems #177
• raw RFC(BCP): Status communities over Waku Simple Scaling #167
• raw RFC(standards): Status 1:1 chat #168
  • RFC 55/STATUS-1TO1-CHAT : add section on private group chat

Overview over the integration of these tasks into the Status MVP

Milestones and Issues

• Waku e2e messaging
  • based on Status 1:1 chat
  • efficient, scaling, privacy/anonymity preserving 1:1 messaging on top of sharded Waku Relay
• secure group messaging based on Waku e2e messaging
  • based on Status group chat

[rymnc]

Should we also move 5/SECURE-TRANSPORT to vac research as an alternative to 35/WAKU2-NOISE?

[kaiserd]

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

[jm-clius]

@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.