New: a threat-model-first guide to choosing your network defence, plus the nym-smoldvpn dVPN package and nym-swizzle sender hygiene.
Network
Threat Model
Configurations
Mixnet · rotating exit

Mixnet · rotating exits

⚠️

Per-request exit rotation is not available in the Nym SDKs yet. This configuration is planned for a future release. Until then a mixnet client uses a fixed exit, which behaves like a single exit at the destination.

✅IP hidden · P1@L2✅Req-unlink · P2@L2✅Local net · P1@L3L◐Global net · P1@L3G❌Fast
L2The destination✅P1✅P2

Sees

  • Requests from many exit gateways, with timing delays

Can't see

  • Client IP
  • A complete per-client profile

Residual / countermeasure

  • Fixed exit behaves like dVPN single-exit; rotating exit restores P2. Intersection attacks over long-running sessions remain, and few users per exit shrinks the anonymity set.
L3LLocal network observer✅P1

Sees

  • Constant-size packets at a Poisson rate with cover traffic

Can't see

  • The destination, the volume, or the activity
L3GGlobal network observer◐P1

Sees

  • Per-packet timing (hampered by mixing and cover)

Residual / countermeasure

  • Long bulk flows weaken per-packet correlation resistance (open question).

Pros

  • The destination sees traffic from all Nym exit gateways, not the client

Cons / mitigations

  • Slow (5-hop + mixing delays)

Fit

  • Client identity and IP heavily hidden; not for bulk transfers

Verdicts and the latency implied by the path are an illustrative model, not measured values.

Mixnet · single exitHybrid (recommended)