Nym dVPN — 2-hop, multiple exits
Distinct WireGuard peers registered at several exits split the sync and broadcasts across exit IPs. Given per-request rotation this restores request-request unlinkability at the destination. Fast, but no mixing — network-observer exposure is unchanged.
dVPN (WireGuard)
One client connected to one entry gateway; batches take dVPN routes to different exit gateways, all reaching a single lightwalletd. Most traffic is downloads (blocks: lightwalletd → exit → entry → client) with some uploads (client → entry → exit → lightwalletd).
ClientEntry GWExit GWlightwalletd
dVPN (WireGuard) (no mixing)
Per-actor assessment & trade-offs
Latency model
Exit A · dVPN (WireGuard)360 ms (3 hops)
Exit B · dVPN (WireGuard)360 ms (3 hops)
Exit C · dVPN (WireGuard)360 ms (3 hops)
Geographic propagation (speed-of-light)
Baseline hygiene applies here tooWhatever the transport, the wallet still owes the same Layer-2 discipline: randomize request times, obfuscate the start height, and never broadcast on reaching the tip.Full detail →
Content from the Nym × Zcash reference doc. Latency figures are an illustrative model (not measured).