logos-messaging/pm
1
0
Fork 0
mirror of https://github.com/logos-messaging/pm.git synced 2026-01-05 23:53:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

Ivan's feedback

Browse Source
This commit is contained in:
fryorcraken 2025-06-06 11:30:00 +10:00
parent cf356020c3
commit 1556d5238c
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
FURPS/core/rln_smart_contract.md
View File

@ -20,7 +20,7 @@
## Performance
1. New node setup with an RLN membership can be ready to verify RLN proof within 5s,
no matter the size of the tree **(Vac-DST)**.
no matter the size of the membership set **(Vac-DST)**.
## Supportability
@ -28,6 +28,6 @@
## + (Privacy, Anonymity, Deployments)
1. Smart Contracts are deployed on Linea Testnet.
2. TWN uses smart contracts deployed on Linea Testnet.
1. Smart Contracts are deployed on Linea Sepolia.
2. TWN uses smart contracts deployed on Linea Sepolia.

4
FURPS/core/store.md
View File

@ -2,7 +2,7 @@
## Functionality
1. Provides historical message retrieval from the Waku network, enabling nodes to query for messages they missed while offline.
1. Provides historical message retrieval from the relay network, enabling nodes to query for messages they missed while offline.
2. Supports multiple query types: time-based, content-topic filtered, and message hash lookups.
3. Enables message presence verification without retrieving full message content.
4. Supports pagination for efficient retrieval of large message sets, and resuming retrieval after disconnection.
@ -26,7 +26,7 @@
## Performance
1. Only one network round trip is required for operation; including both configuration and message retrieval.
1. Only one network round trip is required for operation.
2. Implements pagination to manage resource usage on both client and server.
3. Allows presence queries to verify message existence without transferring full content.
4. Targets query response times under 2 seconds for typical requests.

4
draft-roadmap/integrate_nwaku_in_status_desktop_relay_mode_only.md
View File

@ -1,9 +1,9 @@
# Integrate nwaku in Status Desktop, relay mode only
**Estimated date of completion**: TODO new date
**Estimated date of completion**: 30 June
**Resources Required for 2025H2**:
- 1 nwaku engineer for 1 month TBC
- 1 nwaku engineer
With this milestone, Status Desktop builds can use nwaku instead of go-waku.
However, it should be seen as a MVP as further hardening and implementation of light client mode will be missing.