Hi all,
This is the forum thread for my retroactive grant application: #99 on GitHub.
Short version: zec_wallet is a Flutter package that gives an app shielded ZEC. You add it like any other dependency. The keys stay in a Rust core built on librustzcash and never reach Dart.
I’m asking for $15,000 for work that’s already done and published (category Wallets, June to November 2026).
The wallet code started out inside Relim, a messenger I’m building, but supporting it as a public SDK was never part of the messenger’s plan. After a call with Paco in the spring, I split it out into a separate product so other Flutter teams wouldn’t have to start from zero. Every Flutter Zcash wallet I found was an app, not a library.
What’s out there now:
- zec_wallet on pub.dev, the SDK itself: create or restore, sync, shielded send and receive over Orchard and Sapling, ZIP-321 URIs, memos, ZIP-320 two-step sends, an offline send queue, watch-only through a UFVK, swaps, and a hook so the host app can bring its own transport
- zec_wallet_ui, zec_wallet_ui_platform and zec_wallet_tor: a drop-in wallet UI (16 languages), screen protection for it, and optional Tor
- dialer-tor on crates.io, the Tor client by itself for any Rust app
NU7 was the big job in late October. 0.0.5 went out six days before activation, and after the upgrade a mainnet payment made with it confirmed in under two minutes. On the 0.0.6 release commit the public CI ran 2,622 Rust tests and 2,420 Dart tests.
To be upfront about the limits: it’s pre-release, nobody outside has audited it yet, and you build it from source, so you need a Rust toolchain. The one known issue is public as issue #1.
Some of you saw the earlier thread about a Flutter SDK for Zcash. Watch-only support was asked for there, and it shipped in the first release. If you try the packages in an app, I’d really like to hear what breaks.