2023-10-23 Waku weekly

content/waku/updates/2023-10-23.md

@@ -2,7 +2,6 @@
 title: 2023-10-23 Waku weekly
 tags:
   - waku-updates
-  - waku
 date: 2023-10-23
 draft:
 ---
@@ -11,6 +10,14 @@ 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).
+	- Staging fleet for Status with static sharding and PostgreSQL deployed and being tested by go-waku team using local changes in Status Desktop.
+- _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.
+
 ### [Targeted dogfooding for Status Communities](https://github.com/waku-org/pm/issues/97)
 
 
@@ -19,10 +26,26 @@ draft:
 
 ## [Waku Network can Support 1 Million Users](https://github.com/waku-org/pm/issues/83) - 2023-11-30
 
+
+- _achieved_: See 10k milestone update for PostgreSQL status.
+- _risks_:
+	- 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
+
 ## [Waku Network Gen 0](https://github.com/waku-org/pm/issues/50) - 2023-12-01
 
 ### [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)**
+
+- _achieved_: completed flow up items and main stream of work;
+
+**[js-waku-examples] [feat: re-create rln-js](https://github.com/waku-org/js-waku-examples/issues/279)**
+
+- _achieved_: experimented with different frameworks, almost complete rewriting the example;
+
 **[research] [Message propagation times with waku-rln](https://github.com/waku-org/research/issues/42)**
 
 - _achieved_: Ran simulations with 1000 nwaku nodes with rln enabled, with the goal of measuring message propagation delays under different conditions.
@@ -30,6 +53,14 @@ draft:
 
 ### [2.1: Production testing of existing protocols](https://github.com/waku-org/pm/issues/49)
 
+**[js-waku] [chore: improve logging when fails to connect to a node](https://github.com/waku-org/js-waku/issues/1408)**
+
+- _achieved_: setup a Logger for more verbose and modular error readbility
+
+**[js-waku] [Peer Management: Connection and Disconnection](https://github.com/waku-org/js-waku/issues/914)**
+
+- _achieved_: The Connection and Disconnection Peer Management epic has been closed
+
 **[waku-rust-bindings] [feat: filterv2 support](https://github.com/waku-org/waku-rust-bindings/issues/71)**
 
 - _achieved_: added support to waku_filter_subscribe