logos-messaging/pm
1
0
Fork 0
mirror of https://github.com/logos-messaging/pm.git synced 2026-01-02 14:13:09 +00:00
Code Issues Packages Projects Releases Wiki Activity
pm/draft-roadmap
History

README.md

Waku Draft Roadmap

Finalised roadmap and milestones can be found on the Logos roadmap.

Period in planning: 2025 H2

Proposed Priorities

Whole Team

  1. Support Status application: continue integration of nwaku and provide new chat protocol stack.
  2. Support Logos Core: ensure that any library and API we push to developers can be consumed in Logos Core; review and prioritize any requirements coming from Logos Core project contributors and developers.
  3. Developer and Contributor Experience: Review and improve dev assets (docs) and set quality expectation across the team (docs provided with deliverables, etc); Review and take action to improve developer and contributor experience (nimble usage, vscode plugin, etc).

Core Team

  1. Complete integration of nwaku in Status Desktop.
  2. Simplify a reliable Waku API: aka Messaging API, make it easier to consume Waku library; critical to enable easy development of Chat SDK.
  3. Upgrade Waku for the Web: Ensure web applications built on The Waku Network are reliable.
  4. RLN mainnet and API: Continue RLN migration to onchain tree + L2 testnet, and necessary steps to get RLN on mainnet; provide simple API for Chat SDK.
  5. Nwaku in Status Mobile and Light Mode MVP: de-prioritised in favour of cleaning up Waku and RLN APIs for Chat SDK first.
  6. nwaku performance improvement: Performance on mobile is critical, hence we will review benchmarks and potentially dedicate effort to this topic (note there is some ongoing effort from Status fleet behaviour).

Research Items

  1. RLN (as above)
  2. Incentivisation: Deliver incentivisation PoC for reliability, scalability, risk (running own fleet) and sustainability.
  3. Decentralisation and privacy: continue research work to further decentralised Waku protocols, specifically store, and increase anonymity properties with libp2p-mixnet

Chat/App Team

  1. Chat SDK: Build a chat SDK (new protocol), learning from Status’ experience. Focus for an iterative delivery of the foundational blocks. Targeting private chats and early RLN integration.
    1. Note that building blocks such as identity mgmt are being built for demos app like Qaku - alignment to define and provide common protocols is expected as we are not limited by existing Status chat protocol.
    2. Work in close partnership with the status-backend developers, to ensure that post-refactoring the SDK can be integrated with the least effort possible. Aim for early and iterative integration.
    3. Note that early Status backend design position chat SDK as backend for Communities too; early iteration may not provide the scale in terms of members per communities; but Status' requirement is noted.
    4. Minimum deliverable will be usability of Chat SDK in Logos Core; need to review the architecture expectation in terms of Logos Core plugin interaction chat sdk <> nwaku.
  2. Build demos and PoC apps: Continue building PoC apps to teach how to hunt, dogfood and battle test libraries; as well as throwing ideas in the wild, experimenting and seeing what sticks; promising apps will have lib and specs implemented (e.g. Qaku and Logos Forum).
    1. Potentially expand the relevant platforms: from Web to Logos core, Nim/seaqt, Rust, etc.
    2. Integration with Codex still planned under this umbrella
    3. Review Logos Forum (Opchan) requirements; the 2025 Logos Movement Strategy is the new customer.

Business and Ecosystem Development Team (BD + Solution Eng)

  1. Measure Success: Develop and deploy tools to measure Waku success in terms of users, developers and contributors across all known Waku networks (Status, RAILGUN, TWN, etc)
    1. In partnership with BI.
  2. Waku Chat MVP: Proceed with the same exercise done for Waku MVP. Consult with current and new leads on their ideal Chat SDK. Understand how confident we are they would onboard on Waku if it is delivered and feedback to Chat/App team to take in account for prioritization.
  3. Support integrations: support projects that want to build with Waku SDK and Chat SDK.
  4. Foster and join Nim ecosystem (nwaku): Foster and participate in the Nim developer community inside and outside IFT.
  5. Join FOSS ecosystem: Be an active part of the FOSS developer community.
  6. Continue planned Rust SDK work: Messaging API and stable nwaku integration in Status Desktop and pre-requisites to a quality Rust SDK.

