Support Status application: continue integration of nwaku and provide new chat protocol stack.
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.
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

Complete integration of nwaku in Status Desktop (H1)
Simplify a reliable Waku API: aka Messaging API, make it easier to consume Waku library; critical to enable easy development of Chat SDK.
Upgrade Waku for the Web: Ensure web applications built on The Waku Network are reliable.
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.
Nwaku in Status Mobile and Light Mode MVP: de-prioritised in favour of cleaning up Waku and RLN APIs for Chat SDK first.
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

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

Chat/App Team

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

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.
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.
Support integrations: support projects that want to build with Waku SDK and Chat SDK.
Foster and join Nim ecosystem (nwaku): Foster and participate in the Nim developer community inside and outside IFT.
Join FOSS ecosystem: Be an active part of the FOSS developer community.
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:

Hardening and Scaling Foundations for Private Chats: finishing off the work and descoping items that have been identified as unneeded.
Nwaku in Status Desktop (Relay only): work continues, close to completion.
Nwaku in Status Mobile: deprioritized in favour of improving API for new Chat SDK
e2e reliability protocol: work continues, close to completion.
Foundation for Communities Optimization: this includes finishing a migration, and move community traffic away from 1:1 chat so we complete the work.

New work and priorities:

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.

To finish in H1

Milestone	End Date	nwaku	app-chat
Introduce E2E Reliability in Status Communities	31 Aug		1
Foundation for Communities Optimisation	31 Oct		1
Hardening and Scaling Foundations for Private Chat	Completed/Drop
Integrate nwaku in Status Desktop, relay mode only	30 Jun	2
Deploy RLN Onchain Tree on L2 Testnet	30 Jun

H2 Milestones

Man month: 17.5 * 6 = 105 (Franck, Aaron full time mgmt/leadership/eco dev/comms, Hanno half-time)

Priority	Milestone	End Date	core res	js-waku	nwaku	app-chat	BD
1	Define Incentivisation for RLNaaS	31 Jul	1.5*1m
2	Improve DevEx: API, TWN, Metrics, Docs	31 Aug	1*1m	2*2m	1.5*2m	1*1m
3	Introduce mixnet for message sending	30 Sep	1*3m
4	Formalize and Expand Waku Web Apps	19 Dec				1.5*6m
5	Create Chat SDK MVP	30 Sep				3*3m
6	Integrate RLN with Waku API	30 Sep	1*1m	1*2m	1*2m
7	Streamline DevEx: Mobile, Rust and Web dev	30 Nov		1*1m	1*2m
8	Extend Chat SDK with Group Conversations	19 Dec				2*3m
9	Incentivisation follow-up Outline	TBD	1.5*5m
10	Nim Usage Improvements	19 Dec			1*2m
11	BD - Acquire 10 Customers	19 Dec				0.5*6m	1*6m

Pushed to 2026

WebTransport: depending on nim-libp2p (delivery Q4)
Implementing Waku API in REST: 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
Follow-up steps for incentivization: part of current milestone is to produce a roadmap.
RLN mainnet and audit -> probably wait for Status L2 mainnet?
Signal network

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

README.md Unescape Escape

Waku Draft Roadmap

Proposed Priorities

Whole Team