mirror of
https://github.com/logos-messaging/pm.git
synced 2026-01-03 22:53:09 +00:00
Add nwaku in desktop
This commit is contained in:
parent
3134be5d74
commit
377604c43f
25
FURPS/application/nwaku.md
Normal file
25
FURPS/application/nwaku.md
Normal file
@ -0,0 +1,25 @@
|
|||||||
|
# nwaku FURPS
|
||||||
|
|
||||||
|
## Functionality
|
||||||
|
|
||||||
|
1. libwaku can buil don
|
||||||
|
|
||||||
|
## Usability
|
||||||
|
|
||||||
|
1. ...
|
||||||
|
|
||||||
|
## Reliability
|
||||||
|
|
||||||
|
1. ...
|
||||||
|
|
||||||
|
## Performance
|
||||||
|
|
||||||
|
1. ...
|
||||||
|
|
||||||
|
## Supportability
|
||||||
|
|
||||||
|
1. libwaku, wakunode2 can build on Windows
|
||||||
|
|
||||||
|
## + (Privacy, Anonymity, Deployments)
|
||||||
|
|
||||||
|
1. Every nwaku release includes a Windows binary for wakunode2
|
||||||
27
FURPS/application/status_go.md
Normal file
27
FURPS/application/status_go.md
Normal file
@ -0,0 +1,27 @@
|
|||||||
|
# Status-go FURPS
|
||||||
|
|
||||||
|
## Functionality
|
||||||
|
|
||||||
|
1. Nwaku is the used Waku implementation for relay mode.
|
||||||
|
|
||||||
|
## Usability
|
||||||
|
|
||||||
|
1. Status Desktop CI builds with
|
||||||
|
|
||||||
|
## Reliability
|
||||||
|
|
||||||
|
1. status-backend built with nwaku can pass the status-cli tests **(Vac-QA)**.
|
||||||
|
|
||||||
|
## Performance
|
||||||
|
|
||||||
|
1. status-backend built with nwaku has similar performance than go-waku based status-backend within 10% margin,
|
||||||
|
on metrics measured by existing simulations (Vac-DST).
|
||||||
|
|
||||||
|
## Supportability
|
||||||
|
|
||||||
|
1. Status Desktop binary for Linux, Mac and Windows.
|
||||||
|
2. Relay mode is supported; no edge/light mode.
|
||||||
|
|
||||||
|
## + (Privacy, Anonymity, Deployments)
|
||||||
|
|
||||||
|
1. Status Desktop CI builds binaries with nwaku, alongside go-waku-based binaries.
|
||||||
@ -10,9 +10,14 @@ Testing out new format, once approved:
|
|||||||
|
|
||||||
- [Define and Implement Peer-To-Peer Reliability Strategies](./define_p2p_reliability.md)
|
- [Define and Implement Peer-To-Peer Reliability Strategies](./define_p2p_reliability.md)
|
||||||
- [Introduce E2E Reliability in Status Communities](./introduce_e2e_reliability_in_status.md)
|
- [Introduce E2E Reliability in Status Communities](./introduce_e2e_reliability_in_status.md)
|
||||||
|
- Rendezvous TODO? (may be done)
|
||||||
|
- [Deploy RLN onchain tree on L2 testnet](TODO)
|
||||||
|
- [Integrate nwaku in Status Desktop, relay mode only](TODO)
|
||||||
|
|
||||||
#### P2P Reliability Implementation in the Browser
|
#### P2P Reliability Implementation in the Browser
|
||||||
|
|
||||||
|
TODO: It's actually done
|
||||||
|
|
||||||
**Owner**: js-waku
|
**Owner**: js-waku
|
||||||
|
|
||||||
**Feature**: [P2P Reliability](/FURPS/application/p2p_reliability.md)
|
**Feature**: [P2P Reliability](/FURPS/application/p2p_reliability.md)
|
||||||
|
|||||||
@ -18,8 +18,6 @@ Limited effort will be spent on store performance as its relevance is expected t
|
|||||||
|
|
||||||
**Deliverables**:
|
**Deliverables**:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
<!--
|
<!--
|
||||||
Once the deliverables are created as GitHub issues, we can delete the content below
|
Once the deliverables are created as GitHub issues, we can delete the content below
|
||||||
and just provide a list of GitHub issues, or even simpler, a link to the GitHub milestone that contain them.
|
and just provide a list of GitHub issues, or even simpler, a link to the GitHub milestone that contain them.
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user