Skip to content

Commit e6ad8e2

Browse files
committed
Reduce and simplify key outcomes
1 parent 58cc76f commit e6ad8e2

File tree

1 file changed

+5
-11
lines changed

1 file changed

+5
-11
lines changed

2025H2-SUMMARY.md

Lines changed: 5 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,11 @@
22

33
## 🧭 Key Outcome(s) of Vision you are supporting
44

5-
- 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
6-
- 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
7-
- Improve Waku Developer Experience by stabilizing The Waku Network and reviewing Docs: Support Logos Movement, make it is easy to integrate
8-
- Deploy metrics to measure Waku and any Waku app's level of adoption: Support measuring success of Logos Technology adoption
9-
- Introduce mixnet for message sending: Support Logos Vision of a private technology stack
10-
- Formalize and Expand Waku Web Apps: Support Logos Movement on teaching them how to hunt
11-
- Integrate RLN with Waku API: Supports Chat SDK, and Logos Movement to make it easy it to integrate Waku RLN
12-
- 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
13-
- Extend Chat SDK with Group conversations: ditto create chat sdk
14-
- 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
15-
- Continue Waku Incentivisation: Finish Light push PoC and define next steps, to make Waku infrastructure decentralized and sustainable, as per Logos Vision
5+
- Developers can use a Chat SDK to enable secure conversations, for one-to-one chat and private groups, that scales over Waku, including RLN.
6+
- Onboarding on Waku is improved by simplifying the API of the Waku SDK, including RLN, as well as other developer experience improvements.
7+
- Several applications PoC are built over Waku to demonstrate how to use Waku to developers.
8+
- Progress on privacy and sustainability tracks with research on mixnet and incentivisation.
9+
- Deliver nwaku in mobile as the last step to deprecating go-waku.
1610

1711
Strategy changes:
1812

0 commit comments

Comments
 (0)