2023-12-18 Waku weekly §

Targeted dogfooding for Status Communities §

• achieved: fix panic on logout, publish messages async, fix loading message history for communities, fix invalid bootnodes being used on status desktop, status dogfooding, raise issues and optimizations needed wrt light protocols usage in status-go and improvements to be done in nwaku,
• next: continue dogfooding / fixing issues

Support Many Platforms - 2024-04-30 §

Presentation Readiness §

[js-waku] feat: filter subscription API

• achieved: rebasing
• next: error handling via event emitter as well. plan if restructuring is required.

Other Work §

Enhancements §

[nwaku] feat: Have additional Admin REST API endpoints that helps node operator in monitoring

• achieved: improved logging and merged. Created locally a new REST endpoint that returns the information of all the filter subscriptions on a service node
• next: add unit tests, update documentation and open PR

[research] Sync store baseline understanding

• achieved: PoC of Prolly Tree (fixing a Bug), insertion and deletion of data into it.
• next: a writeup about Prolly trees PoC in issue, further testing, generating some operational data details such as memory consumption using RLN specs.

Bugs §

[nwaku] bug/regression: Relay connection works no more

• achieved: reproduced the issue both in testing framework and with local nodes, analyzed logs and narrowed down to the commit where things got broken
• next: continue investigating, find root cause and fix

[nwaku] bug: no messages returned from store node when multiple content topics and start/end time are used

• achieved: bug fix store service in nim-waku when the query used more than one content topic

Documentation §

[docs.waku.org] Document how to use k-anonymity with content topic

• achieved: add content topic buckets consideration #153

Chores §

[nwaku] Bump vendor dependencies for release 0.23.0

• achieved: bump all nim-waku vendor dependencies