From 6905aa3cdca1d7f760a24ea07e0548bbf6cbdde4 Mon Sep 17 00:00:00 2001 From: fryorcraken Date: Thu, 12 Jun 2025 23:49:23 +1000 Subject: [PATCH] Final review --- 2025H2-summary.md | 13 +++++++------ draft-roadmap/README.md | 10 ++++------ draft-roadmap/integrate_rln_with_waku_api.md | 2 +- 3 files changed, 12 insertions(+), 13 deletions(-) diff --git a/2025H2-summary.md b/2025H2-summary.md index 06426cc..cbfc51f 100644 --- a/2025H2-summary.md +++ b/2025H2-summary.md @@ -5,14 +5,14 @@ - Create Chat SDK MVP - one-to-one (Nim, Rust, Golang), support Status' technical roadmap, supports Logos Movement and Logos Core by enabling secure conversations over Waku - Simplify the API of the Waku SDK (Browser, Nim, Rust, Golang), supports Chat SDK, Logos Movement and Logos Core, make it is easy to integrate - Improve Waku Developer Experience by stabilizing The Waku Network and reviewing Docs: Support Logos Movement, make it is easy to integrate -- Deploy metrics to measure Waku and any Waku app's level of adoption: Support measuring success of Logos Movement +- Deploy metrics to measure Waku and any Waku app's level of adoption: Support measuring success of Logos Technology adoption - Introduce mixnet for message sending: Support Logos Vision of a private technology stack - Formalize and Expand Waku Web Apps: Support Logos Movement on teaching them how to hunt -- Integrate RLN with Waku API: Supports Chat SDK, and Logos Movement to make it easy it to integrate Waku RLN. +- Integrate RLN with Waku API: Supports Chat SDK, and Logos Movement to make it easy it to integrate Waku RLN - Streamline DevEx: Mobile, and Web dev, supporting Status to have nwaku and chat sdk on mobile, provide tooling to make it easy to integrate js-waku - Extend Chat SDK with Group conversations: ditto create chat sdk - Nim Usage Improvement: Dedicate time to improve nim usage (nimble usage, iterate on ffi api, study `nimsuggest` behaviour): to improve nwaku contributor experience, enable all goals above and make it easy to contribute -- Continue Waku Incentivisation: Finish Light push PoC and define next step, to make Waku infrastructure decentralized and sustainable, as per Logos Vision +- Continue Waku Incentivisation: Finish Light push PoC and define next steps, to make Waku infrastructure decentralized and sustainable, as per Logos Vision Strategy changes: @@ -42,8 +42,8 @@ Strategy changes: | [Nim Usage Improvements](draft-roadmap/nim_usage_improvements.md) | Logos Movement Community Enabling: Dev Journey | 0.5 | 5 | FU____ | | [BD - Acquire first 10 customers](draft-roadmap/acquire_first_10_customers.md) | Logos Movement Community Enabling: Growth | 2.1 | 7 | N/A | -✱ Capacity: How may people assigned in a 6 months window. -- 3.5 are applied across all milestones (Franck, Aaron, 1/2 Hanno, Tanya), 1 cc is awol. +✱ Capacity: How many people assigned in a 6 months window. +- 3.5 are applied across all milestones (Franck, Aaron, 1/2 Hanno, Tanya), 1 core research cc is awol. ## 🧩 Strategic Benefits Realisable from coming Half-Year (Top 5) @@ -82,7 +82,8 @@ Strategy changes: https://notes.status.im/E_bcw7cLR36QKI39k-PlMg# -TODO: update +3.5 are applied across all milestones (Franck, Aaron, 1/2 Hanno, Tanya), 1 core research cc is awol. +Not full 6 months planned, see above for contingency. | Strategic Objective | People | |--------------------------------------|--------| diff --git a/draft-roadmap/README.md b/draft-roadmap/README.md index 4b134f9..7a76ccb 100644 --- a/draft-roadmap/README.md +++ b/draft-roadmap/README.md @@ -120,15 +120,13 @@ Note: low allocation on nwaku due to ✱ Capacity: How may people assigned in a 6 months window. Adjusted to 70% allocation for support. - -Pushed to 2026 +Pushed to 2026H1/Next on the list - WebTransport: depending on nim-libp2p (delivery Q4) - Implementing Waku API in REST: Useful for DST/QA, but let's focus on Status, Chat SDK, and Rust first - Delivering NodeJS SDK. - -Not yet planned/not sure: -- nwaku performance on mobile: let's focus on finishing desktop integration and getting API ready for Chat SDK + RLN -- RLN mainnet and audit -> probably wait for Status L2 mainnet + focus on iterations +- nwaku performance on mobile: depending on benchmark results +- New entry points for RLN, in addition to deposit (e.g. Karma holder or SNT staker) +- Message caching/database within Waku SDK ## Gantt diff --git a/draft-roadmap/integrate_rln_with_waku_api.md b/draft-roadmap/integrate_rln_with_waku_api.md index 17bd6ed..cd4eb40 100644 --- a/draft-roadmap/integrate_rln_with_waku_api.md +++ b/draft-roadmap/integrate_rln_with_waku_api.md @@ -4,7 +4,7 @@ **Resources Required for 2025H2**: - 2 nwaku engineer for 2 months -- 1 js-waku engineer for 2 months (til 30 Aug) +- 1 js-waku engineer for 2 months - 1 core research for 1 month - Support from Vac/ACZ to get zerokit working in the browser.