Status Priorities Review

Existing milestones:

New work and priorities:

  1. New Chat SDK (nim) and protocol stack

Draft Milestones

Testing out new format, once approved:

  • Milestones are moved to Logos roadmap
  • Deliverables are moved to GitHub issues
  • Waku FURPS remains in FURPS

In order of priority.

Priority Milestone End Date core res js-waku nwaku app-chat
1 Introduce E2E Reliability in Status Communities 31 Aug 1*2m
2 Foundation for Communities Optimisation 31 Oct 1*2w
3 Hardening and Scaling Foundations for Private Chat Drop
4 Integrate nwaku in Status Desktop, relay mode only 20 Jun
5 Deploy RLN Onchain Tree on L2 Testnet 30 Jun
6 Define Incentivisation for RLNaaS 31 Jul 1.5*1m
7 Improve DevEx: API, TWN, Metrics, Docs TBD TBD TBD TBD TBD
8 Introduce mixnet for message sending 30 Sep 1*3m
9 Formalize Logos Web Apps 19 Dec 1.5*6m
10 Introduce Chat SDK by enabling basic one-to-one chats TODO TBD TBD
11 Integrate RLN with Waku API TBD TBD 1*2m TBD
12 Streamline DevEx: Mobile, Rust and Web dev TBD TBD? TBD TBD
13 Incentivisation follow-up TBD TBD
14 Nim Usage Improvements TBD TBD

Pushed to 2026

  • WebTransport: depending on nim-libp2p (delivery Q4)
  • REST API for Waku API: Useful for DST/QA, but let's focus on Status, Chat SDK, and Rust first

Not yet planned/not sure:

  • nwaku performance on mobile: let's focus on finishing desktop integration and getting API ready for Chat SDK + RLN
  • quic: need to review where to put it, should be easy.
  • Follow-up steps for incentivization: part of current milestone is to produce a roadmap.
  • RLN mainnet and audit -> probably wait for Status L2 mainnet?

Business Development Milestones

TODO

Gantt

TODO: fix dates

gantt
    title Waku 2025H2
    dateFormat YYYY-MM-DD
    axisFormat %b
    section core research (6)
        Define Incentivization for RLNaaS: 2025-07-01, 2025-08-01
        Define Incentivization for RLNaaS: 2025-07-01, 2025-08-01
        Improve DevEx: 2025-08-01, 2025-09-30
        Mixnet: 2025-07-01, 2025-09-30
        Integrate RLN with Waku API: 2025-07-01, 2025-09-01
        Streamline DevEx: 2025-09-01, 2025-12-31
        Incentivization follow-up: 2025-10-01, 2025-12-31
    section nwaku
        Status Desktop: 2025-07-01, 2025-08-01
        RLN Onchain Tree: 2025-07-01, 2025-08-01
        Improve DevEx (API): 2025-07-01, 2025-10-01
        Improve DevEx (TWN): 2025-07-01, 2025-09-01
        Streamline DevEx (Mobile, Rust): 2025-09-01, 2025-12-31
        RLN Library: 2025-08-01, 2025-12-31
    section js-waku
        Improve DevEx (API): 2025-07-01, 2025-10-01
        Improve DevEx (TWN): 2025-07-01, 2025-10-01
        RLN Library: 2025-07-01, 2025-09-01
        Streamline DevEx (Local dev): 2025-10-01, 2025-12-31
    section app-chat
        E2E Reliability: 2025-07-01, 2025-08-01
        Communities Opt: 2025-07-01, 2025-08-01
        Foundations Private Chats: 2025-07-01, 2025-08-01
        Improve DevEx (metrics): 2025-07-01, 2025-09-01
        Logos Web Apps: 2025-07-01, 2025-12-31
        Chat SDK: 2025-07-01, 2025-12-31