waku weekly

content/roadmap/waku/updates/2023-08-06.md

@@ -0,0 +1,120 @@
+---
+title: "2023-08-06 Waku weekly"
+tags:
+  - "waku-updates"
+date: 2023-08-08
+lastmod: 2023-08-08
+draft: false
+---
+
+Milestones for current works are created and used. Next steps are:
+1) Refine scope of [research work](https://github.com/waku-org/research/issues/3) for rest of the year and create matching milestones for research and waku clients
+2) Review work not coming from research and setting dates
+Note that format matches the Notion page but can be changed easily as it's scripted
+
+
+## nwaku
+
+**[Release Process Improvements](https://github.com/waku-org/nwaku/issues/1889)** {E:2023-qa}
+
+- _achieved_: fixed a bug in release CI workflow, enhanced the CI workflow to build and push a docker image on each PR to make simulations per PR more feasible
+- _next_: document how to run PR built images in waku-simulator, adding Linux arm64 binaries and images
+- _blocker_: 
+
+**[PostgreSQL](https://github.com/waku-org/nwaku/issues/1888)** {E:2023-10k-users}
+
+- _achieved_: Docker compose with `nwaku` + `postgres` + `prometheus` + `grafana` + `postgres_exporter` https://github.com/alrevuelta/nwaku-compose/pull/3
+- _next_: Carry on with stress testing
+
+**[Autosharding v1](https://github.com/waku-org/nwaku/issues/1846)** {E:2023-1mil-users}
+
+- _achieved_: feedback/update cycles for FILTER & LIGHTPUSH
+- _next_: New fleet, updating ENR from live subscriptions and merging
+- _blocker_: Architecturally it seams difficult to send the info to Discv5 from JSONRPC for the Waku app.
+
+**[Move Waku v1 and Waku-Bridge to new repos](https://github.com/waku-org/nwaku/issues/1767)** {E:2023-qa}
+
+- _achieved_: Removed v1 and wakubridge code from nwaku repo
+- _next_: Remove references to `v2` from nwaku directory structure and documents
+
+**[nwaku c-bindings](https://github.com/waku-org/nwaku/issues/1332)** {E:2023-many-platforms}
+
+- _achieved_:
+  - Moved the Waku execution into a secondary working thread. Essential for NodeJs.
+  - Adapted the NodeJs example to use the `libwaku` with the working-thread approach. The example had been receiving relay messages during a weekend. The memory was stable without crashing. 
+- _next_: start applying the thread-safety recommendations https://github.com/waku-org/nwaku/issues/1878
+
+**[HTTP REST API: Store, Filter, Lightpush, Admin and Private APIs](https://github.com/waku-org/nwaku/issues/1076)** {E:2023-many-platforms}
+
+- _achieved_: Legacy Filter - v1 - interface Rest Api support added.
+- _next_: Extend Rest Api interface for new v2 filter. Get v2 filter service supported from node.
+
+---
+## js-waku
+
+**[Peer Exchange is supported and used by default](https://github.com/waku-org/js-waku/issues/1429)** {E:2023-light-protocols}
+
+- _achieved_: robustness around peer-exchange, and highlight discovery vs connections for PX on the web-chat example
+- _next_: saving successfully connected PX peers to local storage for easier connections on reload
+
+**[Waku Relay scalability in the Browser](https://github.com/waku-org/js-waku/issues/905)** {NO EPIC}
+
+- _achieved_: draft of direct browser-browser RTC example https://github.com/waku-org/js-waku-examples/pull/260 
+- _next_: improve the example (connection re-usage), work on contentTopic based RTC example
+
+---
+## go-waku
+
+**[C-Bindings Improvement: Callbacks and Duplications](https://github.com/waku-org/go-waku/issues/629)** {E:2023-many-platforms}
+
+- _achieved_: updated c-bindings to use callbacks
+- _next_: refactor v1 encoding functions and update RFC
+
+**[Improve Test Coverage](https://github.com/waku-org/go-waku/issues/620)** {E:2023-qa}
+
+- _achieved_: Enabled -race flag and ran all unit tests to identify data races.
+- _next_: Fix issues reported by the data race detector tool
+
+**[RLN: Post-Testnet3 Improvements](https://github.com/waku-org/go-waku/issues/605)** {E:2023-rln}
+
+- _achieved_: use zerokit batch insert/delete for members, exposed function to retrieve data from merkle tree, modified zerokit and go-zerokit-rln to pass merkle tree persistance configuration settings
+- _next_: resume onchain sync from persisted tree db
+
+**[Introduce Peer Management](https://github.com/waku-org/go-waku/issues/594)** {E:2023-peer-mgmt}
+
+- _achieved_: Basic peer management to ensure standard in/out ratio for relay peers.
+- _next_:  add service slots to peer manager
+
+---
+## Eco Dev
+
+**[Aug 2023](https://github.com/waku-org/internal-waku-outreach/issues/103)** {E:2023-eco-growth}
+
+- _achieved_: production of swags and marketing collaterals for web3conf completed
+- _next_: web3conf talk and side event production. various calls with commshub for preparing marketing collaterals.
+
+---
+## Docs
+
+**[Advanced docs for js-waku](https://github.com/waku-org/docs.waku.org/issues/104)** {E:2023-eco-growth}
+
+- _next_: create guide on `@waku/react` and debugging js-waku web apps
+
+**[Docs general improvement/incorporating feedback (2023)](https://github.com/waku-org/docs.waku.org/issues/102)** {E:2023-eco-growth}
+
+- _achieved_: rewrote the docs in UK English
+- _next_: update docs terms, announce js-waku docs
+
+**[Foundation of js-waku docs](https://github.com/waku-org/docs.waku.org/issues/101)** {E:2023-eco-growth}
+
+_achieved_: added guide on js-waku bootstrapping
+
+---
+## Research
+
+**[1.1 Network requirements and task breakdown](https://github.com/waku-org/research/issues/6)** {E:2023-1mil-users}
+
+- _achieved_: Setup project management tools; determined number of shards to 8; some conversations on RLN memberships
+- _next_: Breakdown and assign tasks under each milestone for the 1 million users/public Waku Network epic.
+
+---