Lowo88
August 7, 2026, 6:41pm
26
Hey I’m back for the retroactive grant Nozy wallet has come a long way since my last try at this. I have learn a lot since then as well and the Zcash community has shown me a lot of support thank you all. Building this wallet is the start of a new life for me. Here’s the NozyWallet Development Roadmap I got the send to work last time Nozy wallet was only a receiving wallet which was shameful on my behalf to submit.
I tried not to be so hard on myself about because this my first time in life doing this and asking for a grant at this level and I’m shaking in my zoots. I did a few side quest as well with Nozy wallet What NozyWallet just shipped (baseline hygiene) we add Zcashnames to Nozy wallet and the dynamic fee a long with NYM IP protection Safer Ironwood migration IP from Nozywallet .
I also created a thread for some of the support and proof of Nozy wallet works Nozy Lounge . Privacy is very important to me and If I get funding I would never stop building just will build more and contribute as much as, I can Zcash is my home and I spend a whole lots of time here and it’s fun so this not work to me it’s a lifestyle.
opened 06:05AM - 05 Aug 26 UTC
### Terms and Conditions
- [x] I agree to the [Grant Agreement](https://9ba4718… c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471_6ff6db4095fd4c4ba21babec361e927e.pdf) terms if funded
- [x] I agree to [Provide KYC information](https://9ba4718c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471_7d9e73d16b584a61bae92282b208efc4.pdf) if funded above $50,000 USD
- [x] I agree to disclose conflicts of interest
- [x] I understand that this grant program is only eligible for completed work, as it is a retroactive grant program. Applications for planned or partially completed work will not be considered. All completed work will be verified and accepted by its intended users or their representatives, who will confirm that the outputs meet the required quality, functionality, and usability before the work is listed as an option for Coinholder voting.
- [x] I agree that for any new open-source software, I will create a CONTRIBUTING.md file that reflects the high standards of Zcash development, using the [`librustzcash` style guides](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#styleguides) as a primary reference.
- [x] I understand when contributing to existing Zcash code, I am required to adhere to the project specific contribution guidelines, paying close attention to any [merge](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#merge-workflow), [branch](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#branch-history), [pull request](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#pull-request-review), and [commit](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#commit-messages) guidelines as exemplified in the librustzcash repository.
- [x] I understand all grants are valued in USD but will be disbursed in Shielded ZEC. I acknowledge and accept that disbursement amounts may fluctuate based on the ZEC/USD exchange rate at the time of payment.
### Application Owners (@octocat, @octocat1)
@Lowo88
### Organization or Individual Name
Leonine DAO
### Additional Team Members
```team-members.yaml
- Name: Lowo88 / LEONINE DAO
Role: Lead maintainer (NozyWallet)
Background: Orchard-first Zcash wallet engineering on Zebrad + lightwalletd
Responsibilities: CLI, desktop, shared core, releases, evidence docs
```
### How did you learn about the Lockbox: Coinholder Retroactive Grants Program?
Zcash Community Forum
### Requested Grant Amount (USD)
$60,000
### Category
Wallets
### Project Summary
### NozyWallet is Zcash privacy you run yourself
Shielded-first on your Zebrad/Zakura + lightwalletd, with local witnesses, not a hosted light wallet that sees your sync graph.
Most wallets trade convenience for someone else’s infrastructure. Nozy is built the other way: you self-host the node stack, keep keys on your machine, and sync/send over Zebrad/Zakura + lightwalletd with local Orchard/Ironwood proofs. Privacy at full strength for people who refuse to outsource the chain CLI, Desktop, and companion API on the same core.
### Project Description
## Overview and goals
NozyWallet (https://github.com/LEONINE-DAO/Nozy-wallet) is a shielded-first Zcash wallet stack for people and businesses who want privacy without outsourcing the chain to someone else’s node. It is a wallet + companion services not a consensus node. Users run (or point at) their own Zebrad/Zakura + lightwalletd; Orchard/Ironwood proofs use local witness derivation.
### Privacy = your node, not someone else’s
The privacy hole is not “who holds the seed phrase in a slogan.” It is what you give away when you connect a wallet to other people’s nodes hosted light servers, remote WalletConnect-style backends, or any third-party sync path that sees your IP, compact-block requests, and usage pattern. Shielded on-chain still leaks if the sync and broadcast path is someone else’s.
NozyWallet is built the other way:
- Default product path: self-host Zebrad/Zakura + lightwalletd (or infra you operate).
- Local witness derivation proofs do not depend on a remote prove/sync provider seeing your wallet graph.
- Companion API defaults to localhost (127.0.0.1); remote bind is explicit.
- Merchants who choose privacy settle shielded on infra they run; business payment/wallet operational data stays on that stack.
- Network privacy for sensitive flows prefers loopback and supports Tor/I2P / opt-in Nym not silent clearnet when policy says otherwise.
### Developers — build on nozywallet-api
The companion HTTP API (`nozywallet-api`) is a first-class surface for builders. Apps can sync, read balances, send shielded ZEC, estimate ZIP-317 fees, track history/confirmations, and use Business/invoice helpers without embedding the full Desktop UI. Production integrators already run the API headlessly on VPS (Gleyo-style withdrawal / product backends and similar). Goal: “build a Zcash app” means “talk to a self-hosted Nozy companion,” not invent a new wallet stack or route users through a third-party node.
### Merchants — run a business on Nozy
Desktop and API expose Business profile / invoice-oriented flows so merchants can accept shielded ZEC on their own node stack. Invoices and Business wallet tooling live in-repo on a native path not a third-party payment processor or someone else’s light wallet. Merchants who want privacy keep operational control of node + wallet/business data.
### Ecosystem goal — more Zcash nodes
Nozy’s default product path assumes Zebrad/Zakura + lightwalletd. When more people adopt NozyWallet for personal use, merchant ops, or API-backed apps, more operators stand up or keep. Zcash nodes instead of concentrating sync on a few hosted light servers. Wallet growth and node growth move together.
### Technical Approach (how you did it)
**Architecture:**
- Shared Rust core (`nozy`) + CLI; Desktop Tauri and api-server reuse the library.
- api-server: Axum HTTP companion (loopback by default) exposing wallet/sync/send/fee/history and related routes for GUI and headless integrators.
- Sync: lightwalletd compact blocks + Zebrad JSON-RPC; local witness derivation.
- Fees: client-side ZIP-317 with Nozy mandatory priority ×4 on send surfaces.
- Ironwood: ZIP 318–shaped migrate path; network privacy gate for broadcast.
- Releases: CLI via GitHub Actions; desktop under desktop-v* tags; api-server as workspace package.
**Reviewer verification:**
- Public repo + CLI/Desktop release artifacts.
- api-server source and docs under api-server/.
- Mainnet TXID evidence for send + Ironwood turnstile.
### Time Period of Work Completion
June 2025 – August 2026 (CLI/Desktop production path and Ironwood mainnet migration evidence; releases through v2.4.4 / desktop-v1.0.0-beta.5)
### Total Budget (USD)
$60,000
### Budget Breakdown
- Compensation:
- $(USD): 60000
- Justification: Retroactive recognition for completed CLI + Desktop + companion API engineering (~600h blended at ~$100/hr narrative).
- Technology/Software:
- $(USD): 0
- Justification: Covered under compensation.
- Infrastructure/Hosting:
- $(USD): 0
- Justification: Operator-run Zebrad/LWD; not requesting hosted node funding.
- Services/Contractors:
- $(USD): 0
- Justification: No third-party audit engagement in this ask.
- Other:
- $(USD): 0
- Justification: N/A
- Total $(USD): 60000
Split (informational):
- CLI (`nozy`): $25,000
- Desktop (Tauri): $25,000
- Companion API (`nozywallet-api`): $10,000
### Previous Funding
No
### Previous Funding Details
N/A
### Other Funding Sources
No
### Other Funding Sources Details
N/A
### Success Metrics
- Verifiable mainnet Orchard send + Ironwood turnstile TXIDs (published evidence docs).
- Public CLI + Desktop releases on GitHub (v2.4.x / desktop-v*).
- Companion API (`nozywallet-api`) used in production by headless VPS integrators (Gleyo-style apps) and merchant/Business flows — not GUI-only.
- Product path couples wallet adoption to self-hosted Zebrad + lightwalletd (more Nozy users → more Zcash nodes) instead of third-party node / WalletConnect-style sync.
- Localhost-default companion API; privacy posture is “your node,” not “someone else’s light server.”
- Zcash Names (ZNS) resolve shipped across CLI, Desktop Send, and companion API — recipients by name, not raw address-only.
- Opt-in Nym network privacy shipped in Desktop (Settings → Network privacy) for sensitive broadcast/submit paths — Tor/I2P-friendly posture, not silent clearnet-only.
- Ironwood readiness + migrate path (ZIP 318–shaped) on CLI/Desktop with mainnet turnstile confirmation.
- ZIP-317 priority ×4 fee policy on send surfaces; fee-estimate on API.
- Business profile + invoice flows on Desktop/API for merchants who choose shielded settle on self-hosted infra.
### Proof of completion
Repository: https://github.com/LEONINE-DAO/Nozy-wallet
- CLI releases: https://github.com/LEONINE-DAO/Nozy-wallet/releases (e.g. v2.4.4 / v2.4.5)
- Desktop releases: desktop-v* tags (e.g. desktop-v1.0.0-beta.5 / beta.6)
- Companion API source: https://github.com/LEONINE-DAO/Nozy-wallet/tree/master/api-server
- https://github.com/LEONINE-DAO/Nozy-wallet/blob/master/api-server/scripts/companion-api-smoke-proof.png
- API docs: https://github.com/LEONINE-DAO/Nozy-wallet/blob/master/api-server/README.md
- Mainnet send evidence: https://github.com/LEONINE-DAO/Nozy-wallet/blob/master/docs/reference/MAINNET_SEND_READINESS_EVIDENCE.md
- TXID: ecbd068880e9512983f9ec36a1014c84ed51065886b0bcc657415feaccd4016b
- Ironwood migration evidence: https://github.com/LEONINE-DAO/Nozy-wallet/blob/master/docs/reference/MAINNET_IRONWOOD_MIGRATION_EVIDENCE.md
- TXID: ea2fa4e64a5ca3f588dea58f38feb2a72a8d4e30292ac012d983e23bde7048fd @ 3430663
- Security self-review (not LA cert): https://github.com/LEONINE-DAO/Nozy-wallet/tree/master/docs/reference/security-audit
- Prior rejected application: https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/6
<img width="634" height="221" alt="Image" src="https://github.com/user-attachments/assets/c189afcc-522b-4af0-882b-54dcc2b33beb" />
<img width="1151" height="817" alt="Image" src="https://github.com/user-attachments/assets/28a281f4-304f-4553-b6b7-6fc8b1dfa8c4" />
### Conflict of Interest Disclosure
None known beyond being the maintainers of NozyWallet.
### Community Forum Posting
- [x] I understand it is my responsibility to post a link to this issue on the [Zcash Community Forums](https://forum.zcashcommunity.com/t/about-the-retroactive-grants-category/52106) after this application has been submitted so the community can give input. I understand this is required in order for the community to discuss and vote on this grant application. Note: If you are unable to post on the forum (for example, due to new user restrictions), please leave a comment below, and we will adjust your posting permissions.
Hope @thowar2 is proud of me
3 Likes
