Shielded by default
zbag defaults to Orchard shielded funds. Sending to a transparent address is a visible exception that requires explicit acknowledgement.
▮ Zcash · Desktop · Self-custody
zbag defaults to the Orchard shielded pool, routes wallet traffic through embedded Tor, and keeps keys in a Rust core. A desktop wallet for macOS, Windows, and Linux, in design preview.
Each line below is something zbag does by design, in plain language. No absolutes, only what the architecture supports.
A Rust core does the sensitive work. The interface works with derived, non-sensitive data, and every automation has a manual lever.
zbag defaults to Orchard shielded funds. Sending to a transparent address is a visible exception that requires explicit acknowledgement.
Routed through an embedded Tor client, no system setup. If Tor is unavailable, zbag does not fall back to a direct lightwalletd connection.
Keystone hardware support over animated QR. Your spending keys can live on a device that never touches the internet, signing with PCZT.
Spending keys never reach the interface. Seed phrases appear only in explicitly permitted flows, not logged or persisted by the UI layer.
Built-in swaps route through NEAR Intents and settle as native ZEC on mainnet. zbag treats swap-related transparent exposure as explicit, not hidden.
A real desktop application, not a browser tab. The dense, deliberate surface privacy work deserves. macOS, Windows, and Linux.
An early design preview of the desktop interface. Balances, addresses, history, and block heights are sample data, shown to illustrate layout rather than real holdings.
Privacy is only real if you can name who is watching and what they get. Here is the read for each observer when a shielded send leaves your machine, and the honest exception when you send to a transparent address.
zbag is not public yet, and what you see here is a design preview. Join the waitlist for early builds, release news, and a heads-up before launch.