update waku weekly update

content/waku/updates/2023-11-06.md

@@ -13,19 +13,19 @@ draft: true
 
 
 - _achieved:_
-  - further PostgreSQL optimisations nearing conclusion
+	- further PostgreSQL optimisations nearing conclusion
-  - implemented bridge to allow Status Community to move to static sharding with backwards compatibility towards default pubsub topic
+	- implemented bridge to allow Status Community to move to static sharding with backwards compatibility towards default pubsub topic
-  - solution for shared bootstrap nodes being filtered out in discv5 as more static shards are activated
+	- solution for shared bootstrap nodes being filtered out in discv5 as more static shards are activated
-  - ensured no unknown blockers from Waku's side to start dogfooding in conversation with Status Communities
+	- ensured no unknown blockers from Waku's side to start dogfooding in conversation with Status Communities
 - _next:_
-  - continue integration of static sharding in status-go.
+	- continue integration of static sharding in status-go.
-  - deploy bridge for backwards compatibility
+	- deploy bridge for backwards compatibility
-  - dogfooding of Status Desktop with Status staging fleet. Will aim to create a small internal Waku community
+	- dogfooding of Status Desktop with Status staging fleet. Will aim to create a small internal Waku community
 - _risks:_
-  - Dependency on Vac/DST to conclude ~1k nodes simulations.
+	- Dependency on Vac/DST to conclude ~1k nodes simulations.
-  - 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.
+	- 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.
-  - lack of confidence in simulation results: results so far exhibits various artifacts and anomalies seemingly related to tooling limitations. It is therefore difficult to draw certain conclusions re Waku scalability.
+	- lack of confidence in simulation results: results so far exhibits various artifacts and anomalies seemingly related to tooling limitations. It is therefore difficult to draw certain conclusions re Waku scalability.
-  - lack of clarity in terms of Status fleet ownership, monitoring and maintenance, which is an integral part of the solution.
+	- lack of clarity in terms of Status fleet ownership, monitoring and maintenance, which is an integral part of the solution.
 
 ### [Targeted dogfooding for Status Communities](https://github.com/waku-org/pm/issues/97)
 
@@ -37,14 +37,14 @@ draft: true
 
 
 - _achieved_:
-  - See 10k milestone update for PostgreSQL status.
+	- See 10k milestone update for PostgreSQL status.
-  - First version of the 10k-tool by DST is ready and is being tested with simulation running a small nim-libp2p/gossipsub binary.
+	- First version of the 10k-tool by DST is ready and is being tested with simulation running a small nim-libp2p/gossipsub binary.
 - _risks_:
