Integrate nwaku in Status Desktop, relay mode only
Estimated date of completion: 30 June
Resources Required for 2025H2:
- 1 nwaku engineer for maintenance and support
- Vac-QA to run status-backend tests on a nwaku-based build
- Vac-DST to complete benchmark works and proceed with nwaku-based vs go-waku-based status-backend comparisons
- Status-QA to include nwaku-based builds in tests
With this milestone, Status Desktop builds can use nwaku instead of go-waku. However, it should be seen as a MVP as further hardening and implementation of light client mode will be missing. Go-waku will still be used for Status Mobile.
This strategy enables concrete steps toward sunsetting go-waku in a short period of time, avoiding a perpetual prototyping phase where many high risk problems (e.g. mobile bundle size, etc) have to be solved before the switch can be made.
The next milestone will then focus on hardening the nwaku Desktop build and implement missing features such as Reliability Protocol for resource-restricted. Once done, it will reduce the scope of go-waku maintenance to light clients only and drastically reduce the duplicate work done between nwaku and go-waku.
Note that we want to draw the line to RLN in terms of go-waku maintenance, meaning that if Status were to use RLN (see Scale 1:1 chat messages PoC), then it should happen with nwaku.
FURPS:
GitHub Milestone and deliverables: https://github.com/waku-org/pm/milestone/33
Enable Waku Metrics in libwaku
Owner: nwaku
Feature: nwaku
FURPS:
- F3. Metrics can be enabled in libwaku.
https://github.com/waku-org/nwaku/issues/3202
Checklist:
- Specs: link to specs and/or API definition
- Code: link to GitHub issues/PRs/Epic
- Dogfood: link to dogfooding session/artefact
- Docs: links to README.md or docs.waku.org (TBD)