A8
Sphinx-based Mixnets
Routing & Transport Research
Description
A privacy-preserving routing protocol utilizing the Sphinx packet format to construct mixnets. Targeted by the PSE team for integration into Ethereum’s node discovery (discv5) and Private RPCs to provide robust broadcast privacy and metadata protection.
Relationships
| Target | Type | Note |
|---|---|---|
| P3 | benefits | Cryptographically obfuscates the origin IP of discovery and RPC requests. |
| P5 | benefits | Provides strong resistance against Global Passive Adversaries via packet shuffling and uniform sizing. |
| P1 | hurts | Multi-hop routing and intentional mixing delays inherently increase network latency. |
| P2 | hurts | Cryptographic packet framing and mandatory cover traffic significantly increase bandwidth overhead. |
| P7 | hurts | Requires profound changes to the libp2p stack and node discovery mechanisms. |
Open questions
- Can mixnet latency be tuned to support real-time attestation propagation, or is it strictly for less time-sensitive tasks like RPCs and discovery?
- Incentivization and deployment of independent mix node operators.
References
Relationships
| Dir | Target | Type |
|---|---|---|
| → | P3 Identity Unlinkability | benefits |
| → | P5 GPA Resistance | benefits |
| → | P1 Latency Bound | hurts |
| → | P2 Bandwidth Overhead | hurts |
| → | P7 Implementation Complexity | hurts |
| ← | A4 Decoy Traffic Injection | complements |
| ← | A1 ZK Proof of Validator (ZK-PoV) | complements |
| ← | A12 Dandelion++ | complements |