mirror of
https://github.com/logos-messaging/pm.git
synced 2026-01-03 06:33:11 +00:00
Merge 2ce478b0159f4eb95750a2a572ede8a5fddd1067 into 3323b11517e2816c46b9b79f9042aea8a1a9193c
This commit is contained in:
commit
f5973874b5
@ -13,9 +13,12 @@
|
||||
|
||||
## Performance
|
||||
|
||||
- P1. Payload (store query, light push message) are limited to 4kB
|
||||
|
||||
## Supportability
|
||||
|
||||
1. `wakunode2` for intermediary and exit nodes.
|
||||
2. nwaku CLI for sender nodes.
|
||||
3. Browser based apps built using js-waku should support acting as entry nodes.
|
||||
|
||||
## + (Privacy, Anonymity, Deployments)
|
||||
|
||||
@ -1,9 +1,11 @@
|
||||
# Introduce Mixnet For Message Sending
|
||||
|
||||
**Estimated date of completion**: 30 Sep 2025
|
||||
**Estimated date of completion**: TBD(As it requires further study and analysis to determine estimate of new changes)
|
||||
|
||||
**Resources Required for 2025H2**:
|
||||
|
||||
- 1 core research engineer for 3 months
|
||||
- TBD (Would depend on who owns js implementation)
|
||||
|
||||
A PoC implementation to improve anonymity in Waku message publishing by mixing Waku Lightpush requests and responses.
|
||||
|
||||
@ -18,9 +20,10 @@ See deliverables.
|
||||
## Risks
|
||||
|
||||
| Risk | (Accept, Own, Mitigation) |
|
||||
|-----------------------------------------|--------------------------------------------------------------------|
|
||||
| --------------------------------------- | ------------------------------------------------------------------ |
|
||||
| Dependency on mix library | Strong collaboration, integrate early, get involved behind the API |
|
||||
| Impact on latency and other UX elements | Run simulations and studies to understand impact |
|
||||
| Unknowns on implementing js-mix | Further study and understanding of js-libp2p internals |
|
||||
|
||||
## Deliverables
|
||||
|
||||
@ -31,6 +34,7 @@ See deliverables.
|
||||
**Feature**: [Mix](/FURPS/core/mix.md)
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- F1. Relay nodes can mount mixnet protocol, acting as sender, intermediary or exit nodes.
|
||||
- F2. Nodes can discover other nodes that support mix using available peer discovery mechanisms
|
||||
- F3. Client nodes can send light push requests over the mixnet before delivery to a service node.
|
||||
@ -40,6 +44,26 @@ See deliverables.
|
||||
- S2. nwaku CLI for sender nodes.
|
||||
|
||||
**Checklist**:
|
||||
|
||||
- [ ] Specs: link to specs
|
||||
- [ ] Code: link to GitHub issues/PRs/Epic
|
||||
- [ ] Dogfood: link to dogfooding session/artefact
|
||||
- [ ] Docs: links to README.md or docs.waku.org (TBD)
|
||||
|
||||
### [Implement and integrate libp2p mix in js-waku for light push](https://github.com/waku-org/js-waku/issues/2634)
|
||||
|
||||
**Owner**: TBD
|
||||
|
||||
**Feature**: [Mix](/FURPS/core/mix.md)
|
||||
|
||||
**FURPS**:
|
||||
|
||||
- P1. Payload (store query, light push message) are limited to 4kB
|
||||
|
||||
- S3. Browser-based apps as sender nodes; light push only.
|
||||
|
||||
**Checklist**:
|
||||
|
||||
- [ ] Specs: link to specs
|
||||
- [ ] Code: link to GitHub issues/PRs/Epic
|
||||
- [ ] Dogfood: link to dogfooding session/artefact
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user