NYMM — Mixnet Timing Dossier (clearnet vs mix-fetch for tip/wallet HTTP)

NYMM — Mixnet Timing Dossier (clearnet vs mix-fetch for tip/wallet HTTP)
none 0.0 0

NYMM — Mixnet Timing Dossier

Live: https://nymm.vercel.app
GitHub: GitHub - panagot/nymm: NYMM — Mixnet Timing Dossier. Clearnet vs Nym mix-fetch latency lab for tip and wallet shaped HTTP. · GitHub

A browser lab that sends the same tip- and wallet-shaped HTTP requests over clearnet fetch and through a real @nymproject/mix-fetch tunnel, then plots the difference.

Tip APIs and wallet RPCs on the clearnet bind client IP to endpoint and timing. Hiding an amount on a feed does not hide that adjacency. This lab answers a narrower question: what does a browser mixnet proxy path actually add, in milliseconds, versus the same request in the clear?

What it does

  • Arm a real mix-fetch tunnel (WASM, @nymproject/mix-fetch v2 — not a mocked delay)
  • Paired probes: GET, tip-shaped POST, wallet-RPC-shaped JSON
  • Clearnet vs mixnet: Δ, ratio, P50/P90
  • Charts, session stats, exportable JSON

Echo target is httpbin.org so the demo is self-contained. Cover traffic and Poisson delays are off for the interactive run (documented on Method). First load pulls about 5 MB of WASM.

How to try

  1. Open https://nymm.vercel.app
  2. Arm & run battery
  3. Open Stats → charts → optional Export JSON

Not measured here

Destination-side timing (the exit still delivers a normal HTTP request), cover-traffic overhead, or a real tip/RPC host. Those are natural next steps.

Independent community prototype. Not affiliated with Nym Technologies SA.

Submitted for: Build with Nym (#tools-and-integrations / #build / #dev)

2 Likes