From 7165d6dc187ae94a73505c6ee5cffedd8114e562 Mon Sep 17 00:00:00 2001 From: "fryorcraken.eth" Date: Tue, 24 Oct 2023 15:57:55 +1100 Subject: [PATCH] 2023-10-23 Waku weekly --- content/waku/updates/2023-10-23.md | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/content/waku/updates/2023-10-23.md b/content/waku/updates/2023-10-23.md index 710612b13..95844ac24 100644 --- a/content/waku/updates/2023-10-23.md +++ b/content/waku/updates/2023-10-23.md @@ -10,13 +10,17 @@ draft: ## [Waku Network Can Support 10K Users](https://github.com/waku-org/pm/issues/12) + - _achieved_: - - Vac/DST team has done further runs with up to 600 nodes in the network as part of wrapping up a [blog post report](https://github.com/vacp2p/vac.dev/pull/123). Clarification around bandwidth usage by Discv5 are being [reviewed](https://github.com/vacp2p/vac.dev/pull/123#discussion_r1366458316). + - Vac/DST team has done further runs with up to 600 nodes in the network as part of wrapping up a [blog post report](https://github.com/vacp2p/vac.dev/pull/123). - Staging fleet for Status with static sharding and PostgreSQL deployed and being tested by go-waku team using local changes in Status Desktop. +- _next_: + - Dogfooding of Status Desktop with Status staging fleet. Will aim to create a small internal Waku community. + - Continue integration of static sharding in status-go. - _risks_: - Dependency on Vac/DST to conclude ~1k nodes simulations. - PostgreSQL implementation has not yet been proven more performant than SQLite. Further improvements and testing in progress. - - Implementation of static sharding in Status Communities and design decisions mostly driven by go-waku developer. See [status-go#4057](https://github.com/status-im/status-go/issues/4057). Mitigation by on-boarding Chat SDK lead on 6 Nov to drive effort. + - Implementation of static sharding in Status Communities and design decisions mostly driven by go-waku developer, with minimal input from Status dev ([1](https://github.com/status-im/status-go/pull/4161), [2](https://github.com/status-im/status-go/pull/4094), [3](https://github.com/status-im/status-go/pull/4093)). See [status-go#4057](https://github.com/status-im/status-go/issues/4057) for remaining work. Mitigation by on-boarding Chat SDK lead on 6 Nov to drive effort. ### [Targeted dogfooding for Status Communities](https://github.com/waku-org/pm/issues/97) @@ -32,10 +36,19 @@ draft: - Dependency on Vac/DST to run 10k nodes simulations. Tracked under [`vac:dst:eng-10ktool`](https://roadmap.logos.co/tags/vac-updates). - Wakutorsis tool is being dropped, meaning new tooling needs to be developed for 10k nodes simulations. It is currently uncertain whether such tool can be developed. - - Dogfooding of Waku v2 static sharding TODO + - Large scale simulations done by Vac/DST only covered nwaku relay. go-waku, status-go simulations are not planned short term (theoretical review of Status Communities messages is), nor are simulations including request-response protocols such as store and filter. ## [Waku Network Gen 0](https://github.com/waku-org/pm/issues/50) - 2023-12-01 + +- _achieved_: + - Critical path work for autosharding done in nwaku, in progress on go-waku + - Parameters for the Waku Network Gen 0 have been captured in an [RFC](https://rfc.vac.dev/spec/64/) and use as a basis for [simulations](https://github.com/waku-org/research/issues/23) and [theoretical analysis](https://github.com/waku-org/research/issues/31), removing uncertainty on this milestone around message rates, performance and expected bandwidth usage. +- _risks_: + - Usage of RLN in js-waku and dependency on a (centralized?) Web3Provider remains unclear as one needs to know the merkle tree state (on chain) to generate proofs. + - We are progressively moving a nwaku engineer to a solution engineer role we need to backfill the role. + - js-waku team is juggling between dev ex and gen 0 with only 2 engineers (3rd one joining at end of Oct) so delivery in this client is likely to lag behind other clients. + ### [3.2: Basic DoS protection in production](https://github.com/waku-org/pm/issues/70) **[js-waku] [Task: Manage RLN membership(s) and keys](https://github.com/waku-org/js-waku/issues/1600)** @@ -68,6 +81,9 @@ draft: ## [Quality Assurance processes are in place](https://github.com/waku-org/pm/issues/73) - 2024-03-31 + +This work is tracked with [vac:dst:software-testingwaku](https://roadmap.logos.co/vac/dst/#software-testingwaku) + ## [Support Many Platforms](https://github.com/waku-org/pm/issues/42) - 2024-04-30 ### [Ship RLN as part of non-native SDKs](https://github.com/waku-org/pm/issues/88)