logos-messaging/pm
1
0
Fork 0
mirror of https://github.com/logos-messaging/pm.git synced 2026-01-02 14:13:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Wrap up dates

Browse Source
This commit is contained in:
fryorcraken 2025-06-11 15:24:04 +10:00
parent c051dc973b
commit 5ab882a004
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
16 changed files with 158 additions and 172 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
2025H1-SUMMARY.md
View File

@ -86,13 +86,7 @@
## Funding and Resources
| Name | Amount |
|------------------------|---------------------|
| Headline Budget Ask | k-USD |
| Final Budget Used | k-USD |
| Resource Count Initial | 21 |
| Resource Count Final | 20 |
| Open Positions | 0 (2 backfill lost) |
https://notes.status.im/E_bcw7cLR36QKI39k-PlMg#
## ⚠️ Keys Risks & Controls
@ -111,5 +105,6 @@
- It was too early to formalize integration with Codex. Nonetheless, Waku apps produced by app/chat team have Codex integration and dogfooding of Waku x Codex will continue.
- We attempted to put in place a process with Vac-QA and Vac-DST respectively "certify" `R`s and `P`s. While good on principle, the tracking processes are not there.
- It was a first round of planning with FURPS. Lessons have been learned and being applied for H2.
- The "Waku (Messaging) API" was initially a tidy up, as Waku was already integrated in Status. With a focus towards Chat SDK and growing a developer community, it became an urgent-important item.
- The Waku internal hackathon was a great experiment to identify use-case but also improvements to the Waku dev ex. With a focus on building (developer) tribes, its strategic value has increased.
- Milestones that involved breaking changes were dragged across several Status release; need to review how this is planned to not postponed milestone completion dates by months.
- Some research items took time to wrap-up, sort bindings, etc. Will discuss with the team on how we can be better are getting research PoC ready for dogfooding.

139
2025H2-summary.md
View File

