Mix FURPS

Functionality

  1. Nodes can mixify individual libp2p protocol messages for anonymous routing over a libp2p mixnet
  2. Nodes can mixify libp2p request-response interactions for anonymous routing over a libp2p mixnet
  3. The libp2p mixnet is protected against trivial DoS attacks
  4. The libp2p mixnet is protected against a 50% + 1 Sybil attack
  5. Nodes can discover other nodes that support mix using available peer discovery mechanisms
  6. Exit nodes are protected against trivial abuse/overuse from a single user
  7. The libp2p mixnet is protected against more sophisticated DoS attacks, e.g. coordinated DoS against intermediate nodes
  8. An application-level mechanism exists to segment large messages and mixify over multiple paths
  9. An application-level mechanism exists to segment large responses and coordinating multiple-SURB response paths
  10. Nodes can generate cover traffic to increase K-anonymity in the mixnet
  11. Providers can anonymously register as a hidden service
  12. Clients can discover and anonymously access hidden services
  13. The libp2p mix protocol’s payload encryption preserves payload integrity
  14. A standalone Logos Mix module encapsulates the Logos libp2p module with nim-libp2p-mix, RLN-based DoS protection, and cover traffic for Logos Core services
  15. Applications can route libp2p request-response messages over mix via the Logos Mix module API
  16. Mix nodes maintain a local reputation record for peers
  17. Nodes generate cover traffic at a Poisson rate rather than a constant rate so that cover and real traffic are indistinguishable in timing
  18. Nodes select mix paths according to the anonymity and communication requirements of each message or session
  19. Nodes monitor the health of their mix node pool using loop cover traffic and exclude nodes that appear not to forward traffic from path selection
  20. Mix nodes rotate their keys so that compromise of a current key does not reveal previously routed traffic
  21. A single Logos Mix module can operate as an intermediate mix node, an entry node, or an exit node
  22. Logos Delivery routes Lightpush over Mix through the Logos Mix module acting as entry and exit node

Usability

  1. The libp2p mix protocol and pluggable DoS and Sybil protection is published in specifications
  2. The libp2p mix protocol with DoS and Sybil protection is integrated in nim-libp2p
  3. The libp2p mix protocol with DoS and Sybil protection is integrated into Waku Lightpush protocol as reference integration
  4. A libp2p module with mix capability is integrated into Logos Core
  5. A Logos Core demo chat app showcases message publishing over libp2p mix
  6. The Logos Core demo chat app discovers mix nodes using libp2p kad-dht discovery with filtering
  7. Extended DoS and exit node abuse prevention mechanisms are published in a specification
  8. The application-level mechanism to support large messages (requests & responses) is published in a specification
  9. Cover traffic generation is published in a specification
  10. The protocol allowing hidden service provisioning, discovery and access is published in a specification
  11. A DHT query can be mixified
  12. The libp2p mix protocol is integrated into the Logos Mix Demo Chat module
  13. The Sphinx payload encryption scheme providing payload integrity is published as a specification
  14. The libp2p mix protocol is integrated into the Logos Delivery module with exposure on the Messaging API
  15. The Logos Chat module provides a user interface to select mix when publishing messages
  16. The Logos Mix module API for routing messages over mix is published as a specification
  17. The anonymity limitations of the mix hidden services approach and alternative provider anonymity techniques are evaluated and published
  18. Differentiated RLN rate-limiting based on peer reputation metrics is researched and published
  19. Non-RLN DoS and Sybil protection approaches are researched and published
  20. Poisson-rate cover traffic generation is published in a specification
  21. The opinionated protocol stack composition and configuration for a Logos Mix Network is specified
  22. The local reputation mechanism for mix nodes is published in a specification
  23. Path selection with pool health monitoring is published in a specification
  24. Basic mix key rotation for forward secrecy is published in a specification

Reliability

Performance

Supportability

  1. Mix, mix RLN DoS protection and mix node discovery are provided to Logos Delivery by the Logos Mix module rather than by implementations integrated into Logos Delivery