2025-06-05 15:46:02 +10:00
|
|
|
# Mixnet FURPS
|
|
|
|
|
|
|
|
|
|
## Functionality
|
|
|
|
|
|
2025-06-10 22:23:47 +10:00
|
|
|
1. Relay nodes can mount mixnet protocol, acting as sender, intermediary or exit nodes.
|
|
|
|
|
2. Nodes can discover other nodes that support mix using available peer discovery mechanisms
|
2025-06-05 15:46:02 +10:00
|
|
|
3. Client nodes can send light push requests over the mixnet before delivery to a service node.
|
|
|
|
|
4. Client nodes can receive a response to a light push request over the mixnet.
|
|
|
|
|
|
|
|
|
|
## Usability
|
|
|
|
|
|
|
|
|
|
## Reliability
|
|
|
|
|
|
|
|
|
|
## Performance
|
|
|
|
|
|
2025-09-12 14:44:51 +05:30
|
|
|
- P1. Payload (store query, light push message) are limited to 4kB
|
|
|
|
|
|
2025-06-05 15:46:02 +10:00
|
|
|
## Supportability
|
|
|
|
|
|
2025-06-10 22:23:47 +10:00
|
|
|
1. `wakunode2` for intermediary and exit nodes.
|
|
|
|
|
2. nwaku CLI for sender nodes.
|
2025-09-09 16:53:53 +05:30
|
|
|
3. Browser based apps built using js-waku should support acting as entry nodes.
|
2025-06-05 15:46:02 +10:00
|
|
|
|
|
|
|
|
## + (Privacy, Anonymity, Deployments)
|
