Nym × Zcash for Ironwood Migration
Welcome — this is the SDK documentation site for wallet integrators. The Ironwood upgrade seals the Orchard pool, and everyone holding shielded ZEC has to migrate through a turnstile that publicly reveals the amount of every migration. The amounts are public by design; the real question is who can tie them back to a person. That’s a network-privacy problem — and it’s exactly what Nym is here to help you solve. Route your wallet’s traffic over Nym and those amounts stop being attributable. The good news: you can build it today. Here’s how.
Where to next
Network privacy analysis
The analysis in full: which Nym configuration protects which invariant, against which adversary, and under which conditions.
★ Recommended architecture
The per-app hybrid we recommend for native wallets, with the operator checklist to build it.
Implementation guidance
The practical how-to for wallet developers: which SDK crate to reach for, how to wire it up, with code.
Threat model
The actors (L1/L2/L3L/L3G), invariants, vectors and countermeasures the rest of the site is threaded through.
Baseline hygiene
Whatever 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.