Zcash · Desktop · Self-custody

A Zcash wallet
that keeps quiet.

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.

Early access by waitlist
Design preview with sample data: a zbag privacy caveats panel that lists each caveat as text, with no balances shown.
Design preview. zbag shows each privacy caveat as text, not color alone. Sample data.

Privacy, stated plainly.

Each line below is something zbag does by design, in plain language. No absolutes, only what the architecture supports.

  • Shielded by default in the Orchard pool: amount, sender, and recipient are not visible on-chain for shielded sends.
  • Wallet traffic is routed through embedded Arti Tor.
  • If Tor is unavailable, zbag does not fall back to a direct connection.
  • Your ISP sees Tor traffic rather than direct wallet-server requests.
  • The lightwallet server does not receive your direct IP, though it still receives wallet requests.
  • Keys and seed stay in the Rust core.
  • Discreet display controls.
  • Fail-closed behavior.

Built like an instrument.

A Rust core does the sensitive work. The interface works with derived, non-sensitive data, and every automation has a manual lever.

F-01

Shielded by default

zbag defaults to Orchard shielded funds. Sending to a transparent address is a visible exception that requires explicit acknowledgement.

Pool · Orchard shielded pool
F-02

Fail-closed Tor

Routed through an embedded Tor client, no system setup. If Tor is unavailable, zbag does not fall back to a direct lightwalletd connection.

Route · Arti, embedded
F-03

Air-gapped signing

Keystone hardware support over animated QR. Your spending keys can live on a device that never touches the internet, signing with PCZT.

Sign · Keystone / PCZT
F-04

Keys stay in Rust

Spending keys never reach the interface. Seed phrases appear only in explicitly permitted flows, not logged or persisted by the UI layer.

Core · librustzcash
F-05

Built-in swap

Built-in swaps route through NEAR Intents and settle as native ZEC on mainnet. zbag treats swap-related transparent exposure as explicit, not hidden.

Swap · NEAR Intents
F-06

Desktop-first

A real desktop application, not a browser tab. The dense, deliberate surface privacy work deserves. macOS, Windows, and Linux.

Build · macOS / Win / Linux

A look at the wallet.

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.

Design preview with sample data: the zbag desktop wallet showing sample balances, addresses, history, and block heights.
Design preview with sample balances, addresses, history, and block heights.

What everyone else sees.

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.

Your ISP
Sees Tor traffic, not direct wallet-server requests.
The lightwallet server
Receives requests over Tor, not your direct IP.
The Zcash chain
Amount and parties hidden for shielded sends.
You
Balances, history, and memos in the clear, locally.
Design preview with sample data: sending to a transparent address, shown as a visible, explicit exception.
Design preview. A transparent send is shown as a visible, explicit exception. Sample data.

Get on the list.

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.

No third-party email service. Your address lives on our own infrastructure, a single Cloudflare Worker and a small database. We store a SHA-256 of your IP, never the raw address. One message when there is something real to say.
Early access
↳ Self-custodial software · this is not investment advice. We do not sell or share your address.