-  - Dependency on Vac/DST to run 10k nodes simulations.  Tracked under
+	- Dependency on Vac/DST to run 10k nodes simulations.  Tracked under
-    [`vac:dst:eng-10ktool`](https://roadmap.logos.co/tags/vac-updates).
+	[`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.
+	- 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.
-  - 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.
+	- 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.
-  - lack of real world feedback/dogfooding: the complete static sharding solution involves significant changes to the Waku protocol and tech stack. Although each element is unit tested, dogfooding may hit corner cases in the integrated solution that cannot be foreseen/recreated in lab conditions.
+	- lack of real world feedback/dogfooding: the complete static sharding solution involves significant changes to the Waku protocol and tech stack. Although each element is unit tested, dogfooding may hit corner cases in the integrated solution that cannot be foreseen/recreated in lab conditions.
 
 ### [PostgreSQL in service node: Further optimisations](https://github.com/waku-org/pm/issues/84)
 
@@ -56,21 +56,21 @@ draft: true
 **[nwaku] [PostgreSQL](https://github.com/waku-org/nwaku/issues/1888)**
 
 - _achieved_:
-  - Time processing enhancement when performing _SELECT_ operations. There was an overhead caused by looping too many times over the returned rows, in order to convert the row types. By applying a "rowCallback" approach we can reduce by 30ms the time spent on the query under analysis.
+	- Time processing enhancement when performing _SELECT_ operations. There was an overhead caused by looping too many times over the returned rows, in order to convert the row types. By applying a "rowCallback" approach we can reduce by 30ms the time spent on the query under analysis.
 - _next_:
-  - The queries used in the comparison analysis still perform much better in _SQLite_ (< ~5ms) than in _Postgres_ (< ~15ms.) Therefore we need to push the investigation further to enhance that.
+	- The queries used in the comparison analysis still perform much better in _SQLite_ (< ~5ms) than in _Postgres_ (< ~15ms.) Therefore we need to push the investigation further to enhance that.
-    ( Edited: notice that the timings indicated above are for tests using consecutive queries. If the queries are performed concurrently, then the timings are worse. I will elaborate more in a report shortly .)
+	( Edited: notice that the timings indicated above are for tests using consecutive queries. If the queries are performed concurrently, then the timings are worse. I will elaborate more in a report shortly .)
 
 ## [Waku Network Gen 0](https://github.com/waku-org/pm/issues/50) - 2023-12-01
 
 
 - _achieved_:
-  - Starting internal dogfooding of Waku Network: We have launched the proto-network and it is already possible to run a node in said network.
+	- Starting internal dogfooding of Waku Network: We have launched the proto-network and it is already possible to run a node in said network.
 - _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.
+	- 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.
+	- 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 just joined) so delivery in this client is likely to lag behind other clients.
+	- js-waku team is juggling between dev ex and gen 0 with only 2 engineers (3rd one just joined) so delivery in this client is likely to lag behind other clients.
-  - Uncertainty as to how RLN membership mechanism would hinder application adoption, if memberships need to be distributed or obtained by registration, if staking is necessary to prevent abuse, etc.
+	- Uncertainty as to how RLN membership mechanism would hinder application adoption, if memberships need to be distributed or obtained by registration, if staking is necessary to prevent abuse, etc.
 
 ### [3.2: Basic DoS protection in production](https://github.com/waku-org/pm/issues/70)
 
@@ -90,8 +90,8 @@ draft: true
 
 - _achieved_: PR to support SQLite code to support `messageHash` attribute without interrupting the existing cursor-related functionality, `id` field stays for now. Skelton for sync in progress.
 - _next_:
-    - finalize the SQLite `messageHash` attribute and add a research page about it.
+	- finalize the SQLite `messageHash` attribute and add a research page about it.
-    - start a research page about the sync mechanism for nWaku, doing request/reply a PoC on the same.
+	- start a research page about the sync mechanism for nWaku, doing request/reply a PoC on the same.
 
 ### [2.1: Production testing of existing protocols](https://github.com/waku-org/pm/issues/49)
 
@@ -103,10 +103,10 @@ draft: true
 **[nwaku] [PostgreSQL](https://github.com/waku-org/nwaku/issues/1888)**
 
 - _achieved_:
-  - Time processing enhancement when performing _SELECT_ operations. There was an overhead caused by looping too many times over the returned rows, in order to convert the row types. By applying a "rowCallback" approach we can reduce by 30ms the time spent on the query under analysis.
+	- Time processing enhancement when performing _SELECT_ operations. There was an overhead caused by looping too many times over the returned rows, in order to convert the row types. By applying a "rowCallback" approach we can reduce by 30ms the time spent on the query under analysis.
 - _next_:
-  - The queries used in the comparison analysis still perform much better in _SQLite_ (< ~5ms) than in _Postgres_ (< ~15ms.) Therefore we need to push the investigation further to enhance that.
+	- The queries used in the comparison analysis still perform much better in _SQLite_ (< ~5ms) than in _Postgres_ (< ~15ms.) Therefore we need to push the investigation further to enhance that.
-    ( Edited: notice that the timings indicated above are for tests using consecutive queries. If the queries are performed concurrently, then the timings are worse. I will elaborate more in a report shortly .)
+		( Edited: notice that the timings indicated above are for tests using consecutive queries. If the queries are performed concurrently, then the timings are worse. I will elaborate more in a report shortly .)
 
 ## [Quality Assurance processes are in place](https://github.com/waku-org/pm/issues/73) - 2024-03-31
 
@@ -122,9 +122,23 @@ draft: true
 # Ecosystem Development
 
 - _achieved_:
-  - Multiple leads from ETHLisbon
+	- Multiple leads from ETHLisbon
-  - Sync call with The Graph
+	- Sync call with The Graph
 
 - _next_:
-  - Review RLN docs readiness for launch at Devconnect
+	- Review RLN docs readiness for launch at Devconnect
-  - Web3privacy event preparation
+	- Web3privacy event preparation
+
+- _achieved_:
+	- Multiple leads from ETHLisbon.
+	- Sync call with The Graph.
+	- js-waku prioritising.
+	- Created Hackathon project with Waku at ETHLisbon.
+	- Awesome-waku updates.
+
+- _next_:
+	- Review RLN docs readiness for launch at DevConnect.
+	- Web3privacy event preparation.
+	- Waku network soft-launch organisation.
+	- Creating tutorial videos.
+	- ETHStaker gathering for gaining some awareness about node operator onboarding.