--- title: 2024-09-30 Waku Weekly tags: - waku-updates date: 2024-09-30 --- ## [Milestone - Store Service Upgrade](https://github.com/waku-org/pm/milestone/28) - [Store v3-beta - Message Hashes](https://github.com/waku-org/pm/issues/131) - achieved: - [chat] go-waku: ratelimit store queries and add options to `Next` to allow customization of cursor queries [feat: ratelimit store queries and add options to Next](https://github.com/waku-org/go-waku/pull/1221) - [chat] go-waku: storenode cycle [feat: storenode cycle](https://github.com/waku-org/go-waku/pull/1223) - [chat] status-go: extract storenode cycle to go-waku `api` [feat_: extract storenode cycle to go-waku api](https://github.com/status-im/status-go/pull/5857) - [chat] storenode cycle add tests on go-waku - [Store v3 - store synchronisation](https://github.com/waku-org/pm/issues/132) - achieved: - [research] finish Waku sync 2.0 research issue - [research] Test plan still WIP - [nwaku] [fix: static linking negentropy in ARM based mac](https://github.com/waku-org/nwaku/pull/3046) - [nwaku] [chore: Switch libnegentropy library build from shared to static linkage](https://github.com/waku-org/nwaku/pull/3041) - next: - [research] updates from feedback - [research] Complete test plan and start with basic tests - [DOS protection for req-res protocols and metrics](https://github.com/waku-org/pm/issues/66) - achieved: - [nwaku] [chore: rate limit peer exchange protocol, enhanced response status in RPC](https://github.com/waku-org/nwaku/pull/3035) - [nwaku] [chore: DOS protection of non-relay req/resp protocols new cli argument description](https://github.com/waku-org/docs.waku.org/pull/216) - [nwaku] [chore: Adjusted peer-exchange to the latest changes made due to rate limit DOS protection](https://github.com/waku-org/specs/pull/39) - [nwaku] nwaku is feature ready for `DOS protection for req-res protocols and metrics` - [PostgreSQL Maintenance](https://github.com/waku-org/pm/issues/119) - achieved: - [research] Completed more benchmark testing scenarios - [nwaku] [chore: extending store metrics](https://github.com/waku-org/nwaku/pull/3042) - next: - [nwaku] [chore: store queries for content topics take longer with cursor](https://github.com/waku-org/nwaku/issues/2963) - [research] Write a quick reference summary of test findings - [nwaku] [chore: store queries for content topics take longer with cursor](https://github.com/waku-org/nwaku/issues/2963) ## [Milestone - Static Sharding - dedicated shards](https://github.com/waku-org/pm/milestone/31) - [Sharding peer management and discovery hardening](https://github.com/waku-org/pm/issues/172) - achieved: - [nwaku] [chore: test peer connection management](https://github.com/waku-org/nwaku/pull/3049) - next: - [nwaku] added an abstraction for libp2p to make the code easier to manage in the future. [refactor: peermanager for stale peers management](https://github.com/waku-org/nwaku/pull/3051) ## [Milestone - RLN Mainnet](https://github.com/waku-org/pm/milestone/34) - [RLNv2 in nwaku](https://github.com/waku-org/pm/issues/204) - achieved: - [chat] waku-rlnv2-contract: do not keep track of membership registration order [refactor: do not keep track of membership registration order](https://github.com/waku-org/waku-rlnv2-contract/pull/14) - [Implement RLN smart contract for paid, multilevel memberships](https://github.com/waku-org/pm/issues/228) - achieved: - [research] started review of RLN memberships PR - next: - [research] review / improve the membership PR for RLN on mainnet - Public dogfooding RLNaaS web app - achieved: - [nwaku] [chore: append current version in agentString which is used by the identify protocol](https://github.com/waku-org/nwaku/pull/3057) ## [Milestone - Scale up number of Communities](https://github.com/waku-org/pm/milestone/32) - [Usage of Rendezvous](https://github.com/waku-org/pm/issues/199) - achieved: - [research] nim-libp2p PR update from feedback - next: - [research] more updates on PR and or merge ## [Milestone: Nwaku in Status Desktop](https://github.com/waku-org/pm/milestone/33) - [Nwaku in Status Desktop](https://github.com/waku-org/pm/issues/203) - achieved: - [nwaku] disabled metrics in libwaku until proper support is implemented [chore: disabling metrics for libwaku](https://github.com/waku-org/nwaku/pull/3058) - next: - [nwaku] [feat: nwaku in status-go (discv5 and dnsdiscovery)](https://github.com/waku-org/nwaku/issues/3039) - [Nwaku on Windows](https://github.com/waku-org/pm/issues/239) - next: - [nwaku] Windows support was put on hold due to a recurring error. We'll revisit it after a break. ## [Milestone: Incentivise running a Waku infrastructure node](https://github.com/waku-org/pm/milestone/35) - [Service Incentivisation - Pay for RLN provision PoC](https://github.com/waku-org/pm/issues/245) - achieved: - [research] updated the Vac forum post on service incentivization ## [Milestone: Bandwidth optimization and protocol review](https://github.com/waku-org/pm/milestone/31) - [Status usage of Waku scaling and bandwidth optimization recommendation](https://github.com/waku-org/pm/issues/197) - achieved: - [chat] review and document status community flow [Status Community Flow](https://www.notion.so/Status-Community-Flow-1078f96fb65c80c0877ee3af092f9e80?pvs=25) - [Review usage of content topics in Status Chat and Communities protocol](https://github.com/waku-org/pm/issues/198) - achieved: - [research + chat] forum-post proposal for content-topic usage in status communities [Status Communities : Review and proposed usage of Waku content-topics](https://forum.vac.dev/t/status-communities-review-and-proposed-usage-of-waku-content-topics/) - next: - [research] POC to showcase proposed usage of content-topic in communities ## Bugs and Maintenance - achieved: - [nwaku] [chore: sharding - reduce log level for a too spammy message](https://github.com/waku-org/nwaku/pull/3045) - [nwaku] Release v0.33 preparation and validation - [nwaku] [chore: updating upload and download artifact actions to v4](https://github.com/waku-org/nwaku/pull/3047) - [nwaku] [fix: px protocol decode - do not treat missing response field as error](https://github.com/waku-org/nwaku/pull/3055) - [nwaku] [fix: PeerExchange rpc decode in order not to take response's status_code mandatory - for support old protocol implementation](https://github.com/waku-org/nwaku/pull/3059) - [chat] status-go [fix_: remove unreachable code error message](https://github.com/status-im/status-go/pull/5845) - [chat] go-waku, fix push notifications not working in mobile in develop branch [fix: filter batch duration opt was not propagated correctly](https://github.com/waku-org/go-waku/pull/1224) ### [Milestone: Demonstrate product-market fit](https://github.com/waku-org/pm/milestone/36) - [Define potential USPs](https://github.com/waku-org/pm/issues/249) - achieved: - Franck redone validation matrix and we defined how to approach prospects to validate our USPs - next: - actively seek validation or invalidation of these USPs in next contacts with customers in a structured manner - [Define target customers](https://github.com/waku-org/pm/issues/250) - achieved: - we have gained knowledge since last GTM plan iteration to further specify our target customers and segments - next: - Iterating on GTM plan with new info - blockers: - doing some interviews and validating USPs - [Customer Interviews](https://github.com/waku-org/pm/issues/251) - achieved: - Defined questions and validation Matrix and lined up first couple of leads - blockers: - some of the contacts went to Bali and other places after token2049 and it’s hard to get a hold of them - [Co-design sessions](https://github.com/waku-org/pm/issues/252) - achieved: - A couple projects interested in participating - next: - defining scope of co design with potential partners - blockers: - need more details and conducting some interviews before extending formal invitations ### [Milestone: Acquire first 10 customers](https://github.com/waku-org/pm/milestone/37) - [5-10 Highly qualified leads](https://github.com/waku-org/pm/issues/254) - achieved: - 4 deals in Solution Engineering stage with others joining soon - next: - advancing - blockers: - mostly on customer side apart from some fixes needed in some of our products like js-waku - [Review current integrations](https://github.com/waku-org/pm/issues/255) - achieved: - rounded up deals and logged dependencies in CRM and agreed on roadmap priorities according to existing customers - next: - looking into deals that were lost and figuring out how to revive with new milestones being hit