@ -1,5 +1,7 @@
# Milestones Presentation (Half-Year to Dec-2025): Waku
TODO what's up with eco dev grwoth
## 🧭 Key Outcome(s) of Vision you are supporting
- 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
@ -11,8 +13,8 @@
- 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 Incentivization: Finish Light push PoC and define next step, to make Waku infrastructure decentralized and sustainable, as per Logos Vision
- 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
Strategy changes:
@ -24,37 +26,29 @@ Strategy changes:
- Introduced Developer Experience items: to support Chat SDK, and "make it easy to integrate"
- Nim Usage Improvement: increased priority to support new chat sdk, and "make it easy to contribute"
- De-scoped any Communities or existing Status chat protocol work, apart from e2e reliability as it is a re-usable block for Chat SDK.
- RLN Mainnet is a long term goal, focused instead of smaller, achievable items that enable integration and dogfooding of RLN.
- RLN Mainnet is a long term goal, focus instead of smaller, achievable items that enable integration and dogfooding of RLN.
## 🚩 Proposed Milestones(s)
| Milestone Headline | Strategic Objective | Capacity* | Business Val (0/10) | FURPS |
|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------|-----------|---------------------|-------|
| [Define Incentivisation for RLNaaS](draft-roadmap/define_incentivisation_for_rlnaas.md) | Logos Vision: Core Values Alignment | 1.5 | 7 | TODO |
| [Improve DevEx: API, TWN, Metrics, Docs](draft-roadmap/improve_devex_api_twn_metrics_docs.md) | Logos Movement Community Enabling via Dev-X + Telemetry | TODO | 8 | FU__+ |
| [Introduce mixnet for message sending](draft-roadmap/introduce_mixnet_for_message_sending.md) | Logos Vision: Core Values Alignment | 1 | 6 | |
| [Formalize and Expand Waku Web Apps](draft-roadmap/formalize_and_expand_waku_web_apps.md) | Logos Movement Community Enabling | 1.5 | 7 | |
| [Create Chat SDK MVP](draft-roadmap/create_chat_sdk_mvp.md) | Logos Movement Module Build Out | 3 | 9 | |
| [Integrate RLN with Waku API](draft-roadmap/integrate_rln_with_waku_api.md) | Logos Movement Module Build Out | 0.5 | 9 | |
| [Streamline DevEx: Mobile, Rust and Web dev](draft-roadmap/streamline_dev_ex_local_dev_rust.md) | Logos Movement Community Enabling via Dev-X | TBD | 9 | |
| [Extend Chat SDK with Group Conversations](draft-roadmap/extend_chat_sdk_with_group_conversations.md) | Logos Movement Module Build Out | | 9 | |
| Incentivisation follow-up (write outline) | Logos Vision: Core Values Alignment | TBD | 7 | |
| [Nim Usage Improvements](draft-roadmap/nim_usage_improvements.md) | Logos Movement Community Enabling: Dev Journey | | 5 | TBD |
| Milestone Headline | Strategic Objective | Capacity | Business Val (0/10) | FURPS |
|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------|----------|---------------------|-------|
| [Define Incentivisation for RLNaaS](draft-roadmap/define_incentivisation_for_rlnaas.md) | Logos Vision: Core Values Alignment | 0.25 | 7 | TODO |
| [Improve DevEx: API, TWN, Metrics, Docs](draft-roadmap/improve_devex_api_twn_metrics_docs.md) | Logos Movement Community Enabling via Dev-X + Telemetry | 1.5 | 10 | FU__+ |
| [Introduce mixnet for message sending](draft-roadmap/introduce_mixnet_for_message_sending.md) | Logos Vision: Core Values Alignment | 0.33 | 4 | |
| [Formalize and Expand Waku Web Apps](draft-roadmap/formalize_and_expand_waku_web_apps.md) | Logos Movement Community Enabling | 0.25 | 7 | |
| [Create Chat SDK MVP](draft-roadmap/create_chat_sdk_mvp.md) | Logos Movement Module Build Out | 1.5 | 8 | |
| [Integrate RLN with Waku API](draft-roadmap/integrate_rln_with_waku_api.md) | Logos Movement Module Build Out | 0.83 | 9 | |
| [Streamline DevEx: Mobile, Rust and Web dev](draft-roadmap/streamline_dev_ex_local_dev_rust.md) | Logos Movement Community Enabling via Dev-X | 0.5 | 7 | |
| [Extend Chat SDK with Group Conversations](draft-roadmap/extend_chat_sdk_with_group_conversations.md) | Logos Movement Module Build Out | 1 | 8 | |
| Incentivisation follow-up (write outline) | Logos Vision: Core Values Alignment | TBD | 7 | |
| [Nim Usage Improvements](draft-roadmap/nim_usage_improvements.md) | Logos Movement Community Enabling: Dev Journey | 0.33 | 5 | TBD |
| Acquire first 10 customers | Logos Movement Community Enabling: Growth | 1.5 | 6 | N/A |
## 🧩 Strategic Benefits Realisable from coming Half-Year (Top 5)
- **Logos Vision - Core Values Alignment**: Progress on making Waku sustainably scalable, resilient, private and censorship-resistant.
TODO: more like above
Sustainable, scalable, secure and usable Chat protocol: Enables anyone to build private native chat application, and set sustainable foundations for Status application.
- Deliver better APIs and SDKs: Broadens utility of Waku protocol, including RLN, enable building desktop, browser and mobile app using a unified, simple, Waku and RLN API.
- Waku web apps: demonstrate how to build on Waku, and iterate on dev ex and UX of Waku APIs and protocols, including RLN.
- Introduce mixnet: Deliver on our promise of network level anonymity, starting with sender anonymity.
- Improve Nim usage: improve the efficiency of Waku nim developers, to better delivery our commitments and "make it easy to contribute".
- **Logos Vision - Core Values Alignment**: Progress on making Waku sustainably scalable, resilient, private and censorship-resistant. Increase anonymity properties.
- **Logos Movement Community Enabling**: Simplify APIs to reduce cost of onboarding and deliver them in demanded languages, build application as examples and demonstrations of the technology, provide telemetry to track success and improve Dev-X for contributors.
- **Logos Movement Module Build Out**: Deliver a Chat SDK that can scale over Waku, supporting secure one-to-one and group chats, with early integration of DoS protection.
## 🚩 Key Cross Project Alignments (Top-5)
@ -85,17 +79,16 @@ Sustainable, scalable, secure and usable Chat protocol: Enables anyone to build
### Rolled-Up By Strategic Objective
TODO: copy from strategic objectives in milestone table.
https://notes.status.im/E_bcw7cLR36QKI39k-PlMg#
| Strategic Objective | People Costs | Infra Costs | Other Costs |
|-----------------------------------|--------------|-------------|-------------|
| Protocol Enhancement on Waku Chat | 300k | 50k | |
| Enable Logos Vision Chat Protocol | 400k | 10k | |
| Strategic Objective | People |
|--------------------------------------|--------|
| Logos Vision - Core Values Alignment | |
| Logos Movement Community Enabling | |
| Logos Movement Module Build Out | |
### Budget Consultation
TODO
| Headline Activity | Status |
|-------------------------|-----------------------------------|
| Financial Review Status | [new,renew,review,approved] |
@ -103,72 +96,34 @@ TODO
### By Resource
| Resource Headline Item | People | Comment |
|-------------------------|---------|-------------------------------------------------|
| Present Resource | 20 | |
| Additional Resource Ask | 2 | backfills (more to ...TODO strategic objhectve) |
| PeopleOps Informed | Yes | |
| Resource Headline Item | People | Comment |
|-------------------------|--------|----------------------------------------------|
| Present Resource | 20 | |
| Additional Resource Ask | 1 | backfill - Logos Movement Community Enabling |
| PeopleOps Informed | Yes | |
### PeopleOps Consultation
TODO
| Review Status | [new,renew,review,approved]|
| Review Comments | [new,renew,review,approved]|
## ⚠️ Keys Risks Identified & Controls
TODO: big ones
Accept: you accept the risk and it may realize
Own: you spend effort to resolve the risk
Mitigation: you find a way to reduce the risk impact
| Risk | (Accept, Own, Mitigation) |
|--------------------|-----------------------------------------------------|
| [Risk] | [Mitigation strategy] |
| [Risk] | [Mitigation strategy] |
| [Risk] | [Mitigation strategy] |
| Risk | (Accept, Own, Mitigation) |
|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|
| Cryptographic primitives in Nim | Expect to nim-wrap existing Rust/C libraries - will consult with Vac to lean towards libraries already used in Nim/IFT ecosystem. |
| Timeline uncertainties for research items | Focus on iterative delivery of usable deliverables, to get early feedback and direction and lower cost of failure. |
| Nim ecosystem and tooling maturity | New initiative to foster Nim community within IFT, work closely with Vac/Nim re tooling, block time to migrate to Nimble. |
| RLN UX | Integrate in web apps, continue dogfooding and iteration, close collaboration with Status. |
| Readiness of status-go for Chat SDK integration | Weekly sync up on chat sdk and status-go refactoring topics between Waku and Status teams, collaborative planning done to align goals and API. |
## ✅ Key Observations
**[Specific observations from this last execution window]**
TO CLARIFY
Lessons, strategic observations, other improvements.
"Key Improvements"/retrospective.
---
TODO: remove below
## 🛠️ FURPS Reference by Proposed Milestone
TO CLARIFY
| Headline 1 | FURPS Defined | Link |
|-------------------------------|----------------------------|---------------|
| Waku Store database narrative | F2(3) U(1) R (1) P(2) S(0) | link to FURPS |
| RLN standard module 1 | F2(3) U(1) R (1) P(1) S(0) | link to FURPS |
| Chat SDK version 1 | F2(3) U(1) R (0) P(0) S(0) | link to FURPS |
# Appendix A (Optional)
See links in [Proposed Milestones(s)](#-proposed-milestoness)
## FURPS
See links in [Proposed Milestones(s)](#-proposed-milestoness). Each milestone has FURPS
## Risks Identified
TO CLARIFY: is this per milestone?
TO CLARIFY: What does "(Accept, Own, Mitigation)" mean?
| Risk | (Accept, Own, Mitigation) |
|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
| Readiness of status-go for Chat SDK integration | Weekly sync up on chat sdk and status-go refactoring topic between Waku and Status teams, collaborative planning done to align goals and API. |
| [Risk] | [how to we address this risk] |
| [Risk] | [how to we address this risk] |
- Exciting 6 months ahead with clear path on how to deliver value to both Status and the Logos Community with the same effort.
- Improving work tracking with Vac-DST/Vac-QA, discussion is ongoing to better integrate Waku FURPS in Vac planning.
- We know have a breaking change strategy for Status items.
- Aiming more of a team rally behind milestones, dev milestones are now larger and contain more items that can be done in parallel, so that most of the team work on same milestone together.
- Focus on more frequent milestone delivery, by avoiding intra-dependency of items in milestone.
- Increasing collaboration between research and engineering teams, to ensure early unblocking and neat wrap-up of items.
- The "Waku (Messaging) API" was initially a tidy up task, as Waku was already integrated in Status. With a focus towards Chat SDK and growing a developer community, it became an urgent-important item.
- Intent to continue internal hackathon initiative with 2 more occurrences in 2025 (tentatively July and October).

23
FURPS/application/local_dev_rln_harness.md Normal file
View File

@ -0,0 +1,23 @@
# Local Dev RLN Harness FURPS
## Functionality
1. Runs local Ethereum environment.
2. Deploys ERC-20 and RLN smart contract.
3. Utility to fund wallet addresses with necessary tokens for deposit for RLN membership registration.
## Usability
1. Developer only need to run a script to setup local blockchain environment.
2. Developers can run documented RPC calls to fund wallet addresses.
3. Developers can run documented RPC calls to interact with RLN smart contract.
## Reliability
## Performance
## Supportability
1. Linux and Mac development environments.
## + (Privacy, Anonymity, Deployments)

7
FURPS/application/nwaku.md
View File

@ -21,10 +21,13 @@
## Supportability
1. libwaku, wakunode2 can build on Windows
2. libwaku supports relay functionalities.
2. libwaku supports relay node functionalities.
3. TCP transport is supported for peer-to-peer message routing connections.
4. QUIC transport is supported for peer-to-peer message routing connections.
5. libwaku builds on Android and iOS
6. libwaku support edge node functionalities.
## + (Privacy, Anonymity, Deployments)
1. Every nwaku release includes a Windows binary for wakunode2.
1. Every nwaku release includes a Windows binary for wakunode2.

9
FURPS/application/status_go.md
View File

@ -3,6 +3,7 @@
## Functionality
1. Nwaku is the used Waku implementation for relay mode.
2. Nwaku is the used Waku implementation for light mode.
## Usability
@ -20,8 +21,12 @@
## Supportability
1. Status Desktop binary for Linux, Mac and Windows.
2. Relay mode is supported; no edge/light mode.
2. Relay mode is supported.
3. Light mode is supported.
4. Status Mobile binary for Android and iOS.
5. Status Tablet binary for Android and iOS.
## + (Privacy, Anonymity, Deployments)
1. Status Desktop CI builds binaries with nwaku, alongside go-waku-based binaries.
1. Status Desktop CI builds binaries with nwaku, alongside go-waku-based binaries.
2. Status Mobile and Tablet CI builds binaries with nwaku, alongside go-waku-based binaries.

7
FURPS/core/waku_api.md
View File

@ -10,6 +10,8 @@
4. Does automatic peer discovery based on the node platform and operation mode.
5. Returns health and connectivity information using proven heuristics.
6. Previously discovered peers are persisted across restarted, and potentially used for future connections.
7. When wrapping the C API, conversion from native types to JSON is needed by the wrapper.
8. When wrapping the C API, conversion from native types to Protobuf is needed by the wrapper.
## Usability
@ -19,6 +21,7 @@
4. Developers pass and receive data to the API in types native to the wrapping language.
5. By default, auto-sharding is applied, meaning developers do not need to be concerned by sharding; pubsub topics are never exposed.
6. Developers only need to handle errors in cases of irretrievable failure requiring end-user action. Internal errors are not bubbled up if they can be recovered internally.
7. When wrapping the C API, a protobuf definition can be used to generate native types for the host language.
## Reliability
@ -32,7 +35,9 @@
1. Nim library; import via git path.
2. Golang library; available on pkg.go.dev.
3. Browser; distribution via npmjs.com.
4. Rust; available on crates.io.
## + (Privacy, Anonymity, Deployments)
1. ...
1. C API uses JSON format for data passing.
2. C API uses Protobuf format for data passing.

25
draft-roadmap/README.md
View File

@ -89,18 +89,19 @@ In order of priority.
| [Deploy RLN Onchain Tree on L2 Testnet](deploy_rln_onchain_tree_on_l2_testnet.md) | 30 Jun (H1) | | | | |
### H2 Milestones
| Priority | Milestone | End Date | core res | js-waku | nwaku | app-chat |
|----------|-----------------------------------------------------------------------------------------|----------|----------|---------|-------|-------------|
| 1 | [Define Incentivisation for RLNaaS](define_incentivisation_for_rlnaas.md) | 31 Jul | 1.5 | | | |
| 2 | [Improve DevEx: API, TWN, Metrics, Docs](improve_devex_api_twn_metrics_docs.md) | TBD | TBD | TBD | TBD | 0.16.. |
| 3 | [Introduce mixnet for message sending](introduce_mixnet_for_message_sending.md) | 30 Sep | 0.5 | | | |
| 4 | [Formalize and Expand Waku Web Apps](formalize_and_expand_waku_web_apps.md) | 19 Dec | | | | 1.5 |
| 5 | [Create Chat SDK MVP](create_chat_sdk_mvp.md) | 30 Sep | | | | 2 dev/1 res |
| 6 | [Integrate RLN with Waku API](integrate_rln_with_waku_api.md) | TBD | TBD | 1*2m | TBD | |
| 7 | [Streamline DevEx: Mobile, Rust and Web dev](streamline_dev_ex_local_dev_rust.md) | TBD | TBD? | TBD | TBD | |
| 8 | [Extend Chat SDK with Group Conversations](extend_chat_sdk_with_group_conversations.md) | TBD | | | | 1 dev/1 res |
| 9 | Incentivisation follow-up | TBD | TBD | | | |
| 10 | [Nim Usage Improvements](nim_usage_improvements.md) | TBD | | | TBD | |
| Priority | Milestone | End Date | core res | js-waku | nwaku | app-chat |
|----------|-----------------------------------------------------------------------------------------|----------|----------|---------|--------|----------|
| 1 | [Define Incentivisation for RLNaaS](define_incentivisation_for_rlnaas.md) | 31 Jul | 1.5*1m | | | |
| 2 | [Improve DevEx: API, TWN, Metrics, Docs](improve_devex_api_twn_metrics_docs.md) | 31 Aug | 1*1m | 2*2m | 1.5*2m | 1*1m |
| 3 | [Introduce mixnet for message sending](introduce_mixnet_for_message_sending.md) | 30 Sep | 1*3m | | | |
| 4 | [Formalize and Expand Waku Web Apps](formalize_and_expand_waku_web_apps.md) | 19 Dec | | | | 1.5*6m |
| 5 | [Create Chat SDK MVP](create_chat_sdk_mvp.md) | 30 Sep | | | | 3*3m |
| 6 | [Integrate RLN with Waku API](integrate_rln_with_waku_api.md) | 30 Sep | 1*1m | 1*2m | 1*2m | |
| 7 | [Streamline DevEx: Mobile, Rust and Web dev](streamline_dev_ex_local_dev_rust.md) | 30 Nov | | 1*1m | 1*2m | |
| 8 | [Extend Chat SDK with Group Conversations](extend_chat_sdk_with_group_conversations.md) | 19 Dec | | | | 2*3m |
| 9 | Incentivisation follow-up | TBD | TBD | | | |
| 10 | [Nim Usage Improvements](nim_usage_improvements.md) | 19 Dec | | | 1*2m | |
Pushed to 2026
- WebTransport: depending on nim-libp2p (delivery Q4)

2
draft-roadmap/create_chat_sdk_mvp.md
View File

@ -19,7 +19,7 @@ This milestone is complete when a development preview of the Chat SDK is publish
## Strategic Objective
TODO: Clarify with Leonard
Logos Movement Module Build Out
## Risks

4
draft-roadmap/define_incentivisation_for_rlnaas.md
View File

@ -3,7 +3,7 @@
**Estimated date of completion**: 31 July 2025
**Resources Required for 2025H2**:
- 1.5 core researchers for 1 month
- 1.5 core researchers for 1 month = 0.25
By the end of this milestone, we will have defined a roadmap and implemented a working proof of concept to incentivise node operators running Waku infrastructure for shared shards.
@ -17,7 +17,7 @@ This is the first step to providing a sustainable way to scale the Status applic
## Strategic Objective
TODO: Clarify with Leonard
Logos Vision: Core Values Alignment
## FURPS
- [Incentivisation](/FURPS/core/incentivisation.md): F1-3, U1-2, R1-3, P1, for S1

2
draft-roadmap/extend_chat_sdk_with_group_conversations.md
View File

@ -16,7 +16,7 @@ Further group size scaling and extension of membership management API would be n
## Strategic Objective
TODO: Clarify with Leonard
Logos Movement Module Build Out
## FURPS

2
draft-roadmap/formalize_and_expand_waku_web_apps.md
View File

@ -19,7 +19,7 @@ to build over Waku.
## Strategic Objective
TODO: Clarify with Leonard
Logos Movement Community Enabling
## FURPS

25
draft-roadmap/improve_devex_api_twn_metrics_docs.md
View File

@ -1,13 +1,12 @@
# Improve DevEx: API, TWN, Metrics, Docs
**Estimated date of completion**: {Enter date}
- js-waku 31 Aug
**Estimated date of completion**: 31 Aug
**Resources Required for 2025H2**:
- 2 js-waku engineer, 31 Aug
- 1.5 nwaku eng, 31 Aug (API)
- {external services consumed (Vac/IFT)}
- {infrastructure}
- 2 js-waku engineers
- 1.5 nwaku eng
- 1 core research
Proceed with a number of improvements to the developer experience on Waku, for both internal and external purposes.
This includes:
@ -71,20 +70,6 @@ For S2. For Web apps as a developer library.
- [ ] Dogfood: link to dogfooding session/artefact
- [ ] Docs: links to README.md or docs.waku.org (TBD)
### [Waku Sync](https://github.com/waku-org/pm/issues/132)
**Owner**: core research
**Feature**: [Store Sync](/FURPS/core/store_sync.md)
**FURPS**: all
**Checklist**:
- [ ] Specs: link to specs and/or API definition
- [ ] Code: link to GitHub issues/PRs/Epic
- [ ] Dogfood: link to dogfooding session/artefact
- [ ] Docs: links to README.md or docs.waku.org (TBD)
### Implement Light Push Error codes in The Browser
**Owner**: js-waku

11
draft-roadmap/integrate_rln_with_waku_api.md
View File

@ -5,8 +5,7 @@
**Resources Required for 2025H2**:
- 1 nwaku engineer for 2 months
- 1 js-waku engineer for 2 months (til 30 Aug)
- core research/test engineer? TODO
- chat sdk engineer TODO
- 1 core research for 1 month (assuming ownership of RLN UX deliverable)
- Support from Vac/ACZ to get zerokit working in the browser.
- {infrastructure}
@ -21,6 +20,10 @@ Introduce RLN proof generation and validation in the Browser. RLN API should be
Finally, migrate to Status network L2 testnet and improve UX issues discovered via dogfooding such as rate of RPC Calls.
## Strategic Objective
Logos Movement Module Build Out
## FURPS
TODO
@ -131,9 +134,9 @@ TODO
### Improve RLN UX by reducing Web3 RPC calls
TODO: other improvements may be flagged as we dogfood the previous RLN milestone.
TODO: Clarify ownership
**Owner**: nwaku
**Owner**: nwaku or core research
**Feature**: [{Feature Name (only 1)}]({path/to/furps/file})

2
draft-roadmap/introduce_mixnet_for_message_sending.md
View File

@ -9,7 +9,7 @@ A PoC implementation to improve anonymity in Waku message publishing by mixing W
## Strategic Objective
TODO: Clarify with Leonard
Logos Vision: Core Values Alignment
## FURPS

17
draft-roadmap/nim_usage_improvements.md
View File

@ -1,18 +1,17 @@
# Upgrade Nim Usage
**Estimated date of completion**: {Enter date}
**Estimated date of completion**: 19 Dec
**Resources Required for 2025H2**:
- {roles and % application to it}
- {external services consumed (Vac/IFT)}
- {infrastructure}
- 1 nwaku eng for 2 months
- Support from Vac/Nim team
Improve usage of Nim related tooling and design patterns by proceedings with PoCs to discover potential gains and caveats.
This includes adoption of Nimble, dogfooding VSCode plugin and iteration on C-Binding methodology.
## Strategic Objective
TODO: Clarify with Leonard
Logos Movement Community Enabling: Dev Journey
## FURPS
@ -58,14 +57,16 @@ Note: maybe taken over by Vac-Nim
- [ ] Optional: provide a plan to make nwaku better compatible with nimsuggest (eg. no git submodule, less macros, etc)
### Use Protobuf to transfer data from Wrapper to nwaku library PoC
### Streamline FFI API Creation by using Protobuf types instead of JSON PoC
**Owner**: nwaku
**Feature**: TODO
**Feature**: [Waku API](/FURPS/core/waku_api.md)
**FURPS**:
- {F1. copy-paste full furps statement}
- F8. When wrapping the C API, conversion from native types to Protobuf is needed by the wrapper.
- U7. When wrapping the C API, a protobuf definition can be used to generate native types for the host language.
**Checklist**:
- [ ] Specs: link to specs and/or API definition

44
draft-roadmap/streamline_dev_ex_local_dev_rust.md
View File

@ -1,9 +1,8 @@
# Streamline DevEx: Mobile, Rust and Web dev
**Estimated date of completion**: {Enter date} TODO
**Estimated date of completion**: 30 Nov
**Resources Required for 2025H2**:
- {roles and % application to it}
- nwaku 1 eng during 1 month 70% until 30 Sep - start 1st Sep
- js-waku 1 eng 70% 1-19th Sep
- {external services consumed (Vac/IFT)}
@ -19,7 +18,7 @@ Finalize the integration of nwaku in Status application by setting up nwaku-base
## Strategic Objective
TODO: Clarify with Leonard
Logos Movement Community Enabling via Dev-X
## FURPS
@ -39,25 +38,35 @@ TODO
**Owner**: nwaku
**Feature**: [{Feature Name (only 1)}]({path/to/furps/file}) TODO
#### **Feature**: [status-go](/FURPS/application/status_go.md)
**FURPS**:
- {F1. copy-paste full furps statement}
- F2. Nwaku is the used Waku implementation for light mode.
- S3. Light mode is supported.
#### **Feature**: [nwaku](/FURPS/application/nwaku.md)
**FURPS**:
- S6. libwaku support edge node functionalities.
**Checklist**:
- [ ] Specs: link to specs and/or API definition
- [ ] Code: link to GitHub issues/PRs/Epic
- [ ] Dogfood: link to dogfooding session/artefact
- [ ] Docs: links to README.md or docs.waku.org (TBD)
TBD
### Nwaku in Status Mobile
**Owner**: nwaku
**Feature**: [{Feature Name (only 1)}]({path/to/furps/file}) TODO
**Feature**: [status-go](/FURPS/application/status_go.md)
**FURPS**:
- {F1. copy-paste full furps statement}
- S4. Status Mobile binary for Android and iOS.
- S5. Status Tablet binary for Android and iOS.
- +2. Status Mobile and Tablet CI builds binaries with nwaku, alongside go-waku-based binaries.
**Checklist**:
- [ ] Specs: link to specs and/or API definition
@ -69,10 +78,10 @@ TODO
**Owner**: nwaku
**Feature**: [{Feature Name (only 1)}]({path/to/furps/file}) TODO
**Feature**: [Waku API](/FURPS/core/waku_api.md)
**FURPS**:
- {F1. copy-paste full furps statement}
- S4. Rust; available on crates.io.
**Checklist**:
- [ ] Specs: link to specs and/or API definition
@ -82,11 +91,6 @@ TODO
### Local Web Dev Harness
TODO: update milestone
1 js-waku engineer, 70% cap allocated;
start 1st Sep, end 19th Sep;
**Owner**: js-waku
**Feature**: [Local Web Dev Harness](/FURPS/application/local_web_dev_harness.md)
@ -110,14 +114,20 @@ start 1st Sep, end 19th Sep;
- [ ] Dogfood: link to dogfooding session/artefact
- [ ] Docs: links to README.md or docs.waku.org (TBD)
### Local RLN Dev Harness
### Local Dev RLN Harness
**Owner**: nwaku
**Feature**: [{Feature Name (only 1)}]({path/to/furps/file})
**Feature**: [Local Dev RLN Harness](/FURPS/application/local_dev_rln_harness.md)
**FURPS**:
- {F1. copy-paste full furps statement}
- F1. Runs local Ethereum environment.
- F2. Deploys ERC-20 and RLN smart contract.
- F3. Utility to fund wallet addresses with necessary tokens for deposit for RLN membership registration.
- U1. Developer only need to run a script to setup local blockchain environment.
- U2. Developers can run documented RPC calls to fund wallet addresses.
- U3. Developers can run documented RPC calls to interact with RLN smart contract.
**Checklist**:
- [ ] Specs: link to specs and/or API definition