Skip to content

Commit 7d2847d

Browse files
jm-cliusjm-clius
authored
docs: add new mix milestone
2 parents 3323b11 + 666a4e4 commit 7d2847d

File tree

3 files changed

+80
-4
lines changed

3 files changed

+80
-4
lines changed

‎FURPS/core/mix.md‎

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,24 @@
33
## Functionality
44

55
1. Relay nodes can mount mixnet protocol, acting as sender, intermediary or exit nodes.
6-
2. Nodes can discover other nodes that support mix using available peer discovery mechanisms
6+
2. Nodes can connect to other nodes that support mix using static configuration.
77
3. Client nodes can send light push requests over the mixnet before delivery to a service node.
88
4. Client nodes can receive a response to a light push request over the mixnet.
9+
5. Nodes can discover other nodes that support mix using available peer discovery mechanisms.
910

1011
## Usability
1112

1213
## Reliability
1314

1415
## Performance
1516

17+
- P1. Payloads are limited to 4kB
18+
1619
## Supportability
1720

1821
1. `wakunode2` for intermediary and exit nodes.
1922
2. nwaku CLI for sender nodes.
23+
3. Browser based apps built using js-waku support acting as entry nodes.
24+
4. Browser based apps built using js-waku support discovering mix nodes using available peer discovery mechanisms.
2025

2126
## + (Privacy, Anonymity, Deployments)

‎draft-roadmap/introduce_mixnet_for_message_sending.md‎

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,9 @@
11
# Introduce Mixnet For Message Sending
22

3-
**Estimated date of completion**: 30 Sep 2025
3+
**Estimated date of completion**: 10 Oct 2025
44

55
**Resources Required for 2025H2**:
6+
67
- 1 core research engineer for 3 months
78

89
A PoC implementation to improve anonymity in Waku message publishing by mixing Waku Lightpush requests and responses.
@@ -18,7 +19,7 @@ See deliverables.
1819
## Risks
1920

2021
| Risk | (Accept, Own, Mitigation) |
21-
|-----------------------------------------|--------------------------------------------------------------------|
22+
| --------------------------------------- | ------------------------------------------------------------------ |
2223
| Dependency on mix library | Strong collaboration, integrate early, get involved behind the API |
2324
| Impact on latency and other UX elements | Run simulations and studies to understand impact |
2425

@@ -31,15 +32,17 @@ See deliverables.
3132
**Feature**: [Mix](/FURPS/core/mix.md)
3233

3334
**FURPS**:
35+
3436
- F1. Relay nodes can mount mixnet protocol, acting as sender, intermediary or exit nodes.
35-
- F2. Nodes can discover other nodes that support mix using available peer discovery mechanisms
37+
- F2. Nodes can connect to other nodes that support mix using static configuration.
3638
- F3. Client nodes can send light push requests over the mixnet before delivery to a service node.
3739
- F4. Client nodes can receive a response to a light push request over the mixnet.
3840

3941
- S1. `wakunode2` for intermediary and exit nodes.
4042
- S2. nwaku CLI for sender nodes.
4143

4244
**Checklist**:
45+
4346
- [ ] Specs: link to specs
4447
- [ ] Code: link to GitHub issues/PRs/Epic
4548
- [ ] Dogfood: link to dogfooding session/artefact

‎draft-roadmap/mixnet_usage_improvements.md‎

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
# Add peer discovery to mixnet and support browser
2+
3+
**Estimated date of completion**: 31 March 2026
4+
5+
**Resources Required for 2025H2**:
6+
7+
- 1 core research engineer for 5 months
8+
9+
Peer discovery for mixnet was descoped from the previous milestones due to upcoming challenges around ENR usage and modification to libp2p needed to support mix peers in rendezvous.
10+
11+
Web apps have been a strong dogfooding and adoption driver for Waku, especially for edge nodes. Adding mix will not only enable wider dogfooding, but also increase anonymity for browser users.
12+
13+
## Strategic Objective
14+
15+
Logos Vision: Core Values Alignment
16+
17+
## FURPS
18+
19+
See deliverables.
20+
21+
## Risks
22+
23+
| Risk | (Accept, Own, Mitigation) |
24+
| --------------------------------------- | ------------------------------------------------------------------ |
25+
| Impact on latency and other UX elements | Run simulations and studies to understand impact |
26+
| Unknowns in implementing js-mix | Further study and understanding of js-libp2p internals |
27+
| Possible `exit==destination` in dependency library impact existing implementation | Frequent syncing with Vac and p2p team to understand impact and progress |
28+
29+
## Deliverables
30+
31+
### [Implement and integrate libp2p mix in js-waku for light push](https://github.com/waku-org/js-waku/issues/2634)
32+
33+
**Owner**: Core Research
34+
35+
**Feature**: [Mix](/FURPS/core/mix.md)
36+
37+
**FURPS**:
38+
39+
- P1. Payloads are limited to 4kB
40+
41+
- S3. Browser based apps built using js-waku support acting as entry nodes.
42+
43+
**Checklist**:
44+
45+
- [ ] Specs: link to specs
46+
- [ ] Code: link to GitHub issues/PRs/Epic
47+
- [ ] Dogfood: link to dogfooding session/artefact
48+
- [ ] Docs: links to README.md or docs.waku.org (TBD)
49+
50+
### [Implement basic discovery for mix]()
51+
52+
**Owner**: Core Research
53+
54+
**Feature**: [Mix](/FURPS/core/mix.md)
55+
56+
**FURPS**:
57+
58+
- F5. Nodes can discover other nodes that support mix using available peer discovery mechanisms.
59+
60+
- S4. Browser based apps built using js-waku support discovering mix nodes using available peer discovery mechanisms.
61+
62+
**Checklist**:
63+
64+
- [ ] Specs: link to specs
65+
- [ ] Code: link to GitHub issues/PRs/Epic
66+
- [ ] Dogfood: link to dogfooding session/artefact
67+
- [ ] Docs: links to README.md or docs.waku.org (TBD)
68+

0 commit comments

Comments
 (0)