NozyWallet Development Roadmap

Zcash Apps
34

Hello everyone,

It’s been about a month since the last post here (Aug 4 — Teriyaki Hot v2.4.5 / Mango Habanero v2.4.6 / Desktop Hot Lemon Pepper Sprinkles beta.6). We’ve been heads-down missing calls etc. This is a development update from master, not a new CLI/desktop tag. If you want the last packaged binaries, those tags are still the ones to download. New work is in the repo and we will cut a release when CI + assets are ready.

Huge thanks to everyone testing with us — especially @gilmore

What landed on GitHub master since that post

1. NU7 coinholder vote (time-sensitive)

Vote window is Aug 25 → Sep 14, 19:00 UTC. Snapshot was Aug 24 19:00 UTC, spendable Ironwood notes only. Tallies: https://tally.valargroup.org · Forum: domain=zcashcommunity.com&sz=64)NU7 Coinholder Vote

Nozy path (issue #273, merged #275):

  • Desktop Vote tab + CLI nozy vote-export-notes / nozy vote-sign-delegation
  • Seed stays in the wallet. Voting hotkey is separate.
  • Prepare / prove / cast go through the nozy-vote helper (we do not link zcash_voting into the same binary as Zeaking — SQLite conflict). Same split on companion API + extension.

Honest: this is export + sign in Nozy, ballot via the Valar helper, not “one-click vote with no extra binary.” If you still have Orchard-only funds, migrate to Ironwood first or you have no weight.

2. ZIP 318 “half balance” — funds were not stolen

After Ironwood prep splits, some wallets showed ~half the expected ZEC. On our operator profile the cache went 0.0199 → 0.0419 ZEC after a targeted rescan. Notes were on-chain the whole time; the app under-counted twins.

Cause: ZIP 318 emits equal-value notes with different nullifiers. Old merge keyed on (txid, height, value) and dropped a twin. Incremental sync could then persist that under-count.

Fix is in-tree (#198, #277): nullifier-keyed merge, refuse-to-persist guard, bounded chunk sync. If your balance looks halved after a split, run nozy sync --start-height <birthday-or-split> --to-tip (or the desktop equivalent) before assuming loss.

3. Mainnet Ironwood sends still on the ZIP-317 floor

Desktop still spends one Ironwood note per transaction (not multi-note “send all”). Wallet UI balance is the sum of notes; a send is one note minus fee. Use Max (largest note − fee) when the total looks “enough” but no single note covers amount + fee.

Recent public v6 txs (fee 0.0004 ZEC = ZIP-317 2-action ×4):

  • 77760342b8eac3c5290af2081d5ae872cf470fadbeccfa4ef66634a9462d2545
  • 661cf93e688879211e86961e33208b8a2d31ce7daeaf0c9c7f1576f003d24c98 (Max send 0.0896 ZEC)

That is the fee-pilot shape, not mempool congestion pricing.

4. Nozy Sync Engine (Zeaking feeder)

New in-repo daemon (#274 / #282): ingest from Zebrad or Zakura JSON-RPC, serve the lightwalletd CompactTxStreamer subset on :9067. Zeaking / Nozy point LIGHTWALLETD_GRPC at it.

Live smoke on our WSL Zebrad: compact blocks + treestate PASS. This does not replace Zebrad. Transparent UTXO / mempool streams are still unimplemented. lightwalletd remains a documented fallback.

5. Chrome Web Store (beta)

The extension is live: domain=google.com&sz=64)https://chromewebstore.google.com/detail/nozywallet/pnlmnkallkmelflckjkmohemibfahoce

Honest versioning: the store listing is 0.1.7 (updated Aug 2). GitHub has newer zips. Store has not caught up to every commit. Treat it as beta.

6. Network privacy — send egress, not a slogan

What we actually shipped: send-egress badge (Local / Mixnet / Tor / I2P / Clearnet / Blocked), local Zebrad stays direct even if mixnet is armed, consumer stopgap at zcash.nym.com (OS VPN, not in-app Nym), Ironwood hygiene still on by default.

What we are not claiming: “Nym integrated,” live remote mixnet sendraw, or fresh dVPN Fast-mode numbers (those two are still blocked on a public RPC / Nym pin).

7. Crosslink Protocol Guardian (feature-net)

Nozy is a companion, not a Crosslink consensus node. We proved stake / unbond on Season 1. That small ZEC pool is a proof surface, not funding. Mainnet ZEC stays isolated from that RPC.

8. Companion API hardening

Still same-machine, default 127.0.0.1:3000, now with API-key hardening. Not a hosted wallet API.

In the tree / interesting, not a tagged product yet

  • Mobile: UI + EAS Android prep. Not on App Store / Play.
  • Merchant / ZekuraPay: local POS in the companion API; hosted gateway is a separate repo. Shielded Ironwood only.
  • ZNS: name resolve on Send was already in the Aug 1 update; on-chain claim from the wallet is still later.

What this is not

  • Not a new installer after v2.4.6 / beta.6
  • Not Desktop GA
  • Not multi-note “send the whole balance in one tx”
  • Not “Least Authority audited NozyWallet”

Repo: GitHub - LEONINE-DAO/Nozy-wallet: NozyWallet is a Orchard wallet built for Zebrad, delivering the highest level of Zcash privacy through fully-shielded transactions and cutting-edge cryptographic security. Built in Rust with support for Ironwood shielded transactions, it provides complete financial privacy with secure key management and seamless integration with the Zcash ecosystem · GitHub

No Delays

— Lowo88 / LEONINE DAO